Why we design one screen before the rest

The usual way to start a design project is to wireframe everything. Every page, every state, grey boxes as far as the eye can see. Then design for everything, then feedback, then more design. Meanwhile the client spends weeks staring at boxes they don't quite believe in. Boxes mean very little to anyone who isn't a designer.

[Invented] I've watched a client scroll through forty wireframes on a call and say "looks good" in the tone you use when you're being polite to a waiter. They weren't excited. They were tired. That's when I stopped trusting wireframes as a way to get people on board. They're a tool for us. They were never meant to be the first thing a client sees.

We start somewhere else, and it starts with the client portal. Contracts, deliverables, timelines, tasks. All of it lives there, and the client sees exactly what we see. It's our progress board, so nobody has to ask which phase we're in.

[Invented] It sounds like admin, and it is. But it changes the mood of a project. When a client can open one page and see what's done, what's next and what's waiting on them, the anxious emails stop. Nobody's guessing. Nobody's chasing us for an update on a Thursday afternoon, and we're not chasing them for feedback they don't know we need.

Then we run a workshop. Branding, web, product, it depends on the job, but the goal never changes. We want to find out what the client really knows about their own brand, their product, their deck. Some exercises are practical. Some are deliberately strange, to get people out of their heads for an hour. We push back. We throw ideas around. We put solutions on the table.

[Invented] One of the strange ones: we ask people to describe their company as if it were a place. A hotel, a workshop, a night market. It sounds silly for about two minutes. Then someone says "actually, we're more of a pharmacy than a hotel" and the whole room leans in, because it's the first honest thing anyone has said all morning. You can't get that from a questionnaire.

A short report goes over for their sign-off, and then we get to work.

[Invented] The report is deliberately short. Two pages, maybe three. What we heard, what we think it means, what we'll do first. We'd rather someone read a short thing and reply "yes, that's right" than skim a long thing and say nothing.

This is where we break from the usual. We don't wireframe the whole thing. We pick one screen, or one page of the website, and go all in on it. Once they approve it, we design the rest.

[Invented] Picking the screen is half the job. We look for the one that carries the most weight, the page where the brand, the product and the pitch all have to show up at the same time. For a website it's usually the homepage. For a product it's often the screen someone sees right after they sign up. If that one works, the rest are variations. If it doesn't, we'd rather know on day ten than day forty.

I like it for a few reasons. The client sees something real from day one, something they can react to without taking our word for it. And it saves us time, because that first piece sets the direction for everything after it.

[Invented] It helps the team too. A designer working on one screen for a week does better work than a designer spread across twelve. You can sweat the type, the spacing, the way the thing feels when you hover over it. And once the client approves it, the rest of the team has a bar to design up to, instead of a list of opinions.

It also shows us fast when we're wrong. And sometimes we are. There have been times we missed on the first try. That's fine. What we show isn't fully polished, so a miss doesn't cost much, and how someone reacts to the wrong screen tells you a lot about what they expect from the right one. A wireframe never gives you that. A moodboard doesn't either.

[Invented] Once we showed a screen we were proud of and the client went still. Then they said, "It's good. It's just not us." We asked what us looked like. Twenty minutes later we had more direction than three rounds of moodboards had given us. The screen was wrong. The conversation it started was the most useful one of the project.

[Invented] The part clients seem to like most is how quickly it gets personal. By the end of the first stretch they're not reviewing a process. They're reacting to their own product, with their own opinions, and arguing for the things they care about. That argument is where the real brief lives. It was never in the kickoff document.

[Invented] It does ask something of us. We have to be willing to be wrong in front of a client, early, on purpose. That's uncomfortable for a studio that likes to look sure. We've decided it's worth the discomfort.

[Invented] That's the whole pattern. Portal, workshop, short report, one screen done properly. Nothing clever. We put something real in front of a client early and let the reaction tell us what to do next.