What Is Design Thinking and How Can You Use It to Generate Ideas Faster?

Updated 2026-10-06

Design thinking is a structured way to solve problems by starting with the people affected and working toward ideas you can test. You can use it to generate value-based ideas faster by compressing the ideation phase into a short, time-boxed routine — often 30 minutes or less — and using gamification to keep a team engaged and cooperative. This approach fits best when you have a vague problem, a small team, and no appetite for a long research cycle. It fits poorly when the problem is already well-defined and you just need to execute.

The Core Stages in Plain Terms

Design thinking is usually described in five stages. They are not a rigid sequence — you loop back as you learn.

Stage	What you actually do	Output
Empathize	Talk to or observe the people who have the problem	Notes on what they feel, say, and struggle with
Define	Turn those notes into one clear problem statement	A sentence describing whose problem and why it matters
Ideate	Generate many possible solutions without judging them yet	A long list of candidate ideas
Prototype	Build the cheapest version that lets someone react	A sketch, mockup, or rough script
Test	Put it in front of real people and watch what happens	Evidence for what to keep, change, or drop

The stage most teams rush is define. If your problem statement is vague, every idea afterward will be vague too. A useful test: can two people read your problem statement and agree on what would count as a good solution?

Why Gamification Speeds Up Ideation

The ideation stage fails for predictable reasons: people self-censor, one voice dominates, and the group converges on the first decent idea. Gamification addresses each of these by changing the rules rather than the people.

Time pressure forces quantity over polish. A short round produces more raw material than an open-ended discussion.
Turn-taking rules stop the loudest person from filling the room.
Scoring or constraints make unusual ideas feel like winning rather than risk-taking.
Visible progress keeps energy up when the problem is hard.

Myndset, a tool built for the ideation phase of a business idea or product, applies gamification specifically so that "everybody can be a creator" — the point is to lower the barrier to contributing, not to make ideation feel like a competition you can lose.

A 30-Minute Ideation Routine

This routine turns a vague problem into value-based ideas you can act on. It assumes a small group (3–6 people) and a problem you have at least some direct knowledge of.

Before you start (5 minutes, one person): Write the problem as a single sentence in the form "How might we help [who] do [what] so that [why it matters]?" Bring it to the session. If you cannot fill in the "who," spend the first minutes of the session on that instead.

Minutes 0–5 — Frame. Read the problem statement aloud. Ask each person to say one thing they know about the people affected. Write these where everyone can see them. This is the empathize-and-define step compressed.

Minutes 5–15 — Diverge. Run two or three short rounds. Each round has a constraint, for example: ideas that cost nothing, ideas that take under a day, ideas that would embarrass you to propose. Everyone writes in silence, then reads one idea each in turn. No criticism during this block.

Minutes 15–25 — Converge. Group the ideas by theme. For each theme, ask: who benefits, and what would have to be true for this to work? Keep the ideas where you can name a specific beneficiary. Those are your value-based candidates.

Minutes 25–30 — Pick and commit. Choose one or two ideas to prototype. Assign one person and one deadline. The prototype should be something a real person can react to within a few days.

How to verify it worked: you should end with a written problem statement, a list of ideas grouped by theme, at least one named beneficiary per surviving idea, and one assigned prototype. If you have ideas but no named beneficiary, you are not done.

Common Sticking Points

The problem statement keeps changing. That usually means you skipped real empathy work. Go talk to two people before the next session.
One person generates everything. Add a silent-writing round before any discussion. It is the single most effective fix.
Ideas all sound the same. Change the constraint. "Ideas that cost nothing" and "ideas that take under a day" produce different thinking than "ideas that scale."
The group picks the safest idea. Ask what the idea would look like if it had to be ten times bolder, then ask what part of that is actually feasible this week.
Nobody wants to prototype. Shrink the prototype until it feels trivial. A sketch or a two-line script counts.

Team Dynamics Matter More Than the Method

The stages are easy to learn; the cooperation is what determines whether you get useful ideas. The evidence around team ideation points to a few things worth building deliberately:

Cooperation over solo work. Groups that build on each other's contributions produce more original combinations than individuals working alone — but only if contributions are visible to everyone.
Stronger bonds. Shared creative work builds trust faster than status updates, which makes later disagreement easier to handle.
Better dialogue. Structured turn-taking turns conversation into something where quieter members actually speak.
Aligned vision. When everyone helps shape the problem statement, they stop arguing about goals later.

The practical takeaway: do not go solo on the ideation step if you have a team available. Even one other person changes the quality of what you produce.

Start Today

Pick one real problem you are facing. Write it as a "How might we" sentence. Set a 15-minute timer and generate ten ideas under a single constraint. Circle the ones where you can name who benefits. That is the whole loop — the five stages and the gamification are just ways of making it repeatable and keeping a team in it.