Skip to content
All articles

 · 3 min read

Why I build design options instead of drawing them

A mock-up is a picture of a website. Clients don't use pictures; they scroll, skim and give up.

A mock-up is a picture of a website. Clients don't use pictures. They scroll, skim and give up. So when a project needs a direction chosen, I build the options as working pages.

What a static frame hides

Pacing, density and length. A hero that looks calm in a frame can feel empty after two seconds of scrolling. A section that looks rich can take a minute to read. None of that shows until you scroll it on your own phone.

What happened on The Source

The first direction was clean and correct, and the client called it bland. That was useful. The second went bold and editorial. The third started from a blank page, and it is the one they kept. Every round of feedback landed on a working page, so nothing had to be rebuilt from a mock-up at the end.

Is it slower?

Less than it sounds. With an agreed copy document and a small set of components, a homepage direction takes about as long as a polished set of frames, and the one that wins is already half built.

When I still draw

For a logo or a slide, the picture is the product, so I draw. For anything people scroll, I build.