myndset.cards

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.

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.

Gamification and design thinking speed up startup ideation by replacing open-ended brainstorming with short, structured activities that have rules, turns, and a visible finish line. Myndset, a tool built for the ideation phase of a business or product idea, applies gamification to this process and states that anyone can be a creator and that ideas can be produced in 30 minutes or less. The approach fits early-stage founders, small teams, and solo entrepreneurs who want a discussable concept quickly rather than a polished business plan.

Why the two methods work together

Design thinking supplies the structure: understand a problem, generate options, and converge on something testable. Gamification supplies the motivation and pace: rules, constraints, and a time box turn vague "let's brainstorm" sessions into activities people actually finish.

The combination matters most at the fuzzy front end of a startup, where the failure mode is not a lack of ideas but too many unstructured ones and no shared direction.

What a 30-minute ideation session looks like

Myndset's stated promise is creating value-based ideas in 30 minutes or less. A practical session built on that premise:

1. Set the frame (2–3 min). Write one sentence naming the user and the problem. Everything generated must connect to it.
2. Generate under constraints (10–12 min). Use a card or prompt format with a rule such as "one idea per turn" or "build on the previous card." Constraints reduce blank-page paralysis.
3. Build on each other (8–10 min). Instead of defending your own idea, add to someone else's. This is where cooperation, not competition, produces stronger concepts.
4. Converge (5 min). Pick the one or two ideas the group can describe in a single sentence.
5. Name the next check (2 min). Decide what evidence would make the idea worth pursuing.

The output is not a plan. It is a small set of ideas specific enough to discuss with a co-founder, mentor, or potential user.

The collaboration element is not optional

Myndset's page headings point in one direction: Team Progress via Cooperation, Building Stronger Bonds, Enhancing Dialogues, Aligning Shared Visions, and a blunt closing line, Don't go solo.

That last point is the practical takeaway. Solo ideation tends to loop: you generate, judge, and discard inside your own head, and the same assumptions survive every round. A second person forces ideas into language, exposes gaps, and surfaces directions you would not have reached alone. Even one collaborator changes the quality of the output.

How to tell if an idea is worth continuing

You do not need a full validation framework at this stage. Use a short filter:

• Specific user: Can you name who has this problem, not just a demographic?
• Real pain: Is the problem frequent or expensive enough that someone would change behavior?
• One-sentence clarity: Can you explain the idea without jargon?
• A cheap next test: Is there a low-cost way to check one assumption — a conversation, a landing page, a manual version?

If an idea fails the first two, return to generation rather than investing in refinement.

Limits to keep in mind

Gamified ideation produces candidates, not validation. A session that feels productive can still yield ideas nobody wants. Treat the 30-minute output as input to customer conversations, not as evidence.

Also note what the source does not specify: Myndset's page mentions "subscribe" among its keywords but lists no pricing links or payment platforms, so cost and access terms are not established here. Check the site directly before assuming it is free.

The method itself, however, is portable. You can run a structured, time-boxed, collaborative ideation session with cards, prompts, or a whiteboard — the tool accelerates it, but the rules are what make it work.

Creativity is the practice of turning an idea into something that exists outside your head — a drawing, a song, a 3D model, a short program, an edited photo. It is a learnable habit rather than a fixed talent, and you can start today with nothing more than a browser and an internet connection. This guide is for beginners who want to understand what creativity actually involves and pick a first medium to work in.

What creativity really is

Most people treat creativity as a personality trait: you either have it or you don't. A more useful definition is that creativity is a loop you repeat:

1. Notice something — a problem, a mood, an image you can't shake.
2. Make a rough version of it, badly at first.
3. Look at what you made and decide what to change.
4. Revise and repeat.

The loop matters more than the output. A first attempt that looks wrong is not a failure; it is the raw material for the next pass. This is why creative skills improve with regular short sessions rather than rare long ones.

Common creative outlets and what each one asks of you

Different media suit different temperaments. The table below maps each outlet to the kind of thinking it rewards, so you can pick a starting point that fits how you already like to work.

If you feel stuck choosing, pick the one where you already consume the most work. People who watch a lot of video tend to take to video editing faster; people who draw in margins tend to take to painting.

Starting with browser-based tools

The main barrier to starting used to be software: expensive licenses, large downloads, and hardware requirements. Browser-based creative apps remove most of that. Sumo, for example, offers a suite of web apps covering painting, music, 3D, coding, photo, audio, video, and pixel art, all accessible from a modern device — mobile, tablet, or computer — with internet access.

A few practical notes on this approach:

• No install step. You open the app and start. That shortens the gap between deciding to create and actually creating.
• Cross-device. Work started on a laptop can often be continued on a tablet, which helps when you want to sketch on the couch and refine at a desk.
• Learning curve varies by app. Painting and photo editing are usually the gentlest entry points; 3D modeling and coding ask for more patience before results look satisfying.

The suite is described as gamified and easy to learn, with the stated goal of making creative tools accessible to everyone. Treat that as a design intention rather than a guarantee — your own experience will depend on the medium you choose.

