The scariest words in a project kickoff are: "the client knows what they want." Sometimes they do. Sometimes the brief is a trap — loaded with solutions that describe a problem nobody told us about.
The two kinds of briefs
The recipe brief lists features: "we need a new logo, a website, a motion reel, a social kit". It's an inventory, not a direction.
The truth brief describes the business friction: "our conversion drops after the first scroll". The deliverable isn't specified because it doesn't matter yet.
Our job in the first workshop is always the same — move the conversation from what to why.
How we escape the trap
- Restate the problem out loud — "so the real cost of this issue is €40k/mo in abandoned carts" — watch faces change
- Kill one beloved feature — removing something proves we're consultants, not order-takers
- Give the answer they didn't ask for — sometimes it's not a website at all
If the brief is already the solution, the client has called the architect to build the pyramid. Our job is to ask how big the pharaoh really is.
The relationship survives
Clients who push back on pushback stay. The ones who wanted a mirror? They leave — and the project was doomed anyway. A truth-teller is worth more than a yes-man, every single time.