When Everyone is Aligned, Why is Nothing Moving?

Most organizations can tell you their headcount cost, their technology spend, their vendor invoices, and their project budgets to the dollar.

Far fewer can tell you what they spend on people talking about work instead of moving it forward.

That number would be uncomfortable.

Not because conversation is wasteful. It isn’t. Strategic discussion matters. Governance matters. Risk review matters. Alignment matters. In complex organizations, you need forums, controls, escalation paths, and decision rights. Without them, things break quietly until the

consequences become expensive.

But somewhere along the way, many organizations have quietly confused conversation with progress.

A meeting is held, but no decision is made.

A risk is raised, but no owner is assigned.

A status update is given, but the system of record is not updated.

A stakeholder is consulted, then another, then another, until the original question becomes a corporate relay race with no finish line.

Everyone is aligned. Nothing is moving.

And the cost keeps accumulating.

Let’s Give Governance Its Credit

I’m not here to argue against governance. Quite the opposite.

Good governance is one of the most valuable operating disciplines an

organization can have. It creates transparency. It protects

decision-makers. It gives teams a structure for managing risk, cost,

scope, and accountability. It prevents projects from becoming

personality-driven or dependent on whoever happens to shout loudest in

the room.

Done well, governance accelerates delivery, because it removes

ambiguity. It tells people who owns the decision, what information is

required, where the approval sits, what risk needs to be managed, and

what happens next.

That’s the good version.

But here’s the part worth sitting with: governance stops being

governance the moment it stops clarifying. When it introduces more

uncertainty than it resolves, it has quietly become bureaucracy.

And bureaucracy is not neutral. It has a cost.

The Coordination Tax

Every organization pays a coordination tax.

Some of it is necessary. People need to communicate. Teams need to

align. Cross-functional work requires shared context. The issue is not

the existence of coordination. The issue is when coordination becomes

the work.

You see it in meetings that exist because no one is willing to make a

decision offline. You see it in governance forums where the same issue

is discussed repeatedly because the previous conversation was never

documented properly. You see it when entire management layers become

skilled at convening calls, forwarding messages, and “checking in,” but

less effective at removing friction, making trade-offs, or driving

resolution.

The meeting itself is rarely the full cost. The real cost is the

preparation before it, the follow-up after it, the duplicated

explanation, the rework caused by miscommunication, the additional

stakeholder management, the delayed vendor action, the contractor hours

spent waiting, and the delivery momentum lost while the organization

tries to remember what it already agreed.

That isn’t a meeting problem. That is an operating model problem.

A Story That Still Bothers Me

A few years ago, I was working on a system implementation that was missing one upstream piece of software. Not a complex piece. A simple,well-understood one. Adding it would have closed several control gaps and saved hundreds of manual hours every month. I knew it would work, because I had installed it at another organization. The case was not theoretical.

I raised it early. There was ample time to act.

I was pulled into location-specific meetings to share the vision. No decision.

I prepared workflow slides showing exactly how the solution would land. No decision.

I pointed out, in senior stakeholder meetings, that the organization already owned adjacent software with overlapping capability that they simply were not fully using. No decision.

A year later, I was still sitting in the same meetings, discussing the same issue. The message had not changed. Some of the faces had.

I have asked myself why many times. Was no one willing to own the decision? Did no one have the time? Did no one believe the math?

Or, and this is the question I keep coming back to, had the discussion itself quietly become the work?

When Alignment Becomes Avoidance

Alignment is one of those corporate words that sounds responsible.

“We need to align.”

“Let’s socialize this.”

“We should bring everyone on the journey.”

“Let’s make sure the right stakeholders have visibility.”

Sometimes those are exactly the right instincts.

But sometimes alignment becomes a sophisticated form of avoidance.

It becomes a way to delay ownership without admitting that no one wants

to own the decision. It becomes a way to distribute accountability so

widely that accountability effectively disappears. It becomes a way for

people to remain involved without being responsible.

That is where organizations quietly lose money. Not always through bad

decisions. Sometimes through the absence of decisions.

A delayed decision still has a cost. A repeated conversation still has a

cost. A poorly documented action still has a cost. A manager who creates

more clarification work than they remove still has a cost.

The problem is that these costs rarely appear cleanly in a budget line.

They show up as project overruns, consultant extensions, vendor delays,

delivery fatigue, missed milestones, and teams quietly working evenings

to compensate for daytime inefficiency.

The Framework Exists. The Behaviour Doesn’t.

Here is the part most organizations don’t want to look at.

Most large organizations already have a governance framework that, if

followed, would resolve much of what I have just described. Decision

rights are documented. Systems of record are defined. Escalation

pathways exist on paper. Roles are mapped between delivery teams,

sponsors, governance, and support functions. The language of “single

