Almost every project I join has a strategy. It has been researched, workshopped and signed off, and it is usually sound. Six months later the thing that launched bears only a family resemblance to it.

Nobody rejected the strategy. It simply did not survive the journey.

Strategy dies by translation

A positioning statement becomes a creative brief, which becomes a route, which becomes a design system, which becomes a build, which becomes a set of launch assets made by a different team under pressure. Each handover is a translation, and each translation loses a little precision.

No single step is wrong. Ten reasonable compromises produce an unreasonable outcome. By the end, the distinctive idea has been sanded into something that could belong to any competitor.

Compress the idea until it travels

A strategy that needs forty slides cannot survive six handovers. It has to be reducible to a sentence that a developer, a copywriter and a media buyer can each hold in their head and apply to a decision you will never see.

That sentence is not a tagline and it is not for the public. It is an internal test. If a proposed choice does not serve it, the choice is wrong, and anyone on the team should be able to say so without needing permission.

The test only works if it can fail. A sentence like we put the customer first rules nothing out and will approve any decision put in front of it. A useful one names a trade-off the organisation has actually accepted, which means somebody senior has to be willing to be pinned to it.

Build the proof early

The fastest way to protect an idea is to make something real while the thinking is still warm. Not a mockup of the ideal case, but the hardest thing the brand will have to do: the pricing page, the difficult product shot, the message that has to work in eight words.

If the idea holds there, it will hold elsewhere. If it does not, you have learned it in week three rather than week thirty, when changing course costs a conversation instead of a rebuild.

Keep one person accountable for coherence

Specialists are accountable for their layer. Somebody has to be accountable for whether the whole thing still adds up, with the authority to stop a reasonable-looking decision that pulls the work off course.

It helps to make this explicit at the outset rather than assuming it. On most projects the role is simply unassigned, and the result is that everybody defers to whoever is most senior in the room on the day, which produces a different answer each week.

That role is unglamorous and mostly consists of noticing drift early, asking the same awkward question repeatedly, and occasionally reopening something the team had considered settled. It is also the difference between a strategy that shaped the work and a strategy that was merely approved.