UX Workshops, Crazy 8s and bonkers 4s

November 11, 2026
Robert Hufton

How to run a Crazy 8s UX workshop in an hour, our Bonkers 4s version for dashboards, and how we turn the sketches into a prototype.

The hardest part of a website or software project is often the start: a room full of people with different ideas, and no quick way to get them onto the table. Crazy 8s is the workshop exercise we use most to fix that. It takes about an hour, needs nothing more than paper and pens, and gets everyone, not just the loudest person, contributing ideas you can actually build.

Here's how it works, the variation we created for dashboards and software, and how we turn the sketches into a prototype.

What is Crazy 8s?

Crazy 8s comes from the Design Sprint method popularised by Jake Knapp at Google Ventures, and it's one of the core exercises in Google's Design Sprint Kit. Each person folds a sheet of paper into eight panels and has eight minutes to sketch eight different ideas for the same problem, roughly one a minute.

The time pressure is the point. The first two or three ideas are usually the obvious ones. By the fifth or sixth, people are past the safe answers and into more interesting territory. Because everyone sketches alone and at the same time, nobody gets anchored to the first idea said out loud.

What it works well for

It suits any focused design problem, such as a landing page, a mobile booking journey, a quote form, a navigation menu, a checkout, or a single product feature. For Fettle, whose Webflow site was built around booking a bike service, the booking journey was exactly this kind of problem. Getting it right helped the conversion rate quadruple within months of launch.

Why we created Bonkers 4s

Crazy 8s works brilliantly for mobile screens. It's cramped for complex desktop software, where a single screen might hold navigation, filters, data tables and alerts.

So for dashboards and data-heavy platforms we use a variation we call Bonkers 4s: four larger landscape panels, about two minutes each. There's enough room to sketch a whole screen layout without slowing the exercise down. We used this approach when designing telematics dashboards for Wrightbus, where the challenge was making large amounts of fleet data readable at a glance. Our SaaS UX design page shows more of that work.

How to run a Crazy 8s workshop

Allow 60 minutes and up to about eight people. Include someone who talks to customers every day, such as sales or customer service. They often have the best ideas.

1. Agree one clear challenge (10 minutes)

Phrase it as a question: "How might we help a homeowner understand which service is right for them?" or "How might we make this dashboard easy to understand on day one?" Share any evidence you have first: analytics, customer comments, screenshots of the current version.

2. Sketch (8 minutes)

Fold, set a timer, sketch. Remind everyone that drawing ability doesn't matter. Boxes, arrows and a few words are enough. Call out each minute so people keep moving.

3. Share (15 minutes)

Stick everything on a wall and give each person a minute to explain their sketches. No debate yet; just questions to understand.

4. Vote (10 minutes)

Give everyone three dot votes to put on the ideas, or parts of ideas, they think are strongest. The winner rarely comes from one sheet. More often it's a combination: one person's layout, another's call to action, a third's way of showing prices.

5. Decide what to prototype (15 minutes)

Agree the one or two concepts to take forward, and what you need to learn from them.

Want us to run a workshop with your team? Get in touch and we'll plan one around your problem.

Running it remotely

It works on video calls too. Ask everyone to sketch on paper and hold it to the camera or photograph it, or use a whiteboard tool like Miro or FigJam with an eight-panel template. Keep cameras on during the sketching so the energy doesn't drop.

From sketches to a prototype

A workshop is only useful if something happens next. Within a few days we turn the winning ideas into a clickable prototype in Figma, so the team can see it working and show it to a few customers before anything is built. This is where problems show up cheaply. Our post on why UX prototyping is useful covers that step in more detail, and our UX design service is built around it.

It's also where AI now speeds things up. In a recent session with a construction client, we took his existing Word proposal and CAD drawings and turned them into an interactive prototype the same day. Our AI and UX consultancy page shows the result, and you can try it yourself.

Common mistakes

Starting without a clear problem. Letting a senior person present their idea first. Debating ideas during the sketching. And ending the session without agreeing what happens next. Avoid those four and the exercise almost always works.

Have a design problem your team keeps going round in circles on? Talk to us. A one-hour workshop is often the fastest way out.

Sources

More UX & CRO insights