A simple first-week plan

You do not need a curriculum. You need a small, repeatable loop.

1. Pick one medium from the table above. Commit to it for a week.
2. Set a 20-minute session. Short enough that you won't skip it, long enough to make something.
3. Make something small and finish it. A single sprite, an eight-bar loop, a one-clip video edit. Finished beats perfect.
4. Save or export your work. Most of these apps support saving or exporting (for example, MP3 export for music, WAV or MP3 for audio, video file export for video). Having a file at the end makes the session feel real.
5. Note one thing to change next time. This is the revision step of the loop, written down so you don't lose it.

After a week, you will know two things: whether the medium holds your interest, and whether the tool fits your device and workflow. If either answer is no, switch — that is not quitting, it is narrowing down.

Common sticking points

• "My work looks bad." Early work looks bad for everyone. The comparison that matters is your work today against your work last week.
• "I don't know what to make." Copy something. Remixing existing work is a standard way to learn; Sumocode, for instance, explicitly offers sample code you can remix, and Sumotunes lets you remix other users' songs.
• "I don't have the right equipment." A browser and a modern device are enough to begin. Upgrading hardware is a later decision, not a prerequisite.
• "I keep starting over." Finish the small thing even if you dislike it. The revision loop only works if there is a version one to revise.

Choosing your starting point

If you want the fastest visible progress, start with photo editing or pixel art — both give quick before-and-after feedback. If you want a skill that compounds over months, painting or coding rewards sustained practice. If you are drawn to physical output, 3D modeling connects to printing. Whichever you choose, the mechanism is the same: pick a medium, make something small, look at it, change one thing, repeat.

Gamification means applying game mechanics — points, levels, challenges, feedback loops — to non-game contexts like work, learning, or brainstorming. It works when the underlying task has real value and the mechanics make progress visible or social. It backfires when you bolt rewards onto meaningless work, or when rewards crowd out the intrinsic motivation people already had. The sections below cover the core motivational levers, how to apply them to a real task, and how to choose mechanics that match your goal.

The core mechanics, and what each one actually does

Gamification is not "adding badges." Badges are one output; the mechanism behind them is what changes behavior. Four levers do most of the work:

