关于 design-thinking
为设计思维任务提供以人为本的创新方法指南,适合规划和主持设计工作坊。内容按同理、定义、构思、原型和测试五个阶段组织,并附有练习与模板。
主要功能
- 01覆盖设计思维五个阶段
- 02提供访谈与同理心方法
- 03包含构思技巧和练习模板
- 04提供原型及测试规划模板
- 05附半日和全天工作坊议程
适用场景
- 01规划以用户需求为中心的创新项目
- 02组织跨职能设计思维工作坊
- 03将研究发现转化为问题陈述
- 04通过原型测试迭代产品概念
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ melodic-software/ claude-code-plugins --skill design-thinking安装后在 Claude Code 中输入/design-thinking确认已加载。
详细介绍
设计思维
何时使用此技能
适用于以下场景:
- 设计思维任务 - 运用以人为本的创新设计思维方法。涵盖 IDEO/斯坦福 d.school 的 5 阶段方法(共情、定义、构思、原型、测试),包括工作坊引导和练习模板
- 规划或设计 - 需要设计思维方法方面的指导
- 最佳实践 - 希望遵循成熟的模式和标准
概述
一种以人为本的创新方法,将人们的需求、技术的可能性以及业务成功的要求融为一体。
什么是设计思维?
设计思维是由 IDEO 开发并在斯坦福 d.school 教授的一种问题解决方法。它强调理解用户、挑战假设、重新定义问题,并通过反复制作原型和测试来创造创新解决方案。
核心原则
| 原则 | 说明 |
|---|---|
| 以人为本 | 从人出发,而不是从技术或流程出发 |
| 拥抱模糊性 | 在早期阶段从容面对不确定性 |
| 注重行动 | 通过实践学习,而不只是思考 |
| 深度协作 | 跨职能协作,汇聚多元视角 |
| 快速迭代 | 快速试错、快速学习、快速改进 |
5 个阶段
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
│ │ │ │ │ │ │ │ │ │
│EMPATHIZE│→│ DEFINE │→│ IDEATE │→│PROTOTYPE│→│ TEST │
│ │ │ │ │ │ │ │ │ │
│Understand│ │Frame the│ │Generate │ │Build to │ │Learn & │
│the user │ │problem │ │ideas │ │learn │ │refine │
└─────────┘ └─────────┘ └─────────┘ └─────────┘ └─────────┘
▲ │
└────────────────── Iterate ─────────────────────────┘
各阶段的特点
| 阶段 | 模式 | 关键问题 | 产出 |
|---|---|---|---|
| 共情 | 发散 | 用户正在经历什么? | 洞察、观察 |
| 定义 | 收敛 | 核心问题是什么? | POV 陈述 |
| 构思 | 发散 | 有哪些可能的解决方案? | 想法、概念 |
| 原型 | 收敛 | 如何将其具象化? | 原型 |
| 测试 | 学习 | 哪些有效,哪些无效? | 经验证的学习成果 |
阶段 1:共情
深入了解用户及其体验。
共情方法
| 方法 | 时长 | 参与者 | 最适用场景 |
|---|---|---|---|
| 用户访谈 | 30-60 min | 1:1 | 深入了解个人情况 |
| 观察 | 数小时至数天 | 实地工作 | 自然行为 |
| 共情地图 | 15-30 min | 工作坊 | 综合研究成果 |
| 用户旅程图 | 1-2 小时 | 工作坊 | 可视化体验 |
| 跟随观察 | 半天 | 实地工作 | 了解工作流 |
共情地图模板
## Empathy Map: [User/Persona Name]
### Says
[Direct quotes from interviews/observation]
- "[Quote 1]"
- "[Quote 2]"
### Thinks
[What might they be thinking? Hopes/fears?]
- [Thought 1]
- [Thought 2]
### Does
[Actions and behaviors observed]
- [Behavior 1]
- [Behavior 2]
### Feels
[Emotional state, what worries/excites them]
- [Emotion 1]
- [Emotion 2]
### Pains
[Frustrations, obstacles, risks]
- [Pain 1]
- [Pain 2]
### Gains
[Wants, needs, measures of success]
- [Gain 1]
- [Gain 2]
访谈指南结构
## User Interview Guide
**Duration:** 45-60 minutes
**Objective:** [What we want to learn]
### Opening (5 min)
- Introduce yourself and purpose
- Explain confidentiality, recording consent
- "There are no right or wrong answers"
### Context (10 min)
- Tell me about your role/day-to-day
- How long have you been doing [X]?
- Walk me through a typical [scenario]
### Deep Dive (25 min)
- Tell me about a time when [specific experience]
- What was the most challenging part?
- What did you try? What happened?
- How did that make you feel?
### Needs & Desires (10 min)
- If you could wave a magic wand, what would change?
- What would that enable you to do?
- What does success look like for you?
### Closing (5 min)
- Is there anything else you'd like to share?
- Can we follow up if we have questions?
阶段 2:定义
综合观察结果,明确真正的问题。
观点(POV)陈述
## POV Statement
**User:** [Specific user type/persona]
**Need:** [Verb - what they need to do]
**Insight:** [Because - surprising insight about why]
---
**Full Statement:**
[User] needs to [need] because [insight].
**Example:**
A busy working parent needs to quickly prepare healthy meals
because they want to model good eating habits for their children
but feel guilty about the time-cost tradeoff.
我们如何才能(HMW)问题
将 POV 转化为可行动的机会陈述:
## How Might We Questions
**POV:** [Your POV statement]
### HMW Brainstorm
Generate HMW questions by asking:
| Lens | Question | HMW |
|------|----------|-----|
| **Amplify the good** | What's working? | HMW do more of [good thing]? |
| **Remove the bad** | What's painful? | HMW eliminate [pain point]? |
| **Explore the opposite** | What if we flipped it? | HMW [opposite approach]? |
| **Question assumptions** | What's assumed? | HMW if [assumption] wasn't true? |
| **Change status quo** | What's expected? | HMW change when/where/who? |
| **Break it into parts** | What are components? | HMW address just [component]? |
### Selected HMW Questions
1. HMW [question 1]?
2. HMW [question 2]?
3. HMW [question 3]?
**Priority HMW:** [The one to ideate on]
阶段 3:构思
生成各种各样的创意解决方案。
构思规则
| 规则 | 说明 |
|---|---|
| 暂缓评判 | 头脑风暴期间不批评 |
| 追求数量 | 想法越多,点子越好 |
| 在他人想法的基础上拓展 | “是的,而且……” |
| 鼓励大胆设想 | 放开思路,不设限制 |
| 视觉化表达 | 画草图,不要只靠口头讨论 |
| 聚焦一场对话 | 倾听、拓展、接续发挥 |
| 保持专注 | 将 HMW 问题放在显眼处 |
头脑风暴会议模板
## Ideation Session
**HMW:** [The How Might We question]
**Duration:** 30-45 minutes
**Participants:** [Names]
### Warm-Up (5 min)
[Quick creative exercise to loosen up]
### Silent Brainstorm (10 min)
- Write one idea per sticky note
- Work individually
- Aim for 10+ ideas each
### Share & Build (15 min)
- Share ideas one by one
- Build on others' ideas
- No criticism, only "Yes, and..."
### Cluster & Theme (10 min)
- Group similar ideas
- Name each cluster
- Identify promising directions
### Ideas Generated
| Cluster | Ideas | Count |
|---------|-------|-------|
| [Theme 1] | [List] | [N] |
| [Theme 2] | [List] | [N] |
### Top Ideas to Prototype
1. [Idea 1]
2. [Idea 2]
3. [Idea 3]
构思技巧
| 技巧 | 说明 | 适用时机 |
|---|---|---|
| 经典头脑风暴 | 自由联想 | 作为起点 |
| 脑写法 | 静默书写想法 | 安静的群体/远程群体 |
| SCAMPER | 替代、组合、调整、修改、另作他用、消除、反转 | 改进现有方案 |
| 类比 | X 会如何解决这个问题? | 打破思维定式 |
| 最糟糕的想法 | 故意提出糟糕的想法 | 陷入瓶颈时 |
| 混搭 | 组合无关的概念 | 激进创新 |
阶段 4:原型
快速、低成本地制作实体呈现,以便学习。
原型理念
“如果一张图片胜过千言万语,那么一个原型就胜过千场会议。” — IDEO
原型类型
| 类型 | 保真度 | 时间 | 适用场景 |
|---|---|---|---|
| 纸上草图 | 很低 | 几分钟 | 最初的探索 |
| 故事板 | 低 | 30 分钟 | 用户旅程、场景 |
| 纸上原型 | 低 | 1-2 小时 | 屏幕流程、UI |
| 角色扮演 | 低 | 30 分钟 | 服务体验 |
| 绿野仙踪原型 | 中 | 数小时 | 复杂交互 |
| 可点击模型 | 中 | 数天 | 数字产品 |
| 实体模型 | 不定 | 不定 | 实体产品 |
原型规划模板
## Prototype Plan
**Concept:** [What we're prototyping]
**Goal:** [What we want to learn]
**Audience:** [Who will test it]
### What to Prototype
- **Include:** [Essential elements to test]
- **Exclude:** [What we won't build yet]
### Prototype Type
**Type:** [Paper/Digital/Physical/Role-play]
**Fidelity:** [Low/Medium/High]
**Time to Build:** [Duration]
### Materials Needed
- [Material 1]
- [Material 2]
### Key Questions to Answer
1. [Question 1]
2. [Question 2]
3. [Question 3]
### Success Criteria
- [How we'll know it worked]
故事板模板
## Storyboard: [Concept Name]
### Scene 1: [Setup]
[Sketch/Description]
**What's happening:** [Action]
**User says/thinks:** "[Quote]"
### Scene 2: [Trigger]
[Sketch/Description]
**What's happening:** [Action]
**User says/thinks:** "[Quote]"
### Scene 3: [Interaction]
[Sketch/Description]
**What's happening:** [Action]
**User says/thinks:** "[Quote]"
### Scene 4: [Resolution]
[Sketch/Description]
**What's happening:** [Action]
**User says/thinks:** "[Quote]"
阶段 5:测试
了解哪些方法有效、哪些无效,并不断迭代。
测试原则
| 原则 | 描述 |
|---|---|
| 展示,而非讲述 | 让原型自己说明 |
| 创造体验 | 让用户参与互动,而不只是观看 |
| 追问“为什么?” | 深入了解用户的反应 |
| 拥抱失败 | 每次测试都会带来启发 |
| 迭代 | 构建-测试-学习循环 |
测试会议模板
## Test Session
**Prototype:** [Name/Version]
**Participant:** [Code or name]
**Date:** [ISO date]
### Introduction
"We're testing a concept, not you. There are no wrong answers.
Please think out loud as you interact with this."
### Scenario
[Context to set up the test]
### Observations
| Moment | Observation | Quote | Insight |
|--------|-------------|-------|---------|
| [When] | [What happened] | "[Said]" | [Meaning] |
### Key Learnings
1. [Learning 1]
2. [Learning 2]
3. [Learning 3]
### What to Keep
- [Element that worked]
### What to Change
- [Element to modify]
### Questions Raised
- [New question to explore]
迭代框架
## Iteration Review
**Prototype Version:** [N]
**Tests Conducted:** [Number]
### Synthesis
| Finding | Frequency | Severity | Action |
|---------|-----------|----------|--------|
| [Finding] | [X/N] | H/M/L | Keep/Change/Remove |
### Next Iteration
**Priority Changes:**
1. [Change 1]
2. [Change 2]
**Hypothesis to Test:**
If we [change], then [expected outcome] because [reason].
工作坊议程模板
半天工作坊(4 小时)
## Design Thinking Workshop
**Duration:** 4 hours
**Participants:** 6-12 people
### Agenda
**0:00 - 0:15** Welcome & Icebreaker
- Introductions
- Creative warm-up
**0:15 - 0:45** Empathy Share (30 min)
- Share research/interviews
- Empathy mapping exercise
**0:45 - 1:15** Define (30 min)
- Synthesize insights
- Create POV statements
- Generate HMW questions
**1:15 - 1:30** Break (15 min)
**1:30 - 2:15** Ideate (45 min)
- Brainstorming
- Clustering
- Voting
**2:15 - 3:15** Prototype (60 min)
- Teams build low-fi prototypes
- Prepare to present
**3:15 - 3:45** Share & Feedback (30 min)
- Each team presents
- Group feedback
**3:45 - 4:00** Wrap-up (15 min)
- Key decisions
- Next steps
全天冲刺(8 小时)
## Design Sprint (1-Day)
**Duration:** 8 hours (condensed from 5-day sprint)
**Participants:** 5-8 people cross-functional
### Morning: Understand & Define
**9:00 - 9:30** Set the stage
- Sprint goal
- Challenge statement
**9:30 - 10:30** Expert interviews / Lightning talks
- Stakeholder perspectives
- User insights
**10:30 - 11:00** How Might We
- Generate HMW from insights
- Vote on priority
**11:00 - 12:00** Sketch solutions
- Individual crazy 8s
- Solution sketches
### Afternoon: Build & Test
**12:00 - 1:00** Lunch
**1:00 - 1:30** Decide
- Critique sketches
- Vote
- Decide what to prototype
**1:30 - 4:00** Prototype
- Build testable prototype
- Prepare test script
**4:00 - 5:00** Test
- 3-5 user tests
- Capture feedback
**5:00 - 5:30** Debrief
- What we learned
- Next steps
与其他方法的集成
上游
- 用户研究 - 为共情阶段提供输入
- 利益相关方分析 - 确定访谈对象
- 战略分析 - 为创新提供业务背景
下游
- 精益创业 - 构建-衡量-学习循环
- 敏捷开发 - 迭代式实现
- 商业模式画布 - 对解决方案进行建模
.NET/C# 上下文
将设计思维应用于软件产品时:
// Example: Tracking Design Thinking sessions
public class DesignThinkingSession
{
public Guid Id { get; init; }
public required string ChallengeName { get; init; }
public required DesignPhase CurrentPhase { get; init; }
public required string HowMightWe { get; init; }
public DateTimeOffset Created { get; init; }
public List<EmpathyInsight> Insights { get; } = [];
public PointOfView? Pov { get; set; }
public List<Idea> Ideas { get; } = [];
public List<Prototype> Prototypes { get; } = [];
public List<TestResult> Tests { get; } = [];
}
public enum DesignPhase
{
Empathize,
Define,
Ideate,
Prototype,
Test
}
public record EmpathyInsight(
string Observation,
string UserQuote,
string Interpretation
);
public record PointOfView(
string User,
string Need,
string Insight
);
public record Idea(
string Title,
string Description,
int Votes,
string Cluster
);
相关技能
stakeholder-analysis- 确定访谈对象journey-mapping- 共情阶段可视化business-model-canvas- 对解决方案进行建模prioritization- 选择要制作原型的创意
版本历史
- v1.0.0(2025-12-26):首次发布
评论
支持 Markdown