jump to...

Sometimes vision pulls reality forward. Sometimes it replaces reality entirely.

Most people talk about the say-do gap as a moral failure. A person says one thing and does another. A company puts values on the wall and behaves differently. A leadership team announces a strategy, then funds the old priorities. The easy conclusion is hypocrisy.

I think that is too simple.

Some distance between what we say and what we do is necessary. If there is no distance at all, there is no aspiration. There is only description. A company that says exactly what it already is has not stated a vision. It has written an inventory.

The useful question is different: how far ahead of reality can a statement sit before it stops pulling behavior forward?

That distance matters more than leaders admit.

The useful gap

I have seen healthy gaps. They are easy to recognize because they create useful discomfort.

An engineering organization says, “We own reliability,” before it has mature SLOs, clean postmortems, or a serious on-call rotation. At first, the statement is ahead of reality. Fine. But then the work starts moving toward the words. Teams define service ownership. They create error budgets. They stop treating incidents as embarrassing surprises and start treating them as operational data. The sentence becomes a magnet.

That is a productive say-do gap.

The same thing happens in leadership. A team says it wants faster decision-making. In the beginning, the calendar still tells the truth: recurring steering meetings, escalation chains, approvals for decisions that should sit two levels lower. But if the aspiration is real, the operating system changes. Decision rights move. Meeting agendas shrink. Leaders stop asking to be briefed on every low-risk tradeoff. The organization becomes a little more like the thing it keeps saying.

This is what I mean by aspirational gravity.

A healthy gap between stated vision and lived reality creates pull. The current state is not identical to the future state, but the relationship between them is still alive. People can see the distance. They can feel it. They can name what has to change.

That last part is important. The gap has to remain visible.

When the distance gets too large

The problem starts when the stated aspiration moves too far away from operational reality.

I see this constantly in AI transformation work. After years around cloud strategy, enterprise architecture, and executive briefings, I have learned to trust the operating model more than the announcement.

A company says it wants to become an agentic organization. Then you look at what the agents are allowed to do. They can summarize account notes, draft a follow-up email, search internal documentation, maybe generate a first-pass market brief. Useful work, but still work trapped inside the old permission model.

The agent cannot open a customer ticket, update a forecast, trigger a workflow in the CRM, make a low-risk configuration change, or decide which lead deserves follow-up without waiting for a manager. Every output gets routed into the same human approval chain that existed before the agent was built.

At that point, the company has added a faster drafting layer to a non-agentic organization.

That distinction matters. The technical details reveal the truth.

When someone tells me “AI will change work,” I look for changed decision rights. For “teams are empowered,” I check budget authority, escalation paths, and who can say no. A data-driven claim has to show me a dashboard that actually changes a resourcing decision. A copilot claim sends me straight to SharePoint permissions, document lifecycle rules, stale content, RBAC, and whether anyone has cleaned the source material.

The words are cheap. The operating model is expensive.

As the distance grows, the aspiration loses gravity. People still repeat it, but the sentence no longer pulls anything. It becomes conference-room language. It appears in slides, town halls, strategy documents, and internal launch posts. The phrase is alive. The mechanism behind it has died.

This middle stage is dangerous because it still looks respectable.

Nobody has to lie. The company can point to pilots, task forces, executive sponsorship, working groups, training sessions, and a roadmap. All of those may be real. But if the work does not move authority, incentives, architecture, funding, and measurement, the aspiration is floating above the organization rather than pulling it.

It becomes a beautiful object in the sky.

The collapse

There is a worse stage.

At some point, the organization stops experiencing the gap as a gap. The words become a substitute for the work.

I have seen this happen in small ways and large ones. A team says it is customer-obsessed, then measures support success by ticket closure instead of customer resolution. A leadership group says it values ownership, then punishes anyone who makes a decision without pre-alignment. A company says it is moving to product thinking, then keeps funding work as projects with fixed scopes, fixed dates, and no durable team accountability.

