Most design processes fail in exactly the same place: the murky middle, where a promising concept dissolves into seventeen half-finished variations and a Slack thread nobody will re-read. We know, because we lived there for years. The way out was not a new tool. It was a rhythm — five beats, always in the same order, with clear exits.
Beat one: the one-page brief
If the brief does not fit on one page, the thinking does not fit in our heads. Ours has five lines: the reader, their job, the one action, the proof we will show, and what success looks like in a number. Clients initially resist the constraint; by week two they defend it fiercely.
Beat two: sketches before screens
Paper first, always. Thirty minutes, six thumbnails each, no erasing. Sketching keeps ideas cheap while they are still fragile — a bad layout costs a minute on paper and a day in code. We photograph the wall of sketches and attach it to the project; months later it is usually the best documentation we have.
Beat three: the written critique
Feedback arrives in writing before anyone speaks. Each reviewer answers three prompts — what works, what confuses, what is missing — in full sentences. It kills the loudest-voice problem dead, and the notes become a decision log we can revisit when scope creeps back wearing a false moustache.
Beats four and five: build small, launch smaller
We build the riskiest screen first, in the browser, with real content. Then we launch the smallest version that keeps its promises and improve in public. Two quiet disciplines — real content early, small launches often — have saved more projects than any workshop ever did.
Audit your own process against the five beats this week. You will find one beat missing and one beat bloated; fix those two and leave the rest alone. Sharp enough beats perfect, every single launch.
