The data initiative had been in discussion for months. Meeting after meeting, we circled the same questions without landing them. Then one day, while in a room with IT leadership, we finally seemed to make progress. Heads nodded. The tone shifted from debate to agreement. We would proceed.
I walked out believing we had alignment. We had nodding. The gap between them cost us some of my best people.
The Agreement That Was Not There
The trouble did not show up while the decision stayed general. At a high level, everyone agreed. We needed the initiative. It mattered. We should move.
The cracks appeared when the details reached the final stages. As we moved from principle to specifics, each IT department turned out to hold a different version of what the project actually was. One team understood it as a platform upgrade. Another saw it as a governance and data quality effort. A third of the participants believed that the focus was primarily on reporting. Each had nodded in that room. Each had nodded at a different project.
The agreement I thought I had was an illusion built on vague language. Nobody had lied. Nobody had even disagreed out loud. They all agreed to a version of the initiative that existed only in their heads, and since we never forced the specifics into the open, those versions never had to reconcile until it was costly to do so.
This is more common than most leaders admit. A 2026 Harvard Business Review analysis of organizational change found that most efforts fail not because of poor execution, but because senior leaders fall into a false alignment trap, believing they agree on the why, the what, and the how when they actually do not. The trap grows from vague discussions, avoidance of disagreement, and pressure to move quickly. We had all three.
They had all nodded. They had each nodded at a different project.
Why the Nodding Happened
Looking back, the false agreement was not an accident. The conditions produced it.
We had spent months in discussion, and everyone was tired of the subject. When agreement finally appeared within reach, nobody wanted to be the person who reopened the debate by asking an awkward, specific question. Fatigue made yes feel like release.
Meetings reward this behavior. Research shows 71% of senior executives consider meetings unproductive, and a large share of that waste comes from decisions that feel settled in the room but were never actually made. McKinsey calls one version of this the consensus trap, where teams mistake the absence of visible objection for genuine agreement, and warns that chasing surface-level consensus leads to diluted outcomes and misdirected effort.
That was exactly what happened to us. Silence in the room was not agreement. People were conserving energy and assuming that their individual interpretations were shared by others.
What It Actually Cost
Here is the part that still bothers me. The project did not fail on paper. We delivered it within acceptable limits of time and budget. If you looked only at the delivery metrics, you would call it a success.
The real cost did not appear on any status report. It fell on the people.
The team members who initiated the data initiative spent the delivery phase watching their vision get continually renegotiated because the initial alignment was never real. During delivery, the team had to revisit every unresolved disagreement from that early room, each one requiring a renewed battle under deadline pressure.
By the time the initiative went live, the people who had started it were gone. They had left the company, worn down not by the work but by the frustration of watching leadership treat a nod as a decision. The project shipped. The talent that created it did not stay to see it. That is a cost no budget line captures, and it is far harder to recover from than an overrun.
I wrote about a related failure in my first big mistake as a technology leader, where I assumed stakeholders had been aligned before I arrived. This was the same lesson from a different angle. Alignment you assume is not alignment you have.
How to Force Real Agreement
The fix is uncomfortable, which is exactly why teams avoid it. You have to make people be specific before you let them say yes.
Reject the agreement on principle. Push the decision into detail while everyone is still in the room. What exactly are we building? What does each department understand its role to be? Ask each person to state, in their own words, what they think the project is. The moment you do this, the false agreements collapse and the real disagreements surface, which is precisely when you want them, at the start, not during delivery.
Write the decision down and circulate it within a day, in plain language, with the specifics named. If someone’s understanding differs, they will say so when they read it, before the difference becomes expensive. HBR’s research on the false alignment trap points to the same discipline: specificity, early and safe dissent, clear decision rights, and formal commitment. Investing that time up front does not slow you down. It accelerates execution, because you are not re-litigating settled questions halfway through the build.
And protect the people who raise the awkward question. The person who says “wait, I thought this was about something else” is not slowing you down. They are saving you months and, in my case, saving you the people you cannot afford to lose.
I have learned to distrust a smooth room. When agreement comes too easily after a hard problem, I now assume it is not real until I have heard each person describe the decision in their own words. If your team nods and moves on, ask them what they just agreed to. The answers will tell you whether you have alignment or just the appearance of it. Getting that right is a large part of the work I do with leadership teams. I explore these patterns further in my book Life in the Digital Bubble, and you can find more at tamerbadawy.com.