Skip to content

Pick your style: Denkbaar

Book a conversation

Articles

Knowledge

Design first: a clickable journey before you build

A clickable design lets you show and test what you want before there is one line of real code. This is how we work.

Two people test a phone beside sketches of several screens.
Test the whole clickable journey before you build. Illustration: Denkbaar.

With AI, you can build an app in an afternoon. So it is tempting to start building at once. We first make a clickable design of the whole journey, and only build when that is right.

Plain technical English A clickable prototype is a series of screens that you can click through, without real data or logic. Users test the journey on it, from start to end. The prototype is the design; the real code is built separately after it.

Why it matters

A change in a design takes minutes. The same change in built software takes hours, and often more. The UK government writes it in its manual for digital services: you must make prototypes to explore, share and test designs before you commit to building anything. Code prototypes are better for user research there, because they feel more real.

Five screen sketches form a route on a table.
A design shows the journey from first click to result. Illustration: Denkbaar.

How it works

changeapproved

Question and goal

Sketch

Clickable design of the whole journey

Test with users

Build to the design

Compare with the design

You sketch, make the journey clickable, test it, and only build after approval.

A large screen and a phone stand beside two sketches of the same layout.
Compare the built result on phone and desktop with the design. Illustration: Denkbaar.

What you do

  1. Draw the whole journey, not one screen. From the first click to the result.
  2. Make it clickable. We make designs in Claude Design, as clickable screens.
  3. Let someone click through it without explanation. Watch where they get stuck.
  4. Change it until the journey works. That is the approved design.
  5. Do not copy the prototype as production code. The GOV.UK manual says so too: prototype code does not need to meet the same standards. Build the real version separately, with tests.
  6. Compare the result with the design, with screenshots on phone and desktop side by side.

We put a new design that is not yet approved on the site behind its own address, so that the approved version stays in place.

What we can do with you: we make a clickable design of your idea with you, test it, and then build it. Book a conversation.

Sources

  1. GOV.UK Service Manual: Making prototypes

Topics: designprototypesmethod