Don’t call it calm water just because the room hasn’t looked yet.
A leadership team had worked together for a while. Collegiality reigned supreme. They could almost finish each other’s sentences and usually saw eye to eye. This came in handy because the business was experiencing rapid growth and the pace of application development was increasing as a result. Pressure was building to deliver the applications to help the business meet its financial objectives.
Vigorous debate was replaced by acquiescence for the sake of speed. That distinction matters because senior teams often mistake polite silence in the meeting for alignment. People leave without openly objecting, then reinterpret the decision, delay execution, protect their functions, or continue advocating for the option they lost. The organization experiences conflicting priorities while the leadership team continues to describe itself as aligned.
On paper, everyone had agreed to the growth plan and to the process that was supposed to support it. Nobody had verified the network could carry the load the plan assumed.
A team member discovered the approaching tsunami and went to their manager, visibly shaken: the network didn’t have the capacity to handle the wave of graphic-intensive applications already coming down the pipeline.
If they raised it, they would face resistance from a significant piece of the organization racing to hit its financial targets. If they didn’t, the organization would suffer consequences senior leadership hadn’t yet seen coming — a forced pause on a number of customer-facing application rollouts.
In the process, they uncovered a flaw in the project management process itself: people had been using exceptions to skirt strict adherence to process, kicking the can down the road.
The team member and their manager took the finding to functional leadership, then called the other functions in to deliver the news. It did not go well — until they laid out the scenario end-to-end and showed the projected month-by-month capacity requirements. The team member did the bulk of the presentation; the manager bookended it, opening and closing, and made sure credit for catching the problem landed where it belonged.
As the group began debating next steps, they displayed the final chart: a plan for closing the capacity gap and fixing the process flaw. Toward the end of the meeting, someone asked how this could have happened. The answer was direct: “For the sake of speed, we took everybody’s word that it would all work out, never challenged it, and let the exception process prevail.”
The fix was projected to take eighteen to twenty-four months. The network partner they brought in rebuilt it in twelve. The team member who’d walked into that first meeting visibly shaken left the year having been right, heard, and credited for it. The credit stuck — he went on to lead the technology side of a bank acquisition and became one of the real stars of the organization.
A leadership team does not need unanimity of opinion—but it does need unity of execution. If you and I always agree, one of us is redundant. Every room needs a devil’s advocate, someone who will push back when they see the wave building. There was agreement on the plan. There was no alignment on enforcing the discipline that made it possible.
Agreement is intellectual: We see this the same way.
Alignment is operational: We understand the decision, know why it was made, accept our responsibilities, and will act consistently with it—even though some of us preferred another course. We had the debate and looked at all the issues eight ways from Sunday. We’ve experienced positive contention and have now settled on a course of action that we can all agree on.
Real alignment requires four things:
Clarity: What exactly was decided—and what was not?
Commitment: Will each leader support the decision in words and behavior?
Coordination: Who owns what, by when, and what dependencies must be accounted for?
Consistency: Will employees hear the same message from every leader and execute accordingly?
The cultural prerequisite is genuine permission to disagree before the decision. If dissent is unsafe, apparent agreement may simply be compliance. But compliance is not commitment. Once relevant concerns have been heard and the decision is made, leaders have a responsibility to execute it faithfully—or explicitly state that they cannot.
Shorthand:
Agreement means, “I would have chosen this.”
Alignment means, “This is what we have chosen, and I am committed to help make it work.”
The measurable test is not what leaders say around the conference table. It is whether priorities, resources, decisions, communications, and behavior remain coherent after they leave the room.
The wave doesn’t wait for a vote.
Where in your organization is ‘we’re aligned’ actually just ‘nobody objected’?
