The Six Things That Count as Your Word
Most promises are easy to recognize.
A proposal is due Friday. A call is scheduled for three. Responsibility for a task has been accepted. If the commitment is missed, there is a visible sentence or agreement to point back to.
Yet many failures of reliability begin without a sentence that sounds like a promise.
A person knows something needs attention and leaves it untouched. An expectation is allowed to stand while another person relies on it. A claim is presented as true without enough care for the evidence behind it. A value is publicly declared and then treated as optional when acting on it becomes inconvenient.
The 2010 seminar materials collected under A New Model of Integrity: The Missing Factor of Production propose a demanding way to examine these situations. In that source model, a person's word is larger than the explicit promises they remember making.
That expansion changes the audit. The question is no longer limited to what was formally promised. It also includes what other people have reasonably been given to organize around because of what was said, known, implied, asserted, or stood for.
The source organizes that inquiry into six forms of one's word.
1. Explicit commitments
This is the familiar category.
A date, deliverable, meeting, payment, response, decision, or action has been promised. The commitment is visible because it was spoken or written.
The harder issue is maintaining accurate information around it. When circumstances change, the people relying on the commitment need to know. That is the territory explored in [When a Broken Promise Is Not the Same as Broken Integrity](/post/when-a-broken-promise-is-not-the-same-as-broken-integrity/): reliability includes what happens as soon as the original promise is at risk.
The audit question here is direct:
Which explicit commitments are currently open, and what is their real status?
Intentions and hopes do not answer that question. The concern is what was actually promised.
2. What is already known to need attention
Sometimes nobody needs to ask.
The customer received the wrong information. A handoff is incomplete. A document contains an error. Equipment requires attention. A difficult conversation needs to happen before the next step can safely proceed.
The source treats such knowledge as relevant to a person's word.
This does not make one person responsible for everything they happen to notice. It creates a decision point when the matter is genuinely theirs to handle. Silence does not resolve that decision.
Several responses can preserve clarity:
- handle the issue;
- assign it explicitly;
- tell the relevant person that responsibility is being declined;
- renegotiate the expectation;
- make the risk visible.
Trouble grows when the issue remains in a private category of things that somebody should probably handle while everyone else assumes it is covered.
Ask:
What is already known to require attention but is currently being treated as though it were unknown?
3. What others reasonably expect unless told otherwise
Working relationships contain expectations that were never written as formal promises.
A manager may be expected to review something before release. A service provider may be expected to protect customer information. A colleague who owns a process may be expected to flag a material problem. A meeting host may be expected to tell participants when the meeting is cancelled.
The source includes these expectations within one's word unless they have been explicitly declined.
This requires judgment. Not every expectation is legitimate, realistic, or binding. Roles can be vague. Teams and families can carry assumptions that should be challenged.
That is why making expectations explicit matters.
A hidden expectation is dangerous in both directions: one person may believe a commitment exists while the other person does not know they are carrying it.
Ask:
Which expectations are other people relying on, and which of them have never been made explicit?
When an expectation is unreasonable, clear refusal is still more workable than silent refusal.
4. What is presented as true
A person's word is not only about future action. It also includes statements other people are invited to rely on.
The numbers are correct.
The system is ready.
The customer approved the change.
The contract was checked.
The deadline is still achievable.
Other people may make decisions from statements like these. The source's model therefore connects integrity with being prepared to stand behind the evidence for an assertion.
This matters in modern work because so much coordination happens through compressed summaries. A dashboard, email, ticket, slide, status update, or AI-generated brief may turn a complicated situation into a few sentences.
Perfect certainty is not required. Accurate representation of certainty is.
A verified fact differs from information received second-hand. Data differs from interpretation. A firm delivery commitment differs from a current forecast.
Ask:
What are other people being asked to treat as true, and what evidence supports that confidence?
5. What a person or organization says it stands for
Organizations publish values. Leaders make declarations. People describe themselves as careful, fair, transparent, dependable, customer-focused, evidence-led, or willing to speak plainly.
Those statements shape expectations.
If a company says privacy matters, that statement becomes relevant when a shortcut would expose unnecessary data. If a leader says disagreement is welcome, the declaration becomes relevant when somebody actually disagrees. If a person presents themselves as reliable, ordinary follow-through becomes part of whether that identity is usable by others.
The source treats what a person stands for as another form of their word.
This turns values from decoration into an operating question:
Where does a declared value create a concrete expectation about action?
A value that never changes a decision may remain an aspiration. It is not yet functioning as much of a commitment.
6. Rules and standards accepted through participation
The final category is the widest.
People participate inside legal systems, professional standards, organizational policies, contracts, ethical codes, and social rules. The source argues that these can become part of one's word through participation unless a rule is explicitly rejected and the consequences of that refusal are accepted.
That does not mean every rule is wise or beyond challenge. Laws can be disputed. Policies can be defective. Ethical standards can conflict.
The useful distinction is between open disagreement and quiet exemption.
A rule can be challenged through refusal, appeal, negotiation, advocacy, or exit. A different integrity problem appears when someone accepts the benefits of participation while secretly treating a shared rule as optional only for themselves.
Ask:
Which rules, standards, or agreements govern current participation, and where has an unspoken personal exception appeared?
A six-part integrity audit
Taken together, the source's model expands the practical meaning of a person's word:
1. Explicit commitments.
2. Responsibilities already known.
3. Reasonable expectations that have not been declined.
4. Assertions presented for others to rely on.
5. Values and standards publicly stood for.
6. Rules accepted through participation unless openly refused.
The list is useful because it makes invisible commitments visible enough to manage.
An expectation can be declined.
An assertion can be corrected.
A commitment can be changed openly.
A value can be named as aspirational instead of presented as an achieved fact.
A rule can be challenged rather than quietly ignored.
Clarity gives other people something real to coordinate around.
The commitments that cause trouble are often the ones never named
Explicit promises have a moment of creation. That makes them easier to remember.
Implicit commitments are harder. They live inside roles, knowledge, assertions, identity, and participation. Two people can therefore carry different understandings of the same situation without either one noticing the gap.
A useful weekly review can go beyond a task list. Move through the six categories and look for places where someone is relying on a commitment that has not been treated as one.
That review can expose a missed handoff before it becomes a failure, a hidden expectation before it becomes resentment, an unsupported claim before it becomes a bad decision, or a declared value before it becomes empty branding.
Integrity becomes more workable when the commitments themselves become visible.
Before a word can be honored, it helps to know where that word already exists.