source of truth” appears on slide one.

The cost is rarely a missing framework. The cost is the gap between the

framework and the daily operating reality.

Organizations are, in effect, paying twice. Once to design the

discipline. Once to absorb the consequences of not following it.

Verbal updates are given in meetings and never make it into the system

of record. The next forum rediscovers the same issue and reopens it. A

decision is taken in a working session and quietly unwound by a

stakeholder who was not in the room. A risk is flagged repeatedly

without being formally owned, because everyone assumes someone else has

logged it.

That is not governance. That is theatre dressed in governance language.

And the irony is that the policy documents themselves are usually

excellent. They are clear. They are well-structured. They were signed

off at senior level. The question is not whether organizations know what

good looks like. They have written it down. The question is why they do

not operate by it.

What the System Quietly Selects For

It is tempting to blame individuals — the manager who attends every

meeting but resolves nothing, the project lead who forwards rather than

decides, the stakeholder who shows up late and reopens settled

questions.

That is unfair, and more importantly, unhelpful.

Organizations select for and promote the very behaviour they later

complain about.

We reward visibility. We reward presence in the right forums. We reward

people who use the right language, manage perception, and stay close to

the most senior person in the room. We rarely reward friction removed.

Over time, this produces a layer of management that is highly skilled at

corporate navigation, because that is what the system has been training

people to be. It is not a moral failing. It is an incentive design.

If we want different behaviour, we have to price different outcomes. Did

this person clarify ownership? Did they accelerate a decision? Did they

reduce duplication? Did they protect delivery from unnecessary noise?

Did they make the path easier for the people doing the actual work?

Those are answerable questions. We just rarely ask them.

The Accounting Mirror

There is something quietly absurd in all of this, especially for those

of us trained in finance.

We measure vendor spend to the cent. We challenge contractor rates. We

review every line of technology cost. We debate headcount approvals down

to the FTE. We track variance against budget with monthly precision.

But we estimate the cost of internal coordination at roughly zero.

We do not measure how much time is spent in recurring meetings that

produce no decisions. We do not measure how many people attend forums

where they neither contribute nor own an action. We do not measure how

often delivery leads are pulled away from execution to re-explain

context that should already have been captured. We do not measure how

many delays come from unclear ownership rather than genuine complexity.

For a profession built on precision, that is a strange omission. It is

not that the cost is invisible. It is that we have decided not to look.

What Better Looks Like

Better does not mean fewer meetings. It does not mean stripping

governance to the bone. That would be reckless.

Better means being more disciplined about the purpose of every

conversation.

Every meeting should produce at least one of four things: a decision, an

owner, an action, or a documented risk. If it produces none of those, it

should not have happened.

Every governance forum should be clear on whether it is there to inform,

recommend, approve, or escalate. If the purpose is unclear, the forum

will drift.

Every recurring meeting should be challenged regularly. What decision

does this enable? What risk does it reduce? What work does it

accelerate? If the answers are vague, the meeting is probably theatre.

Every manager should be assessed not only on activity, but on friction

removed. Did they clarify ownership? Did they reduce duplication? Did

they improve decision velocity? Did they protect delivery teams from

unnecessary noise?

Because that is what good management does. It does not create more work

around the work. It clears the way for the work to happen.

Cut the Drag, Not the Control

Organizations often hesitate to challenge bureaucracy because they worry

it sounds like challenging control.

But reducing bureaucracy does not mean reducing accountability. In most

cases, it means strengthening it.

A bloated process can hide weak accountability. A long meeting can

disguise poor decision rights. A crowded approval chain can make

everyone feel involved while no one is truly responsible.

Lean governance is not careless governance. It is governance that knows

what it is for.

It is clear on who decides, who advises, who executes, and who needs to

be informed. It records decisions properly. It avoids reopening settled

questions. It distinguishes between material risk and procedural habit.

It respects the time of the people doing the actual delivery.

Most importantly, it recognizes that every hour spent in circular

conversation is an hour not spent building, solving, testing,

implementing, improving, or serving the customer.

The Bottom Line

The organizations that thrive in the next decade will not be the ones

with the most meetings, the most governance forums, or the most

elaborate reporting structures.

They will be the ones that know the difference between useful

coordination and expensive noise. They will be the ones that ask whether

their management layers are enabling delivery or insulating themselves

from accountability. They will be the ones that measure decision

velocity with the same seriousness they apply to budget variance. They

will be the ones that understand that Opex leakage does not only come

from external spend. Sometimes it comes from internal inefficiency that

everyone has learned to tolerate.

So maybe the real question is not whether organizations need more

alignment.

Maybe it is this:

If everyone is in the meeting, everyone has visibility, and everyone is

aligned, why is the work still not moving?