From Brief to First Sketch

Every project I start has the same dangerous moment: the brief is on the screen, the client is waiting, and the pull to open a design tool is almost physical. I have learned to resist it. The best work I do starts on paper, and it starts slowly.

Read the brief twice

The first read is for the client’s words, the second for what they leave out. I underline nouns and verbs, then write a single sentence that describes the problem without mentioning any solution.

Only after that sentence feels right do I pick up a pencil. The first sketches stay small and fast, so no idea gets precious before it has been compared with the others.

Sketch wide before going deep

I give myself twenty minutes and fill a single sheet with thumbnails. The goal is quantity: layouts, type pairings, crops, even bad ideas that exist only to be crossed out.

Working at this size makes it impossible to polish. You can only decide where things sit and how heavy they feel, which is exactly the conversation a first round should have.

When the sheet is full, I step away for a few minutes. Coming back, two or three thumbnails always look stronger than the rest, and I can usually say why.

Name the constraints

Every project has limits that are easier to design with once they are written down: the format, the budget, the audience, the one thing the piece must never do.

I keep the list short and visible next to the sketches. A good constraint is not a wall, it is a reason to choose one option over another without second-guessing.

• What must the audience understand in the first three seconds?

• Which assets are fixed, and which can change?

• Where will this actually be seen, and at what size?

Test the idea on paper

Before anything moves to the screen, I show the strongest sketches to someone who has not seen the brief. I do not explain them. I only ask what they think the piece is trying to say.

If their answer is close to my one-sentence problem statement, the idea is ready to grow. If not, I return to the thumbnails instead of rescuing a weak direction with polish. This check costs ten minutes and has saved me whole days of refining the wrong thing.

A sketch is a question you can answer quickly. Make enough of them and the right answer shows itself.

Move to the screen with a plan

Once a direction survives the paper test, I rebuild it digitally at a rough fidelity. Grey boxes, placeholder type and real content where I have it. Color comes last.

I keep the sketch beside the screen and compare often. If the digital version drifts from the paper idea, I want to know whether that was a conscious improvement or just the tool pulling me sideways. At this stage I also write down the open questions, so feedback can be directed at the real decisions instead of the surface.

Share early, share small

The first thing a client sees should never be a finished layout. I send two or three rough directions with a short note on the problem each one solves.

Early feedback is cheaper and kinder to everyone. It also turns the project into a shared exploration rather than a reveal, which makes the later rounds calmer. Good feedback tends to sound like a preference for a direction, not a list of tweaks. When I hear tweaks, I ask which goal they are protecting.

Close the loop

When a direction is chosen, I go back to the original brief and read it a third time. Not to check boxes, but to confirm the sketch still answers the sentence I wrote on day one.

Then the real work begins: refining spacing, type and color with a clear idea of what the piece is for. If you want to see how I keep that stage short and focused, read Designing in Small Loops.