Prototyping: Thinking in clicks, not just screens

Prototyping is where design starts to feel real. It turns static screens into connected experiences and gives you something to test, share, and poke at before any code is written. I use prototypes to explore interactions, test assumptions, and get fast feedback. They help spot friction early, align teams quickly, and bring ideas to life in a way slides and static mockups never can.

Why I Use Them

Prototypes make conversations better. When you can click through a journey, it’s easier to see what works and what doesn’t. For sos.dance I built a rough prototype of the dashboard experience to test layout and interaction patterns. Within a day, we uncovered a confusing toggle and reworked it before design time was wasted.

They’re also great for involving non-designers. Northern Rail, a clickable prototype helped PMs and engineers flag edge cases we hadn’t thought of yet. It wasn’t about polish, it was about clarity and momentum.

Prototyping Wireframes

I often start by prototyping directly from wireframes. It speeds things up and keeps the focus on flow, not final UI. For sos dance, I connected a low-fi wireframe to naviagtion and pattern logic. Seeing it in motion helped the team agree on the flow before any styling began.

For more layered products like Northern Rail, I’ll build out clickable wires with branching paths and real content. This gives a solid sense of interaction early on and lets us test logic before screens are even styled. Prototyping wireframes saves time later by surfacing gaps early.

From Prototype to Product

A prototype is only as useful as what comes next. I always link prototyping to a clear decision, is this ready to build, ready to test, or still too rough?

For, the prototype moved straight into specs. We added annotations, states, and edge cases to turn it into a working blueprint. In other cases, like the prototype for Protientech, the prototype stayed light. It was there to explore and learn, not lock things down.

That flexibility is why I use prototyping as a core method. It’s not just about showing the work, it’s about shaping it.

Why It Matters

Prototyping helps ideas grow fast without getting stuck in the details too soon. It gives structure to early thinking, invites better feedback, and builds confidence in what we’re designing.

For me, it’s not an extra step, it’s how I think through problems, with the user in mind from the start.