Most leaders assume shared context exists in their teams. They think smart people in the same room will naturally align on goals, priorities, and what “done” means. They’re wrong.
Common sense is not common. Clarity is something you build deliberately, every time — through explicit expectation setting, deliberate buy-in, and only then execution. In that order. Always.
The assumption that breaks teams
I’ve seen it happen dozens of times. A leader runs a planning session, everyone nods, and then the team ships something completely different from what was intended. The leader calls it an execution failure. It wasn’t. It was a clarity failure — and the leader caused it.
When you assume shared context, you skip the hardest part of leadership: creating genuine alignment before work begins. You end up with a team that’s working hard in slightly different directions, and you won’t know it until the damage is done.
The three-step model
Step 1: Expectation setting. Write down what you mean. Not the goal — the full picture of what success looks like, what constraints exist, what trade-offs are already made. If it’s not written, it doesn’t exist.
Step 2: Buy-in. This is not agreement. Buy-in means the person understands what’s expected AND has had a genuine opportunity to push back. Without this step, you have compliance at best. When things get hard, compliance evaporates.
Step 3: Execution. Only now. If you’ve done steps one and two properly, execution becomes almost boring. The decisions that usually slow teams down — trade-offs, prioritisation, scope — have already been made.
Why leaders skip to step three
Because steps one and two feel like overhead. They take time, they require writing things down, they require uncomfortable conversations where people disagree. Step three feels productive. You’re shipping things. You’re moving fast.
Until you’re not. Until the team has built the wrong thing, or built the right thing but nobody adopted it, or built the right thing but burned out because they didn’t understand why it mattered.
What this looks like in practice
Before any significant piece of work, I write a one-page brief. Not a spec — a brief. What we’re doing, why now, what success looks like in 90 days, what we’re explicitly not doing, and what decisions I’ve already made. Then I share it with the team before the kickoff conversation, not during it.
The kickoff conversation is step two. Its job is not to explain the brief — it’s to pressure-test it. I want people to find the holes before we start, not after we’ve shipped.
This process takes maybe two hours of my time upfront. It saves weeks downstream.
Clarity is your job to create. Nobody else is going to do it for you.