The key insight: progress and feedback are informational — they tell you where you stand. Cooperation and competition are social — they change how you relate to others. Most failed gamification projects pick a social lever (leaderboards) when the actual problem was informational (people didn't know if they were improving).

Applying it to a real task: a team brainstorming session

Take a concrete case: a team that needs to generate and select business or product ideas, and tends to either stall or let one loud voice dominate. Here's how the levers map onto that task.

1. Define the win condition before adding anything

Decide what "done" looks like. For ideation, that's usually a set of candidate ideas that the team agrees are worth pursuing — not a pile of sticky notes. If you can't state the win condition in one sentence, no mechanic will fix the session.

2. Use cooperation to surface everyone's input

A cooperative structure means the team's score depends on collective contribution, not individual brilliance. Practical moves:

• Shared progress: Track how many distinct ideas the group has generated against a target, visible to everyone.
• Mutual dependency: Require each idea to be built on or combined with someone else's before it counts toward the group total. This forces dialogue rather than parallel monologues.
• Team-level status: Recognize the group's progress, not individual winners, during the session.

This is the lever Myndset leans on: its stated approach centers on team progress through cooperation, building stronger bonds, enhancing dialogues, and aligning shared visions — with an explicit "don't go solo" framing. That's a cooperation-first design, which fits ideation where the goal is alignment, not a single winner.

3. Add feedback, not just scoring

Feedback is what makes the loop work. In a brainstorming session, that means reacting to ideas in the moment — building on them, asking a clarifying question, or noting why one is stronger — rather than collecting everything and judging at the end. Immediate, specific reactions keep people generating; a silent room followed by a verdict does the opposite.

4. Reserve competition for the selection phase

Competition is useful when you need to narrow options, not when you need to generate them. Early competition suppresses risk-taking; late competition sharpens choices. So: generate cooperatively, then let ideas compete (a vote, a scoring rubric, a head-to-head comparison) once there's a pool worth choosing from.

Choosing the right mechanic for your goal

Match the lever to the outcome you actually want:

• Solo habit or skill-building → progress tracking plus immediate feedback. Streaks and levels work here because the loop is fast and personal.
• Team bonding or alignment → cooperation. Shared goals and mutual dependency, as in the brainstorming example above.
• Short-term energy or skill comparison → competition. Keep it time-boxed so the leaderboard resets and doesn't calcify.
• Learning or practice → feedback first, everything else second. Without a tight feedback loop, points are just decoration.

If two goals conflict — say you want both bonding and ranking — run them in sequence, not simultaneously. Cooperation to generate, competition to select.

Common pitfalls

• Gamifying work that has no intrinsic value. If the task is genuinely pointless, points make it feel manipulative rather than fun. Fix the task first.
• Over-rewarding. Large or frequent extrinsic rewards can displace the internal motivation people already had. Small, informational feedback usually outperforms big prizes.
• Confusing activity with progress. A streak that rewards opening an app is not the same as one that rewards real output. Make sure the metric maps to the outcome you care about.
• Leaderboards as a default. They're the most visible mechanic and the most likely to demotivate the majority. Use them only when the goal is genuinely comparative and short-term.
• No feedback loop. Points without meaning are noise. Every mechanic should tell the participant something true about how they're doing.

A quick way to start

Pick one task you or your team avoids. State the win condition in one sentence. Choose one lever — progress if it's solo, cooperation if it's a team, competition if you need to narrow options. Add immediate feedback so people know where they stand. Run it once, then check whether the mechanic changed behavior or just added decoration. If it didn't change behavior, the mechanic was wrong for the goal, not the other way around.

IDEO is a global design and innovation firm known for popularizing human-centered design and for turning design thinking into a repeatable process that product teams, startups, and entrepreneurs can borrow. Its influence shows up most clearly in three practices: framing problems around real user needs, generating many ideas through structured brainstorming, and testing rough prototypes early. If you want faster, more user-grounded idea generation, IDEO's methods are a useful reference — but they work best when you actually talk to users and iterate, not when you treat them as a checklist.

What IDEO is

IDEO is a design consultancy that works across product design, service design, digital experiences, and organizational innovation. Its reputation rests on a human-centered approach: instead of starting from technology or a business model, teams start by observing how people actually behave, what they struggle with, and what they need but can't articulate.

That orientation is why IDEO is so often mentioned alongside design thinking. The firm didn't invent every element of the method, but it did a great deal to make it accessible to non-designers — through project work, teaching, and widely read material on the topic.

How IDEO shaped design thinking

Design thinking, as IDEO practices and teaches it, is usually described as a loop rather than a straight line. The common stages are:

• Empathize — observe and interview the people you're designing for.
• Define — turn raw observations into a clear problem statement.
• Ideate — generate a wide range of possible solutions.
• Prototype — build quick, low-fidelity versions of the most promising ideas.
• Test — put prototypes in front of users and learn what fails.

Two things distinguish the IDEO-style version from a generic five-step diagram. First, the stages are iterative: testing often sends you back to redefine the problem. Second, the process is explicitly collaborative — it assumes a mix of disciplines in the room, because a single perspective tends to produce a single kind of idea.

IDEO's idea-generation methods

Brainstorming with rules

IDEO-style brainstorming isn't a free-for-all. It typically enforces a few constraints that raise output quality:

• Defer judgment — no criticism while ideas are being generated.
• Encourage wild ideas — extremes often contain the seed of a workable concept.
• Build on others' ideas — "yes, and" rather than "no, but."
• Stay focused on the question — one clear prompt per session.
• Go for quantity — more ideas increase the odds of a strong one.

Rapid prototyping

The point of a prototype is to answer a question, not to look finished. A paper sketch, a role-play, or a clickable mockup can all serve. The faster you can put something in front of a user, the faster you find out whether your assumption holds.

Cross-disciplinary teams

IDEO projects typically combine designers with engineers, researchers, and sometimes psychologists or business specialists. The friction between different ways of thinking is treated as productive rather than a problem to smooth over.

Applying IDEO's approach to your own project

You don't need a consultancy to use the core logic. A practical sequence for a small team or solo founder:

1. Pick a real user and watch them. Spend time with people who'd actually use your product. Note workarounds, frustrations, and things they take for granted.
2. Write a problem statement in one sentence. Frame it around the user, not your solution. "New parents can't tell whether a baby's cry means hunger or discomfort" is more useful than "build a cry-analysis app."
3. Run a timed ideation session. Set a prompt, apply the brainstorming rules above, and aim for volume before filtering.
4. Choose two or three ideas and prototype them cheaply. Match the fidelity to the question you're asking.
5. Test with the same kind of user you observed. Record what surprised you, then decide whether to refine, pivot, or redefine the problem.

The verification step is simple: if your prototype changes what you believe about the user, the loop is working. If it only confirms what you already thought, you probably tested too late or asked leading questions.

Common sticking points

• Skipping empathy. Teams often jump to ideation because it feels more productive. Ideas generated without user contact tend to solve imagined problems.
• Treating design thinking as a fixed pipeline. The value is in looping back, not in completing five stages in order.
• Prototyping too polished. A high-fidelity prototype invites feedback on appearance instead of on the underlying concept.
• Ideating alone. As the Myndset material on team progress puts it, "Don't go solo" — cooperation, stronger bonds, and aligned shared visions are part of what makes group ideation work. Diverse input is a feature, not overhead.

Why this matters for entrepreneurs and product teams

IDEO's lasting contribution isn't a proprietary tool — it's a stance: start with people, generate broadly, test cheaply, and expect to revise your framing. That stance scales down to a two-person startup and up to a large organization. If your goal is to generate ideas faster, the speed comes less from rushing the ideation step and more from shortening the loop between observing a user, building something rough, and learning whether you were right.