Menu

UX

Design Studios

A practical UX method for rapidly generating, sharing, and refining ideas in a structured workshop so teams can align on better directions quickly.

How to use design studios to explore multiple concepts fast, align teams around promising ideas, and move from discussion to design direction.

4 min read

What it is

Design studios are a UX method where teams rapidly generate, sketch, and critique ideas in a structured workshop format.

They bring together designers, , and sometimes users to explore multiple solutions quickly.

The is iterative, with participants sketching ideas, sharing them, and building on each other’s work.

The focus is on quantity, diversity, and collaboration rather than polished outputs.

The goal is to explore different directions, align teams, and move quickly towards better solutions.

Design studios are most useful when teams need to explore a broad solution space quickly before committing to one direction.

When to use it

Use this method when you need ideas and quickly.

It is most useful when:

You are exploring design concepts
You want input from multiple perspectives
You need to align teams on direction
You are working on complex problems
You want to generate a range of ideas

It is less useful when:

You already have a clear solution
The problem is very simple
Participants lack context or understanding
Design studios are often used in early design and concept phases.

Key takeaway

Use design studios when speed, collaboration, and idea diversity are more important than producing polished outputs in the session itself.

How to run it

Set up properly

Be clear on the problem and the before anybody sketches. A design studio without constraints produces ideas that cannot be built.

Get the group right: six to eight people, including somebody who knows what is technically feasible.

Run the method

A design studio runs timed rounds of individual sketching followed by group critique. The structure exists to get several genuinely different concepts onto the table before anybody commits.

  1. Introduce the problem and the , and check everybody has understood them the same way.
  2. Run timed sketching rounds individually. Time pressure is what stops people polishing a first idea instead of having a second.
  3. Have each participant present their ideas briefly, without apologising for the drawing.
  4. Critique and on concepts as a group, focusing on the idea rather than the execution.
  5. Iterate through several rounds, carrying the strongest elements forward and discarding the rest.

Keep the rounds short and the critique structured. Both prevent the becoming a discussion, which is what it reverts to whenever the timer stops.

Capture and make sense of it

The value comes from breadth before commitment. After the , document:

  • The concepts generated and what distinguished each
  • Elements carried forward, and the reasoning
  • Ideas rejected and why, which prevents them returning
  • The direction agreed and what still needs resolving

Use this when a team is circling one solution. It is a fast way to prove whether that solution is the best of several or simply the first.

What to look for

Focus on:

Alternatives: whether the first idea was genuinely challenged
Breadth: how genuinely different the concepts are from each other
Patterns: common themes across ideas
Innovation: new or unexpected approaches
Carried elements: the parts of losing concepts worth keeping

Where it goes wrong

Most issues come from:

If it’s not structured, it won’t deliver.

Sketching without constraints, producing ideas nobody can build
Letting the timer slip, at which point people polish one idea
Critiquing the drawing rather than the concept
Running one round, which returns the first idea with more confidence
Leaving without a decision about what carries forward

What you get from it

Done properly, this method gives you:

Several genuinely different concepts in a couple of hours
A documented reason for the direction chosen
Ideas rejected with the reasoning, so they do not return
Alternatives on the table before commitment

Key takeaway

It helps you move quickly and confidently.

Get in touch

If this sounds like something you need, we can help you run design studios that generate strong ideas and align your team.

No guesswork. No assumptions. Just fast, effective collaboration.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What are design studios in UX?

They are collaborative workshops for generating and refining ideas.

When should you use design studios?

When a team has settled on a problem but is circling a single solution. A studio puts several alternatives on the table in a couple of hours, which is far cheaper than discovering those alternatives after the first idea has been built.

Who should be involved?

Anyone who can put a solution on paper, and anyone who knows the constraints: designers, a product owner, an engineer who can say what is buildable. Keep it to six or eight; beyond that, sketching time turns into presenting time.

What do you get from a design studio?

Several genuinely different concepts in a couple of hours, and a documented reason for the one you take forward. The value is in the breadth: a studio forces alternatives onto the table before a team commits to the first idea anyone sketched.

Do design studios improve UX?

Yes. They help explore better solutions quickly.

Quick take

If you want fast ideas and team alignment, run a design studio.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer