The Chief Executive looked across the table at her leadership team and said something I hear often: "We keep having the same conversation. We agree in the room, then nothing changes."
Six months earlier, this technology company had launched a digital transformation programme. The leadership team had "agreed" on the approach. But progress was glacial. Projects were starting and stalling. Resources were being pulled in different directions.
What looked like poor execution was actually something else entirely.
The Problem Hidden in Plain Sight
Before the session, I ran individual diagnostic calls with each leader. The pattern became clear quickly.
The Chief Technology Officer described the transformation as "modernising our tech stack and moving to cloud infrastructure." Sensible. Specific. Technical.
The Head of Operations saw it as "streamlining processes and automating manual work to improve efficiency." Logical. Operational. Process-focused.
The Commercial Director framed it as "improving customer experience and launching digital products faster than competitors." Strategic. Customer-centric. Market-driven.
Three leaders. Three entirely different interpretations of the same "agreed" programme.
No wonder progress was slow. They were not building one transformation. They were building three.
The Moment of Truth
The session opened with silent writing. Each leader wrote their definition of the digital transformation in one paragraph. No discussion first. No anchoring on what others thought.
Then I read each definition aloud without naming who wrote what.
The silence that followed was profound. You could see recognition dawning on each face. They had been polite to each other for six months while fundamentally disagreeing about what they were doing.
The Chief Executive spoke first: "We have been agreeing to disagree without realising we were disagreeing."
Structured Conflict, Not Polite Alignment
Most teams would have spent the next hour debating whose definition was "right." Instead, we used a structured approach to surface what each definition revealed about underlying priorities.
I gave each leader five minutes to argue for their interpretation. Not to defend it - to advocate for it. What would success look like if we pursued their version? What would we be able to do that we cannot do now?
The CTO made the case for technical foundation: "If we do not fix the infrastructure, everything else is built on sand."
The Head of Operations argued for process efficiency: "We are wasting 30% of our capacity on manual work that should be automated."
The Commercial Director pushed for market impact: "Our competitors are launching products in weeks while we take months. That gap will kill us."
Each argument was compelling. That was the problem.
The Trade-Off That Changed Everything
After each leader had made their case, I asked the question that most teams avoid: "If you had to choose one of these three approaches as the primary driver, which would it be? And what would you explicitly not do to make it happen?"
This is where the real work began.
The conversation that followed was uncomfortable. It had to be. They were choosing between three good strategies, which meant explicitly rejecting two of them as secondary priorities.
The Commercial Director argued that market timing was everything. "We can build the best infrastructure in the world, but if our competitors capture the market while we are perfecting our tech stack, we lose."
The CTO pushed back: "If we prioritise speed over foundation, we will build solutions that break under load. We have done this before."
The Head of Operations made a different case: "Both of you are right, but neither of your approaches works if we cannot execute efficiently. Process has to come first."
Silent Prioritisation Reveals the Truth
I could have let them debate for hours. Instead, I used silent prioritisation.
Each leader privately ranked the three approaches from 1-3. No discussion. No negotiation. Just their honest assessment of what should come first.
The results were revealing:
Two leaders ranked market impact as #1. One ranked infrastructure as #1. Process efficiency was ranked #2 by all three leaders, but #1 by none of them.
The data told a story the discussion had obscured. There was more alignment than conflict, but the conflict was in the wrong place.
The Decision That Ended Six Months of Drift
With the real priorities visible, the decision became clear. Market impact would drive the transformation. Infrastructure would be improved as needed to support customer-facing initiatives, not as a separate programme. Process efficiency would be embedded into every initiative but would not lead it.
More importantly, they named what they would stop doing.
The CTO agreed to pause the infrastructure modernisation programme that was not directly supporting customer-facing products. The Head of Operations committed to stopping the process automation initiative that was running in parallel to the transformation. The Commercial Director acknowledged that not every customer request would be treated as equally urgent.
Each leader stated their trade-off explicitly. In front of the others. On the record.
Three Months Later
The transformation is moving faster than it has in eighteen months. Not because the team is working harder, but because they are working on the same thing.
The Chief Executive told me recently: "The conversation we avoided for six months took us ninety minutes to resolve. We should have had it on day one."
She was right. But having it on day one would have required them to acknowledge that they disagreed. That is harder than it sounds.
The Facilitation Lesson
Polite agreement is often disguised disagreement. When teams keep having the same conversation without making progress, the problem is usually not execution. It is alignment.
But surfacing real disagreement requires structure. Left to themselves, most teams will choose comfort over clarity. They will agree to disagree without acknowledging the disagreement exists.
Silent writing, structured advocacy, and forced prioritisation create the conditions for teams to discover what they actually think. Not what they think they should think, or what they think others want to hear.
The insight was in the room all along. It just needed a process to reveal it.