The case for visible strategy

The traditional agency rhythm — brief, silence, dramatic presentation — is optimised for the presentation rather than for the work. It concentrates every disagreement into a single meeting, at the point when changing course is most expensive.

Worse, it trains clients to respond to polish. When a direction arrives fully rendered, the conversation becomes aesthetic, because the reasoning has already been packaged as a conclusion.

For us it means the messy artefacts are shared: the diagnostic notes, the discarded structures, the decision record with the reason attached. Clients see the option we rejected and why, which is usually more useful than the one we chose.

It also means writing decisions down. A decision that lives only in a call is a decision that will be re-litigated in six weeks by someone who was not on it.

Visible strategy exposes when we are wrong, or slow, or when the evidence does not support the recommendation we started with. That is the point. Disagreement surfaced in week two is cheap; surfaced in week ten it is a change order and a strained relationship.

It also requires clients to engage earlier than some expect. The projects that go best are the ones where someone senior reads the diagnostic properly and argues with it.

Put it in the brief. Ask for a written diagnostic before design, a decision record per stage, and a preview environment rather than screenshots. Any studio confident in its reasoning will agree without hesitation; the request itself is a useful filter.

Then hold your side of it. Read the diagnostic properly, argue with the parts you disagree with, and name one person who can approve direction. Visible strategy only works when someone is actually looking.