The meeting ended with nods. The document was signed off. The roadmap was approved. Everyone is aligned.
Until the first constraint surfaces and every stakeholder retreats to their original position. The alignment was not agreement. It was the temporary absence of conflict.
⸻
The Vocabulary Gap
Alignment fails because the same words mean different things to different functions.
When the VP of Engineering says "scalable," they mean the system can handle ten times the current load without architectural changes. When the VP of Sales says "scalable," they mean the pricing model supports enterprise contracts. When the VP of Product says "scalable," they mean the feature set can expand to adjacent markets.
All three approved the roadmap that said "build a scalable platform." All three believe they are aligned. They are not. They are using the same word to describe three different outcomes.
The collision arrives when resources must be allocated and only one definition survives.
⸻
The Approval Trap
Stakeholder sign-off does not mean stakeholder commitment.
Approving a document costs nothing. It is a low-friction action with no immediate consequence. The VP who signed the roadmap did so because objecting would have required a confrontation they did not want to have in that meeting.
Their signature means "I will not block this today." It does not mean "I will defend this when priorities shift next quarter."
When the reorg happens, when the budget gets cut, when the CEO changes direction, the approval evaporates. Every stakeholder reverts to optimizing for their function, and the "aligned" roadmap is quietly abandoned.
⸻
The Meeting as Theatre
Alignment meetings produce a specific artifact: the appearance of consensus. This artifact is politically valuable. It allows the project lead to say "stakeholders are aligned" in the status update.
But the meeting itself is a performance. The real negotiations happen before and after. The backchannels, the one-on-one lunches, the Slack threads between executives that the project team never sees.
If you are relying on the meeting to create alignment, you have already lost. The meeting is where alignment is announced, not where it is built.
⸻
Operating in the Fog
True alignment requires shared constraints, not shared vocabulary.
Instead of asking "Do you agree with this plan?", ask "What would cause you to withdraw support?" Map the kill conditions. Name the resource conflicts explicitly. Document the tradeoffs that each stakeholder is accepting, not just the outcome they approved.
If you cannot name the conditions under which the alignment breaks, you do not have alignment. You have politeness.
End.