Handoff is a myth
The baton pass from strategy to design to development looks clean on a process diagram. Batons don't carry context. People do.
Every agency process diagram has the same arrows. Strategy hands off to design. Design hands off to development. Development hands off to QA, QA hands off to launch, and everyone stands at the finish line looking accomplished.
The arrows are lying. Let’s take them one myth at a time.
Myth: the document carries the thinking
The theory of handoff is that you can compress three weeks of strategic thinking into a deck, pass the deck down the line, and the thinking arrives intact. It doesn’t. A strategy document is a photograph of a conversation, and like all photographs it leaves out everything that made the moment make sense: the option that got rejected and why, the client’s face when a certain word came up, the constraint that was never written down because everyone in the room already knew it.
Then a designer opens the deck cold and reads “the brand should feel confident but approachable,” which is a sentence that could produce four hundred different homepages. So they guess. Their guess is reasonable. It’s also wrong in some small way nobody can articulate until review, at which point the strategist says “that’s not quite what we meant,” and everyone spends a week excavating meaning that was free three weeks earlier.
Reality: documents are receipts, not vehicles. The thinking travels in people or it doesn’t travel.
Myth: each phase can be sealed before the next begins
Waterfall logic says strategy finishes, then design begins. Clean phases, clean invoices. But strategy that has never touched a screen is speculation, and design that has never talked to a developer is theater. Some of our best strategic corrections have come from a developer asking one blunt question in week two, the kind of question that reveals an assumption everyone upstream had stopped seeing because they’d walked past it so many times it had become furniture.
Reality: phases should overlap like shingles, not stack like bricks. The developer belongs in the strategy readout; the strategist belongs in the design review. Not to supervise. To keep the context alive in the room where the next decision gets made.
Myth: handing off means walking away
This is the quiet one, and it does the most damage. In a handoff culture, finishing your phase means you’re done. The strategist moves to the next pitch and the designer rotates to another account. By the time the site launches, nobody who made the original promises is still around to check whether the launch kept them.
We’ve inherited projects like this, and doing the autopsy is always the same experience: every individual phase was done competently, and the total is still wrong, because correctness leaked out at each exchange and nobody owned the sum.
Four good phases can add up to a bad project.
Nothing in the handoff model even has a word for that failure, which tells you something about the model.
Reality: nobody on our side hands off and walks away. The strategist who wrote the positioning sees the design that interprets it; the designer who set the system watches it survive contact with real content and real code. Ownership runs the length of the project, not the length of a phase.
So what replaces the arrows
Mostly, proximity. Fewer artifacts, more conversations. A designer who heard the client explain the problem in their own words needs a much thinner brief than one who didn’t. We still write things down (decisions need receipts, and memory is a liar), but the documents confirm understanding instead of substituting for it.
And overlap costs something, we should be honest about that. Having a developer in early meetings looks inefficient on a spreadsheet. It reads as billing hours before “their phase” starts. What the spreadsheet can’t see is the rework that never happened, the week-seven surprise that got dissolved in week two, the redesign that wasn’t needed because the first design was built by someone who actually understood the constraint instead of inheriting a sentence about it.
Prevention is invisible. That’s the whole problem with it, and the whole case for it.
A relay team practices the baton pass because the baton is the point. Our work isn’t a baton. It’s more like a story being told by several people in turn, and the only way that ever works is if everyone stays to hear the whole thing.
