Sanjay K Mohindroo
One question reveals whether leaders truly agree on outcomes, value, and accountability before a transformation consumes more capital and credibility.
The One Question That Exposes Misalignment in 60 Seconds
Give a leadership team 60 seconds and one sheet of paper.
Ask each person the same question separately, and you may learn more about the state of a major transformation than you will from a 60-page steering committee deck.
The question is:
“Twelve months from now, what single business outcome will prove this initiative was worth the capital, how will we measure it, and who is accountable for delivering it?”
Over three decades around enterprise technology, I have learned that the most dangerous form of misalignment is rarely open disagreement.
Open disagreement is visible. It can be debated.
The expensive kind is false alignment. Everyone approves the same programme, uses the same vocabulary, attends the same steering committee, and leaves the room believing they agreed on something they actually defined very differently.
That is why this question matters.
It turns alignment from an impression into something you can test.
Most leadership teams confuse consensus with alignment
The conventional wisdom is that large transformation programmes need stakeholder buy-in.
They do.
But buy-in is not alignment.
A board can unanimously approve a technology investment while individual executives expect entirely different returns from it.
The CEO may believe the programme is about improving customer experience.
The CFO may believe it is about reducing operating cost.
The CIO may believe it is about replacing an ageing technology estate.
The business unit leader may expect faster growth.
The risk function may primarily want stronger controls.
Everyone can support the programme.
Everyone can also be pulling it in a different direction.
That distinction matters because large initiatives rarely fail from a complete absence of intelligent people, project plans or governance meetings.
They often fail because important decisions are made against different definitions of success.
When budgets tighten, which capability survives?
When implementation creates disruption, which benefit justifies continuing?
When two business units compete for priority, which objective wins?
When the programme is six months late, what gets protected and what gets cut?
If the leadership team has never agreed on the primary business outcome, those questions get answered tactically.
That is when transformation becomes a collection of compromises rather than an instrument of strategy.
The 60-second business alignment test
The test is deliberately simple.
Before reviewing roadmaps, architecture, vendors, or programme status, ask the leaders responsible for the initiative:
Twelve months from now, what single business outcome will prove this initiative was worth the capital, how will we measure it, and who is accountable for delivering it?
Ideally, ask them individually before discussing the answers as a group.
You are looking for four things.
1. Outcome: Are we solving the same business problem?
The first test is whether people describe the same result.
Not the technology.
Not the project.
Not the activity.
The result.
“Implementing a new platform” is not an outcome.
“Completing the cloud migration” is not an outcome.
“Deploying AI across customer service” is not an outcome.
Those describe work being performed.
A business outcome sounds different:
- Reduce customer onboarding time from ten days to two.
- Increase revenue per sales employee by 15 percent.
- Reduce inventory locked in the supply chain by 20 percent.
- Cut the cost of servicing a customer transaction by 25 percent.
- Reduce the financial exposure created by a critical operational risk.
The distinction looks obvious on paper.
It becomes surprisingly difficult in a boardroom.
If one executive describes the outcome as growth, another as cost reduction, and another as technology modernisation, the initiative is not yet aligned. It may simply have accumulated several rationales to secure approval.
That is an uncomfortable conclusion.
It is also far cheaper to discover before the capital is spent.
2. Measure: Would we recognise success if we saw it?
The second test is measurement.
I have seen many initiatives with extensive programme dashboards and surprisingly weak measures of business value.
Green milestones do not necessarily mean a successful investment.
A programme can be on budget, complete every technical milestone and still fail commercially.
Boards should therefore distinguish between delivery metrics and outcome metrics.
Delivery metrics tell you whether the programme is progressing.
Outcome metrics tell you whether the company is becoming better because of it.
Both matter, but only one answers the investment question.
Consider a company funding a major digital customer programme.
A delivery dashboard might report:
- percentage of functionality completed,
- number of users migrated,
- system availability,
- implementation milestones achieved.
Useful information.
But none of those numbers tells the board whether customers are buying more, staying longer, receiving faster service or costing less to serve.
The board should be able to identify one primary business measure that determines whether the investment created value.
If success cannot be measured, almost any result can later be presented as success.
That is not governance.
It is retrospective storytelling.
3. Time: When exactly should value become visible?
Transformation language often becomes vague around time.
We talk about strategic value, future capability, long-term competitiveness, and foundations for growth.
Some investments genuinely require patience.
But “long term” can also become a convenient hiding place for weak accountability.
A board allocating capital should know when evidence of value is expected to appear.
Not necessarily the full return.
Evidence.
If the programme is expected to take three years, what should be materially different after twelve months?
If nothing measurable is expected for thirty-six months, the board should understand why.
Time creates discipline because it converts ambition into a commitment.
Without a time horizon, programmes can remain strategically important almost indefinitely.
4. Accountability: Which executive owns the outcome?
This is where the question becomes uncomfortable.
Ask who owns programme delivery, and the answer is usually easy.
There is a programme director.
There may be a CIO, transformation office, implementation partner, and steering committee.
Ask who owns the business outcome, and the answer is often less clear.
That is a problem.
Technology can enable a reduction in working capital.
It cannot own working capital.
Technology can enable sales productivity.
It cannot own revenue.
Technology can provide customer data.
It cannot own customer retention.
If a transformation promises a business result, a business executive must ultimately own that result.
This does not reduce the CIO’s accountability. It makes accountability more accurate.
The CIO remains accountable for technology capability, reliability, security, execution and the integrity of the investment.
But if a programme claims it will increase revenue, improve margins or change customer behaviour, the executive responsible for that business outcome must be visibly committed to delivering it.
A steering committee is not an accountable owner.
Neither is “the organisation”.
When everyone owns the outcome, nobody truly does.
What misalignment sounds like in the boardroom
Imagine asking six executives the 60-second question before approving the next phase of a major programme.
You receive these answers:
CEO: “It should materially improve customer retention.”
CFO: “It needs to take at least 10 percent out of our cost base.”
CIO: “We need to retire our legacy environment and reduce operational risk.”
COO: “It should simplify processes across the organisation.”
Business leader: “We need faster product launches.”
Programme sponsor: “We need to deliver the transformation roadmap.”
None of these objectives is irrational.
That is precisely the problem.
They are all plausible enough to coexist without anyone noticing that the company has not made a choice.
A major programme can support several benefits, but it still needs a dominant economic or strategic logic.
Why?
Because eventually those benefits will compete.
A decision that optimises customer experience may increase operating cost.
A decision that accelerates implementation may delay legacy retirement.
A decision that standardises processes may reduce flexibility for a high-growth business unit.
Without an agreed hierarchy of outcomes, every trade-off becomes political.
The programme does not lack governance.
It lacks a governing objective.
A simple board framework: O-M-T-A
I use a very simple way of thinking about the answer.
Call it O-M-T-A:
Outcome. Measure. Time. Accountability.
Before committing significant capital, the board should be able to complete one sentence:
We are investing in this initiative to achieve [OUTCOME], evidenced by [MEASURE], by [TIME], with [EXECUTIVE] accountable for delivering the business result.
If that sentence cannot be completed without twenty minutes of debate, the organisation is not ready to debate technology choices.
That debate comes later.
First agree on what the money is supposed to accomplish.
The board should test five things
Once the sentence is written, ask:
1. Is there one primary outcome?
Secondary benefits are fine, but the organisation should know which result wins when trade-offs appear.
2. Is the measure economic or strategically meaningful?
Avoid confusing implementation progress with enterprise value.
3. Is the time horizon explicit?
Define when evidence of value should become visible.
4. Does one executive own the result?
Committees can govern. Individuals remain accountable.
5. Would the same answer survive outside the meeting?
Ask leaders independently. Alignment produced only after group negotiation may be compliance, not conviction.
That fifth test is particularly useful.
Senior leadership teams are very good at creating consensus in meetings.
The stronger test is whether they remain aligned when they are no longer sitting around the same table.
Misalignment is a capital allocation problem
It is tempting to classify this as a communications issue.
I think that seriously understates the risk.
Misalignment is a capital allocation problem.
If a company commits $50 million to a transformation and its executives disagree about what the investment is fundamentally intended to achieve, the organisation has effectively approved multiple competing investment theses under one budget.
That affects far more than project execution.
It changes vendor choices.
It changes sequencing.
It changes organisational design.
It changes which capabilities receive funding.
It changes which compromises are acceptable.
And, eventually, it changes how success or failure is reported to the board.
The cost of misalignment therefore does not appear as a single line item.
It appears as rework, delayed benefits, scope expansion, political escalation, underused capabilities and investments that technically finish but never produce the return originally expected.
“But large transformations have multiple objectives”
This is the most reasonable objection to the one-question test.
Of course they do.
A major ERP transformation, for example, may improve control, lower cost, standardise processes, reduce technology risk and create better management information.
The answer is not to pretend those secondary outcomes do not exist.
The answer is to establish hierarchy.
Every serious strategic investment needs a primary reason for existing.
If the company had only 60 percent of the available capital, which benefit would it protect?
If the programme had to sacrifice one objective to secure another, which one wins?
If the board had to judge the investment five years later using only one measure, what would it choose?
Those questions expose priority.
And priority is what makes strategy executable.
A strategy that treats every objective as equally important has avoided the hardest part of strategy: choosing.
Use the question before the programme is in trouble
Most organisations perform alignment exercises after warning signs appear.
Budgets increase.
Timelines move.
Benefits become uncertain.
Business sponsors disengage.
Then everyone asks whether the programme is aligned with strategy.
That is too late.
The 60-second question belongs much earlier.
Use it when approving the business case.
Use it before selecting major partners.
Use it at the start of each major investment phase.
Use it when leadership changes.
Use it when a programme requests substantial additional funding.
Most importantly, use it before discussing the technology itself.
Boards do not need to become technology committees.
They need to become much harder to satisfy on the connection between technology and enterprise value.
The real test of alignment
A perfectly aligned leadership team does not need identical language.
It needs a common economic logic.
Ask five leaders why the organisation is spending the money.
If one talks about growth, another about efficiency, another about risk, another about modernisation and another about completing the programme, do not congratulate yourself on having a broad transformation agenda.
You have probably discovered five different investment theses.
Resolve that before approving the next tranche of capital.
The best governance question is often not the most sophisticated one.
Sometimes it is simply the question nobody has forced the room to answer precisely.
Twelve months from now, what single business outcome will prove this initiative was worth the capital, how will we measure it, and who is accountable for delivering it?
Ask it separately.
Give people 60 seconds.
Then compare the answers.
You may discover that the transformation problem you thought you had is actually an alignment problem.
And discovering that early can save far more than another round of programme optimisation ever will.
What is the one question you use to determine whether a leadership team is genuinely aligned, rather than simply in agreement?
Subscribe to TechnologyTrends, or add your perspective in the comments, especially if your experience leads you to a different conclusion.