Sanjay K Mohindroo
Alignment meetings rarely solve misalignment. Learn the four decisions leaders must make to turn executive discussion into real business commitment.
Alignment Meetings Do Not Create Alignment
I have sat through two-hour alignment meetings where every executive left saying, “We are aligned.”
Three weeks later, the same programme had three priorities, two definitions of success, and no one willing to make the trade-off that mattered.
That is not unusual.
Across large transformation programmes, I have seen organisations spend enormous amounts of executive time trying to create alignment through meetings. More steering committees are formed. More workshops are scheduled. More stakeholders are invited. More slides are produced.
Yet the underlying disagreement remains.
The conventional wisdom is that alignment comes from communication. Get the right people into a room, give everyone visibility, discuss the issues openly, and eventually the organisation will converge.
I disagree.
Alignment is not a communication problem. It is a decision problem.
Meetings can expose misalignment. They can clarify information. They can improve understanding.
But alignment only exists when leaders agree on the outcome, accept the trade-offs, know who has the right to decide, and understand what happens next.
Without those conditions, the meeting has merely created the appearance of alignment.
The Most Dangerous Meeting Ends With Everyone Agreeing
The obvious sign of a bad meeting is conflict.
The more dangerous sign is unanimous agreement followed by inconsistent action.
Consider a familiar transformation scenario.
A large enterprise decides that improving customer experience is a strategic priority. The business wants faster product launches. Operations wants stability. Finance wants tighter investment discipline. Technology wants to reduce legacy complexity.
None of these positions is irrational.
The executives meet. Everyone agrees that customer experience matters. Everyone supports transformation. Everyone agrees that speed, resilience, cost control, and modernisation are important.
The meeting ends positively.
Then the real decisions begin.
Should the company delay a launch to retire a fragile legacy dependency?
Should it accept higher near-term operating cost to improve resilience?
Should a business unit abandon a customised process so the enterprise can standardise?
Should a promising initiative lose funding because another programme has greater enterprise value?
That is where alignment is tested.
Agreement on objectives is easy when the objectives are abstract. Alignment becomes visible only when two desirable outcomes compete for the same capital, capacity, or executive attention.
If nobody has agreed which objective wins under pressure, the organisation was never aligned.
It merely agreed with a collection of aspirations.
More Alignment Meetings Often Make the Problem Worse
When executives sense disagreement, the natural response is often to schedule another meeting.
This can become a sophisticated form of avoidance.
The same issue is discussed again with slightly different slides. More analysis is requested. Another stakeholder is brought in. Someone proposes a workshop. The decision is deferred until the next steering committee.
Activity increases while accountability decreases.
There is a reason for this.
A meeting allows an organisation to distribute discomfort. A decision concentrates it.
Choosing one priority means another priority loses. Funding one programme may mean stopping another. Giving one executive decision authority means somebody else has less control. Standardising across the enterprise means some business units lose local flexibility.
Those are real organisational costs.
So leaders can unconsciously substitute discussion for decision.
I call the result alignment theatre: visible collaboration without explicit commitment.
It feels constructive because everyone is participating. But the underlying economics have not changed, the conflicting incentives remain, and nobody has accepted the consequences of the supposed agreement.
Business and IT Alignment Is Really About Trade-Offs
This is particularly visible between technology and the business.
For years, organisations have talked about “business and IT alignment” as if the challenge were primarily one of mutual understanding.
Certainly, understanding matters.
But most senior executives already understand far more about each other’s priorities than we sometimes admit.
The CEO knows that technology cannot modernise an estate instantly.
The CIO knows that a commercial leader cannot simply tell customers to wait while architecture improves.
The CFO understands that resilience costs money.
The business understands, at least conceptually, that accumulated complexity creates risk.
The problem usually appears when those truths collide.
A business unit wants a capability in three months. Technology says delivering it properly requires six. Finance will fund only one of two competing programmes. Operations refuses a change during a critical trading period.
Another alignment session does not resolve that conflict.
A decision does.
Which outcome matters most?
Which risk is the enterprise prepared to accept?
Who owns that call?
What stops as a consequence?
Those questions create alignment because they turn strategic language into operational commitment.
The Four Tests of Real Alignment
Over time, I have found it useful to test alignment against four questions.
If a leadership team cannot answer all four clearly, I would hesitate to call it aligned.
1. Outcome: What are we optimising for?
Most organisations have too many priorities because they confuse important things with priorities.
Everything can be important.
Everything cannot come first.
A transformation programme might be expected to reduce cost, improve resilience, accelerate growth, simplify the technology estate, improve customer experience, and strengthen compliance.
But when those outcomes conflict, which one takes precedence?
Boards should demand more precision.
Instead of saying, “This programme will improve efficiency and customer experience,” ask what measurable business outcome has first claim on capital and management attention.
Perhaps the primary objective is reducing customer onboarding time from ten days to two.
Perhaps it is reducing the cost-to-serve by 15 percent.
Perhaps it is eliminating a concentration risk before a regulatory deadline.
Once the outcome is explicit, hundreds of downstream decisions become easier.
Without it, every function optimises for its own interpretation of success.
2. Trade-offs: What are we willing to give up?
This is the question most alignment discussions avoid.
Strategy is not a list of things an organisation wants.
Strategy is a set of choices about what it will prioritise and what it will not.
If speed is genuinely the priority, the organisation may need to accept additional cost.
If standardisation is the priority, some local flexibility will disappear.
If resilience is non-negotiable, certain launches may move more slowly.
If capital efficiency is the priority, some attractive innovations will not be funded.
The boardroom test is simple:
Can leaders articulate what they are willing to sacrifice in order to achieve the stated priority?
If not, the priority is probably still an aspiration.
A useful discipline is to write the trade-off beside the objective.
“Accelerate market launch, accepting up to X additional transition cost.”
“Reduce operating complexity, accepting reduced local customisation.”
“Improve resilience, even if selected delivery milestones move.”
That language is less comfortable than a strategy slide.
It is also far more useful.
3. Decision rights: Who makes the call when priorities collide?
Many organisations are clear about governance until somebody has to say no.
Then authority becomes surprisingly ambiguous.
A programme has a sponsor, a steering committee, a transformation office, business owners, technology leaders, finance representatives, and risk functions.
Yet when a difficult choice emerges, nobody is sure who can decide.
Consensus becomes the default decision mechanism.
That sounds collaborative. At enterprise scale, it can become expensive.
Consensus works when interests naturally align. Governance exists for the moments when they do not.
Every material transformation should therefore establish explicit decision rights.
Who decides whether scope changes?
Who can move funding between initiatives?
Who can accept a technology or operational risk?
Who can stop a programme whose original business case no longer holds?
Who breaks a deadlock between enterprise and business-unit priorities?
If five executives believe they possess veto rights, the organisation does not have governance. It has a queue.
4. Consequences: What changes because we agreed?
This is the most practical test.
After the meeting, what is different?
Has capital moved?
Has a programme stopped?
Has a milestone changed?
Has one priority been elevated above another?
Has an executive accepted ownership of a risk?
Has a team been told what it should no longer do?
If nothing changes, there is a reasonable chance that no meaningful alignment occurred.
Real alignment leaves evidence.
You should be able to see it in investment decisions, performance measures, resource allocation, portfolio sequencing, incentives, and executive behaviour.
The minutes of the meeting matter less than the decisions visible in the organisation afterwards.
The Hidden Cost of Alignment Debt
There is another consequence that boards should pay attention to: alignment debt.
Like technical debt, alignment debt accumulates when difficult choices are repeatedly deferred.
A programme begins with several unresolved assumptions. Nobody settles them because delivery needs to start.
Business units interpret priorities differently. Exceptions are approved. Temporary compromises become permanent. Dependencies multiply.
Eventually the organisation pays for those unresolved decisions through delay, duplicated investment, executive escalation, rework, and weakened accountability.
What initially looked like a people problem often becomes a capital problem.
I have seen transformation teams blamed for slow execution when the underlying issue sat much higher in the organisation. They had been asked to execute against priorities that senior leaders had never truly reconciled.
No project management methodology fixes that.
Teams cannot execute clarity that leadership has not created.
Surely Meetings Still Matter?
Of course they do.
The answer is not fewer conversations for the sake of fewer conversations.
Good alignment meetings have an important role. They surface facts, expose assumptions, identify disagreements, and create the conditions for a decision.
The mistake is treating the meeting itself as the outcome.
A useful alignment meeting should therefore be designed around decisions rather than updates.
Before the meeting, leaders should know:
1. What decision must be made?
2. What competing outcomes are involved?
3. What evidence is required?
4. Who owns the final decision?
5. What actions will change depending on the answer?
That produces a very different conversation from an agenda consisting of 12 workstream updates followed by “discussion.”
The distinction matters.
Information can be shared asynchronously.
Executive time should be spent resolving choices that cannot be delegated.
Alignment Does Not Mean Consensus
There is one final misconception worth challenging.
An aligned leadership team does not necessarily agree.
This matters because some organisations pursue harmony when they should pursue clarity.
A CIO may believe a decision creates unacceptable technical risk. A commercial leader may believe delay creates unacceptable market risk. The CFO may challenge both assumptions.
That disagreement is healthy.
Alignment exists when the debate has occurred, the decision mechanism is legitimate, the choice has been made, and leaders commit to executing it even if their preferred option did not win.
That is very different from consensus.
In fact, organisations that require visible consensus on every important decision often make decisions too slowly or dilute them until nobody strongly objects.
The result may feel collaborative.
Competitors are unlikely to care.
What Boards and CEOs Should Ask Instead
The next time a major programme comes to the board or executive committee claiming that “stakeholders are aligned,” I would ask four questions:
What outcome are we optimising for?
What have we explicitly agreed to trade off?
Who has the authority to resolve the next conflict?
What changed in capital, priorities, ownership, or behaviour because of this alignment?
If the answers are vague, another meeting will not solve the problem.
The leadership team has a decision to make.
That distinction becomes more important as organisations undertake larger digital, AI, operating-model, and technology transformations. These programmes cut across functions precisely because the underlying business choices cut across functions.
Technology rarely creates the hardest trade-offs.
It exposes them.
The organisations that move fastest are not necessarily those with the most workshops, steering committees, or collaboration tools.
They are the ones that can turn disagreement into decisions without turning every decision into an organisational crisis.
That is what real alignment looks like.
In your organisation, how often does “we are aligned” actually mean “we have made the difficult trade-offs”?
If this resonates, subscribe to TechnologyTrends or share your experience in the comments.