Why delegation fails when context doesn’t move with authority

“This is not what Joe promised me.”

I have lost clients who felt that way. It hurt.

Looking back, conversations from the beginning of a relationship hadn’t always travelled into the business. The team received work to deliver. The client carried expectations formed in earlier conversations with me.

Those expectations could concern the outcome, the attention they would receive or how we would work together. They weren’t always captured in the brief.

That experience taught me something about delegation: a person can receive responsibility and permission to act while still missing the understanding needed to make a sound decision.

When that understanding remains with the founder, the work keeps finding its way back.

The team can know the task without knowing the promise

In my experience, founders often lead sales in the early years.

They hear why a client wants to change something, what has disappointed them before and what would give them confidence to proceed. Along the way, expectations form through conversations as well as formal agreements.

By the time the work reaches a delivery team, the relationship has already begun.

A handover containing scope, dates and budget may leave out why the client chose the business, what they are particularly concerned about or how they understood a commitment.

The team might know what to produce while lacking the context to explain a trade-off, recognise a concern or judge when a change needs discussion.

I have seen the same gap in advisory work: the project is recorded, while important relationship knowledge remains with the people who brought it in.

The problem sits between sales and delivery. Giving the delivery team more responsibility won’t, by itself, supply what was lost in that handover.

Context makes authority usable

Delegated authority answers a question: what am I allowed to decide?

Context helps someone exercise that authority. What are we trying to achieve? What have we promised? What matters in this situation? Why was the previous decision made?

A manager can have permission to act and still return to the founder because the consequences are difficult to judge without that knowledge.

The founder then supplies the missing history or interpretation. The immediate issue moves forward, but the business may remain dependent on the same explanation next time.

That is why “you have the authority” can leave part of the delegation unfinished.

The person also needs access to the reasoning relevant to their work, along with clear boundaries and a way to raise uncertainty.

Surface expectations before treating them as facts

When I talk about capturing the unspoken conversation, I mean making space to surface expectations that haven’t been clearly expressed or recorded.

An expectation may concern an outcome rather than a task. It may concern the relationship: how concerns will be handled, who will be involved or what access the client believes they will have.

The practical work is to restate our understanding and give the client an opportunity to confirm or correct it.

What do they believe we have committed to? What matters to them beyond the deliverable? What have we assumed rather than confirmed?

A perceived expectation needs checking. Writing down our interpretation doesn’t turn it into an agreement.

Once it is understood, the people responsible for the work need that context in a form they can find and use.

The client needs to understand the authority too

A founder’s presence can carry particular assurance. The client may feel they are speaking to someone who can decide, commit resources and take responsibility for what has been promised.

An internal delegation may therefore be incomplete from the client’s point of view.

In my business, I would bring the person responsible for a smaller client into the conversation early and explain who would look after them. With a major relationship, I would stay alongside the person taking over until the client was comfortable, then make it clear who would lead.

The team member needed context and authority. The client also needed confidence that this person could act with my backing.

Records support that transition. Trust continues to develop through the person’s decisions, follow-through and handling of difficult moments.

Capture the reasoning that helps people decide

Useful context includes commitments, client concerns, relevant history and the reasons behind decisions.

It needs to remain usable as circumstances change. An old preference or assumption should be available for discussion, rather than silently becoming a permanent rule.

The same applies when a new leader wants to change how the business operates. Understanding why a practice developed makes it easier to judge what still matters and what can change.

Records and AI tools can help capture, organise and retrieve this information. People still need to check accuracy, confirm expectations and exercise judgement.

A record earns its place when it helps someone understand the situation well enough to act.

From the founder as the connection to oversight

Revenue and client relationships repeatedly showed me where the business relied on my involvement.

The issue might appear to belong to sales, delivery or account management, while the missing understanding sat between them. I became the connection: explaining the promise, supplying the history or resolving the interpretation.

As the company grew, carrying those connections personally became harder.

Moving towards operating as CEO required a way to see across the business while other people made decisions. That meant helping context travel with responsibility and authority, then building review routines that showed where attention was needed.

This is part of the move from personal control to oversight. The team has a stronger basis for judgement, and the founder can review progress without supplying the meaning behind every decision.

Diagnose what keeps coming back

When a decision returns to the founder, look at what the person needed that they didn’t have.

Was authority unclear? Was a commitment missing from the handover? Did two teams have different understandings of the outcome? Was the situation genuinely outside the person’s remit?

This is the kind of gap I look for through Oversight: the team has the task, but someone else holds the promise. It is also why the connections between functions matter in Growth Architecture. The problem can persist even when each team is doing its own job.

The response should follow that diagnosis. Another process document won’t necessarily resolve an unspoken expectation; more authority won’t supply missing history.

Before asking someone to take more ownership, consider what they need to understand to exercise it.

If that understanding still sits with you, sharing it is part of the delegation.

Where to go next

• How to Grow Client Relationships Beyond the Founder — explore the practical structures that support relationship continuity.

• Keep Client Knowledge in the Business When People Move On — consider how useful context stays available beyond one person.