The Art of the Handoff
The moment a project moves from one person to another is where most things break. On designing clean interfaces between humans.
Every broken project I've ever seen died at a handoff. Not at the kickoff. Not at the deadline. At the seam where one person's understanding ended and another's was supposed to begin.
We talk endlessly about strategy, about execution, about talent. But we almost never talk about the connective tissue between them — the moment when context transfers from one mind to another. And yet, this is where the real work lives.
The context problem
When you've been deep in a project, you carry an enormous amount of implicit knowledge. You know why that decision was made. You know which stakeholder cares about what. You know the three approaches that were considered and rejected. You know the political landmines. This context lives in your head, and most of it never makes it into a document.
So when you hand the project to someone else — "here's the brief, here are the files, good luck" — you're handing them an iceberg and pretending it's just the tip. They can see what was decided. They can't see why. And without the why, they'll inevitably re-litigate decisions, miss constraints, or optimize for the wrong thing.
Designing the interface
Software engineers figured this out decades ago. When two systems need to communicate, you design an interface — a clear, documented contract between them. The interface defines what goes in, what comes out, and what each side is responsible for. Good interfaces are the reason complex software works at all.
Human handoffs need the same rigor. Not a 40-page document no one reads — a clear, structured transfer of the essential context. I've found that a good handoff answers exactly five questions:
Where are we? The current state, honestly assessed. Not where the plan says we should be. Where we actually are.
Why are we here? The key decisions that shaped the current state, including the ones that went sideways. Context on constraints, tradeoffs, and the reasoning behind non-obvious choices.
Where are we going? The intended outcome. Not a list of tasks — the actual destination. What does "done" look like, and what does success feel like?
What could go wrong? The risks you can see from your vantage point. The stakeholder who changes their mind. The technical constraint lurking under the surface. The thing that kept you up at night.
Who matters? The people with influence, their motivations, and how to work with them. The human map of the project.
Leaders as editors
The best leaders I've worked with aren't the most visionary or the most charismatic. They're the ones who are exceptional at editing information flow. They take a complex, messy reality and compress it into something their team can actually act on. They absorb ambiguity so their team doesn't have to.
This is the real work of leadership — not making decisions, but creating the conditions for good decisions to happen. And that starts with clean handoffs. Clean briefs. Clear context. The unglamorous work of making sure the person after you has everything they need to succeed.
Every minute you invest in a clean handoff saves hours of misalignment downstream. It's the highest-leverage work that almost nobody prioritizes — because it doesn't feel like "real work." It feels like overhead. But it's not overhead. It's the infrastructure that makes everything else possible.