After enough repetition, people adapt to the contradiction. The phrase no longer irritates them. Nobody flinches when the slide says “ownership” in a room where nobody owns the outcome. Nobody feels strange saying “AI-first” while every AI output still waits in a human queue for approval. Nobody sees the irony in announcing speed through a process that requires four governance meetings before a team can test anything with a customer.

That is aspirational collapse.

The aspiration has stopped pulling reality forward. It now protects the organization from seeing reality clearly.

This is the point where the say-do gap becomes more than hypocrisy. Hypocrisy still knows there is a gap. Collapse is worse because the awareness starts to disappear. The organization talks as if the desired future has already arrived. The talk becomes evidence. The deck becomes proof. The announcement becomes progress.

This is why I am skeptical when leaders say, “We already do that.”

Sometimes they do.

Often, they have simply heard themselves say it so many times that the statement has become familiar enough to feel true.

How to measure the gap

The practical answer is to treat aspiration as an operational claim.

If a company says “we are becoming agentic,” that sentence should create testable evidence. Which decisions are now delegated to systems? Which human approvals were removed? Which workflows can an agent complete end to end? What is the rollback path when the agent is wrong? What telemetry proves the process changed? Who owns the error budget? What work disappeared from human calendars?

If the answer is mostly demos, training, and enthusiasm, the aspiration is still speech.

If a company says “teams are empowered,” watch what happens when a team makes a decision that creates discomfort above them. Are they protected if the decision was reasonable, or punished because they failed to pre-align? Empowerment without protected decision rights is theater.

If a company says “we move fast,” look at approval latency. How many days pass between a good idea and a real customer-facing test? How many people can block the path? How many of those blockers carry accountability for the outcome? Speed is measurable. So is slowness.

I would build a simple say-do ledger for any serious transformation.

For every major aspiration, write the operational proof beside it. Not the communication artifact. Not the launch plan. The proof. Then write the current distance from that proof, the owner of the gap, and the next irreversible action that would reduce it.

“We are AI-first” is a slogan.

“Thirty percent of Tier 1 support tickets are resolved by an agent inside approved policy boundaries, with human escalation below five minutes and weekly defect review by the service owner” is proof.

“We empower teams” is a slogan.

“Product teams can approve experiments under $25,000 without VP review, as long as legal and security constraints are met, and the decision is logged for monthly pattern review” is proof.

This is where most organizations get uncomfortable. The moment aspiration becomes measurable, it loses some of its poetry. Good. Poetry is useful when it gives people direction. It becomes dangerous when it shields leadership from operational debt.

The part leaders hate

The hardest part is that organizations usually cannot diagnose aspirational collapse from the inside.

That sounds harsh, but I think it is true.

Once people have adapted to the gap, the gap becomes normal. The internal language system protects itself. A person who asks, “Where exactly has authority moved?” sounds negative. A person who asks, “Which metric changed because of this strategy?” sounds tactical. A person who asks, “What work stopped because this new priority started?” sounds like they are slowing the team down.

In reality, those are the people keeping the aspiration alive.

A healthy organization needs outsiders, or at least outside-positioned insiders, who can say: your words are here, your work is there, and the distance is growing.

That role cannot be purely ceremonial. It cannot be another advisory board with no teeth. The feedback loop has to reach funding, staffing, governance, architecture, incentives, and performance review. Otherwise the external eye becomes part of the performance.

This is also why I care about the connection between communication and delegation.

Communication names the future. Delegation proves whether the organization means it. Culture decides whether the distance between the two can be discussed without punishment.

When those three are connected, aspiration has gravity.

When they break apart, vision becomes insulation.

I am not arguing for smaller visions. I am arguing for honest distance.

Say the ambitious thing. Put the future in language before it fully exists. Give people a direction worth moving toward. But keep measuring the gap. Ask what changed in the operating model, who has new authority, what old work disappeared, which metric moved, and what decision the organization can now make that it could not make before.

The say-do gap is not always hypocrisy.

Sometimes it is the only reason progress happens.

But when the gap gets too wide, and nobody is allowed to name it, the vision stops being a magnet.

It becomes make-believe.

Daron Yondem advises senior technology leaders on AI-driven organizational transformation. Learn more →