Most organisations forget their own promises

Most organisations forget their own promises.

Not the formal ones, or not only those. The signed contract usually survives. The engagement letter is filed. The deadline may be in a calendar. The invoice has a number. The project plan has milestones.

The more fragile promises are quieter.

"We'll keep you close to the process."

"We'll come back with options."

"We'll make sure this does not happen again next year."

"This will stay partner-led."

"We understand what matters to you."

"We'll remember that for the next phase."

These promises are often made in meetings, calls, pitches, check-ins, reviews, side emails, and moments of reassurance. They matter because they shape what people expect. Then the work moves on, the team gets busy, the person who heard the promise is not in the next meeting, and the organisation quietly forgets.

The client does not experience that as a systems problem.

They experience it as distrust.

The Shadow Balance Sheet

Every organisation has a shadow balance sheet of promises.

Some promises are explicit liabilities: deadlines, deliverables, service levels, budgets, filings, approvals, and contract terms.

Others are off the books: reassurance given in a pitch, an exception granted to a key client, a lesson learned after a bad project, a partner's comment in a meeting, a principal's promise about how the work will feel.

Forgotten promises still accrue interest.

The interest shows up as rework, awkward calls, client frustration, write-offs, internal blame, and the familiar sentence: "Why are we having this conversation again?"

The problem is rarely that nobody cared. It is that the promise never became part of the organisation's memory.

Organisational Memory Is Not Just Knowledge

Walsh and Ungson's classic paper on organisational memory describes how organisations acquire, store, and retrieve information from past experience ^{1Walsh and Ungson, "Organizational Memory"}. That sounds like knowledge management, and it is.

But promises add another layer.

An organisation does not only need to remember facts. It needs to remember what it led people to expect.

That is a different kind of memory. It is not just "what do we know?" It is:

• what did we say we would do?
• who heard it?
• who owns it?
• when does it matter again?
• has the promise changed?
• should it be retired, renewed, or corrected?

Professional trust often depends on those questions more than on the brilliance of any single deliverable.

Broken Promises Are Often Small

Research on psychological contracts is useful because it treats promises and expectations as part of working life, even when they are not written into formal contracts. Rousseau described psychological contracts as perceived obligations between parties ^{2Rousseau, "Psychological and implied contracts in organizations"}. Later work found that perceived breaches are common and linked to trust problems (Robinson and Rousseau).

That research is often discussed inside employment relationships, but the idea travels well.

Clients also carry expectations. Teams carry expectations. Partners carry expectations. Project sponsors carry expectations.

Many breaches are not dramatic. They are small failures of continuity:

• a client has to explain the same preference again;
• last year's fix is forgotten during this year's work;
• a promised update arrives only after chasing;
• the team changes and the handover misses the relationship context;
• an agreed constraint disappears from the next draft;
• the firm remembers the task but forgets the reason it mattered.

Each incident may be survivable. Together, they teach people not to trust the organisation's memory.

The Promise Can Be More Important Than The Note

A note might say:

"Client prefers monthly updates."

The promise underneath may be:

"We will not leave you wondering where things stand."

Those are not the same.

If the organisation only remembers the note, it may send a monthly update that technically satisfies the record but misses the client concern. If it remembers the promise, it understands that timing, tone, and reassurance matter.

This is where professional work becomes hard to reduce to tasks. The task is the visible unit. The promise is often the reason the task matters.

Why Firms Forget

Firms forget promises for ordinary reasons.

The person who made the promise is not the person doing the work. The promise was made verbally. The CRM has a note but no owner. The matter file has documents but not expectations. The project plan has tasks but not relationship commitments. The annual cycle resets and everyone assumes someone else remembers.

No villain is required.

This is why better individual diligence is not enough. A promise held only in one person's head is not yet an organisational promise. It becomes one only when the organisation can see it, assign it, revisit it, and decide what to do with it.

Olivera's empirical work on organisational memory systems is useful here because it looks at mechanisms for collecting, storing, and accessing knowledge ^{5Olivera, "Memory systems in organizations"}. Promises need similar mechanisms, but with more care. Not every reassurance should become a rigid obligation. Not every preference should become a permanent rule. Some things need interpretation.

That is why the system should not simply capture promises. It should help people review them.

Promise-Based Work

Donald Sull and Charles Spinosa wrote about promise-based management as a way to understand execution: work moves through networks of commitments between people ^{6Sull and Spinosa, "Promise-Based Management"}.

That is a useful lens because it makes execution human again.

Work is not only a chart of tasks. It is people making and keeping commitments under changing conditions.

For professional firms, this matters because the most valuable work is often relationship-led. Clients do not only buy a deliverable. They buy confidence that the firm has understood the situation and will carry that understanding forward.

When the firm forgets, the client feels the break.

What A Firm Should Remember

A firm does not need to turn every sentence into a task.

That would be awful.

It does need a way to notice commitments that matter:

• explicit promises made to clients;
• recurring preferences;
• sensitive constraints;
• lessons learned after mistakes;
• handover risks;
• promises tied to annual cycles;
• relationship commitments made during pitches;
• follow-up that someone agreed to own.

The key is not only capture. It is review.

Some promises should become tasks. Some should become notes. Some should become risks. Some should be clarified with the client. Some should be rejected because the firm cannot responsibly stand behind them.

Forgetting is not the only danger. Over-promising is another.

The Plain Test

Ask a simple question:

If the person who made the promise is unavailable, does the firm still know what it said it would do?

If the answer is no, the promise is private memory.

That may be fine for small things. It is not fine for the commitments that shape trust.

The firm should also ask:

• Where does this promise live?
• Who owns it?
• When should it be checked?
• What evidence shows it was kept?
• Has the situation changed?
• Does the client still expect it?

These questions are not bureaucracy. They are how a firm remembers the future it asked someone else to believe in.

The Conclusion

Most organisations do not forget because they are careless.

They forget because promises are treated as residue from conversation rather than part of the work.

That is a mistake. Promises are not decoration. They are part of the structure of professional trust.

A firm needs to know what it knows. But it also needs to know what it has said, implied, reassured, and left people expecting.

Otherwise the organisation can complete the task and still fail the promise.

Sources

1. Walsh and Ungson, "Organizational Memory"
2. Rousseau, "Psychological and implied contracts in organizations"
3. Robinson and Rousseau, "Violating the psychological contract"
4. Robinson, "Trust and breach of the psychological contract"
5. Olivera, "Memory systems in organizations"
6. Sull and Spinosa, "Promise-Based Management"