Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
doubleslashse avatar

Design Thinking

  • 10 installs
  • 4 repo stars
  • Updated June 18, 2026
  • doubleslashse/claude-marketplace

Facilitate human-centered problem solving using the five-phase design thinking methodology for workshops and user research.

About

Provides the five-phase design thinking methodology for human-centered innovation and problem solving. A facilitator uses it when running design workshops or user research sessions.

  • Five-phase human-centered process
  • Balances user needs, technology, and business

Design Thinking by the numbers

  • 10 all-time installs (skills.sh)
  • Ranked #2,198 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/doubleslashse/claude-marketplace --skill design-thinking

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs10
repo stars4
Last updatedJune 18, 2026
Repositorydoubleslashse/claude-marketplace

What it does

Facilitate human-centered problem solving using the five-phase design thinking methodology for workshops and user research.

Files

SKILL.mdMarkdownGitHub ↗

Design Thinking Skill

Overview

Design Thinking is a human-centered approach to innovation and problem-solving. It integrates the needs of people, the possibilities of technology, and the requirements for business success.

The Five Phases

1. Empathize

Purpose: Understand the people you're designing for.

Key Activities:

  • User interviews
  • Observation
  • Immersive experiences
  • Empathy mapping

Outputs:

  • User insights
  • Empathy maps
  • User journey maps
  • Pain points and gains

Key Questions:

  • Who is the user?
  • What do they need?
  • What frustrates them?
  • What delights them?
  • What are their goals?

2. Define

Purpose: Synthesize findings into a clear problem statement.

Key Activities:

  • Insight synthesis
  • Problem framing
  • Point of View (POV) statements
  • "How Might We" questions

Outputs:

  • Problem statement
  • POV statement
  • HMW questions
  • Design challenge

Frameworks:

POV Statement:

[USER] needs [NEED] because [INSIGHT]

How Might We (HMW):

How might we [action] for [user] so that [outcome]?

3. Ideate

Purpose: Generate a wide range of potential solutions.

Key Activities:

  • Brainstorming
  • Mind mapping
  • Sketching
  • SCAMPER technique
  • Worst possible idea

Outputs:

  • Idea bank
  • Concept sketches
  • Clustered themes
  • Selected concepts for prototyping

Rules for Ideation: 1. Defer judgment 2. Encourage wild ideas 3. Build on others' ideas 4. Stay focused on topic 5. One conversation at a time 6. Be visual 7. Go for quantity

4. Prototype

Purpose: Create representations of solutions to explore.

Key Activities:

  • Sketching
  • Storyboarding
  • Role-playing
  • Paper prototypes
  • Digital mockups

Outputs:

  • Prototypes (any fidelity)
  • Storyboards
  • Scenarios
  • Physical or digital models

Prototype Principles:

  • Start rough, refine later
  • Build to think
  • Fail fast, learn faster
  • Prototype to learn, not to prove

5. Test

Purpose: Gather feedback and refine solutions.

Key Activities:

  • User testing
  • Feedback sessions
  • Observation
  • Iteration

Outputs:

  • Feedback synthesis
  • Refined prototypes
  • Iteration plans
  • Validated concepts

Feedback Framework:

  • What I like...
  • What I wish...
  • What I wonder...
  • What if...

Design Thinking Mindsets

1. Human-Centered

Always start with people and their needs.

2. Bias Toward Action

Build to think. Don't just talk about ideas.

3. Radical Collaboration

Diverse perspectives lead to better solutions.

4. Culture of Prototyping

Make ideas tangible early and often.

5. Show, Don't Tell

Use visuals, stories, and prototypes.

6. Mindful of Process

Know where you are in the process.

7. Embrace Ambiguity

Stay open even when unclear.

Workshop Timing Guide

90-Minute Sprint

PhaseTimeFocus
Empathize15 minQuick user perspective
Define10 minProblem statement
Ideate25 minSolution brainstorm
Prototype20 minConcept sketches
Test/Feedback15 minPeer review
Close5 minNext steps

Half-Day Workshop (3 hours)

PhaseTimeFocus
Empathize45 minDeep user research
Define30 minSynthesis + HMW
Ideate45 minMultiple techniques
Prototype45 minMultiple concepts
Test30 minUser feedback
Close15 minActions

Full-Day Workshop (6+ hours)

Extended exploration of each phase with breaks and team exercises.

Common Techniques

Empathy Map

┌───────────────────────────────────────────────────┐
│                     SAYS                          │
│                 (quotes, phrases)                 │
├───────────────────────┬───────────────────────────┤
│       THINKS          │         FEELS             │
│  (beliefs, thoughts)  │   (emotions, reactions)   │
├───────────────────────┼───────────────────────────┤
│        DOES           │                           │
│  (actions, behaviors) │                           │
├───────────────────────┴───────────────────────────┤
│    PAINS              │         GAINS             │
│ (frustrations, fears) │   (wants, needs, goals)   │
└───────────────────────┴───────────────────────────┘

User Journey Map

PHASE:    Awareness → Consideration → Decision → Use → Loyalty
ACTIONS:  [What user does at each stage]
THOUGHTS: [What user thinks]
EMOTIONS: [How user feels - graph line]
PAIN PTS: [Friction points]
OPPTYS:   [Opportunities to improve]

2x2 Matrix for Prioritization

                HIGH IMPACT
                    │
    ┌───────────────┼───────────────┐
    │    DO LATER   │   DO NOW      │
HIGH│               │               │LOW
EFFORT              │              EFFORT
    │   DON'T DO    │   FILL-IN     │
    └───────────────┼───────────────┘
                    │
                LOW IMPACT

When to Use Design Thinking

Best For:

  • Complex, ill-defined problems
  • Human-centered challenges
  • Innovation and new product development
  • Experience design
  • Service design

Less Suitable For:

  • Well-defined technical problems
  • Urgent decisions with no time for exploration
  • Problems with clear, known solutions

See activities.md for detailed activity guides.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.