design-thinking

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Design Thinking

Design Thinking(设计思维)

When to Use This Skill

何时使用该方法

Use this skill when:
  • Design Thinking tasks - Working on design thinking methodology for human-centered innovation. covers the 5-phase ideo/stanford d.school approach (empathize, define, ideate, prototype, test) with workshop facilitation and exercise templates
  • Planning or design - Need guidance on Design Thinking approaches
  • Best practices - Want to follow established patterns and standards
在以下场景使用本方法:
  • Design Thinking任务 - 开展以人为中心的创新设计思维方法论工作,涵盖IDEO/斯坦福d.school的五阶段方法(共情、定义、构思、原型、测试),包含工作坊引导与练习模板
  • 规划或设计 - 需要Design Thinking方法的指导
  • 最佳实践 - 希望遵循既定模式与标准

Overview

概述

A human-centered approach to innovation that integrates the needs of people, the possibilities of technology, and the requirements for business success.
一种整合用户需求、技术可能性与商业成功要求的以人为中心的创新方法。

What is Design Thinking?

什么是Design Thinking?

Design Thinking is a problem-solving methodology developed by IDEO and taught at Stanford d.school. It emphasizes understanding users, challenging assumptions, redefining problems, and creating innovative solutions through iterative prototyping and testing.
Design Thinking是由IDEO开发、斯坦福d.school教授的问题解决方法论。它强调理解用户、挑战假设、重新定义问题,并通过迭代式原型制作与测试创造创新解决方案。

Core Principles

核心原则

PrincipleDescription
Human-CenteredStart with people, not technology or process
Embrace AmbiguityComfortable with uncertainty early on
Bias to ActionLearn by doing, not just thinking
Radical CollaborationCross-functional, diverse perspectives
Iterate RapidlyFail fast, learn fast, improve fast
原则描述
以人为中心(Human-Centered)从用户出发,而非技术或流程
接纳模糊性(Embrace Ambiguity)早期阶段适应不确定性
行动导向(Bias to Action)在实践中学习,而非仅停留在思考
深度协作(Radical Collaboration)跨职能、多元视角
快速迭代(Iterate Rapidly)快速试错、快速学习、快速改进

The 5 Phases

五阶段

text
┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐
│         │  │         │  │         │  │         │  │         │
│EMPATHIZE│→│ DEFINE  │→│ IDEATE  │→│PROTOTYPE│→│  TEST   │
│         │  │         │  │         │  │         │  │         │
│Understand│  │Frame the│  │Generate │  │Build to │  │Learn &  │
│the user │  │problem  │  │ideas    │  │learn    │  │refine   │
└─────────┘  └─────────┘  └─────────┘  └─────────┘  └─────────┘
     ▲                                                    │
     └────────────────── Iterate ─────────────────────────┘
text
┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐
│         │  │         │  │         │  │         │  │         │
│EMPATHIZE│→│ DEFINE  │→│ IDEATE  │→│PROTOTYPE│→│  TEST   │
│         │  │         │  │         │  │         │  │         │
│Understand│  │Frame the│  │Generate │  │Build to │  │Learn &  │
│the user │  │problem  │  │ideas    │  │learn    │  │refine   │
└─────────┘  └─────────┘  └─────────┘  └─────────┘  └─────────┘
     ▲                                                    │
     └────────────────── Iterate ─────────────────────────┘

Phase Characteristics

各阶段特征

PhaseModeKey QuestionOutput
EmpathizeDivergeWhat is the user experiencing?Insights, observations
DefineConvergeWhat is the core problem?POV statement
IdeateDivergeWhat are possible solutions?Ideas, concepts
PrototypeConvergeHow can we make it tangible?Prototypes
TestLearnWhat works and what doesn't?Validated learning
阶段模式核心问题产出
共情(Empathize)发散用户正在经历什么?洞察、观察结果
定义(Define)收敛核心问题是什么?POV陈述
构思(Ideate)发散有哪些可行的解决方案?创意、概念
原型(Prototype)收敛如何将方案具象化?原型
测试(Test)学习哪些有效,哪些无效?经过验证的学习成果

Phase 1: Empathize

第一阶段:共情

Build deep understanding of users and their experiences.
建立对用户及其体验的深度理解。

Empathy Methods

共情方法

MethodDurationParticipantsBest For
User Interviews30-60 min1:1Deep individual insight
ObservationHours-daysField workNatural behavior
Empathy Mapping15-30 minWorkshopSynthesizing research
Journey Mapping1-2 hoursWorkshopExperience visualization
ShadowingHalf-dayField workWorkflow understanding
方法时长参与者适用场景
用户访谈30-60分钟一对一获取深度个体洞察
观察法数小时至数天实地工作了解自然行为
共情地图15-30分钟工作坊整合调研结果
旅程地图1-2小时工作坊可视化用户体验
跟岗学习半天实地工作理解工作流程

Empathy Map Template

共情地图模板

markdown
undefined
markdown
undefined

Empathy Map: [User/Persona Name]

共情地图:[用户/角色名称]

Says

所言

[Direct quotes from interviews/observation]
  • "[Quote 1]"
  • "[Quote 2]"
[访谈/观察中的直接引用]
  • "[引用1]"
  • "[引用2]"

Thinks

所思

[What might they be thinking? Hopes/fears?]
  • [Thought 1]
  • [Thought 2]
[他们可能在想什么?期望/担忧?]
  • [想法1]
  • [想法2]

Does

所为

[Actions and behaviors observed]
  • [Behavior 1]
  • [Behavior 2]
[观察到的行动与行为]
  • [行为1]
  • [行为2]

Feels

所感

[Emotional state, what worries/excites them]
  • [Emotion 1]
  • [Emotion 2]
[情绪状态,担忧/兴奋的点]
  • [情绪1]
  • [情绪2]

Pains

痛点

[Frustrations, obstacles, risks]
  • [Pain 1]
  • [Pain 2]
[挫败感、障碍、风险]
  • [痛点1]
  • [痛点2]

Gains

增益

[Wants, needs, measures of success]
  • [Gain 1]
  • [Gain 2]
undefined
[需求、期望、成功衡量标准]
  • [增益1]
  • [增益2]
undefined

Interview Guide Structure

访谈指南结构

markdown
undefined
markdown
undefined

User Interview Guide

用户访谈指南

Duration: 45-60 minutes Objective: [What we want to learn]
时长: 45-60分钟 目标: [我们想要了解的内容]

Opening (5 min)

开场(5分钟)

  • Introduce yourself and purpose
  • Explain confidentiality, recording consent
  • "There are no right or wrong answers"
  • 自我介绍与说明访谈目的
  • 解释保密原则与录音许可
  • "没有正确或错误的答案"

Context (10 min)

背景(10分钟)

  • Tell me about your role/day-to-day
  • How long have you been doing [X]?
  • Walk me through a typical [scenario]
  • 请介绍你的角色/日常工作
  • 你从事[X]工作多久了?
  • 请描述一个典型的[场景]

Deep Dive (25 min)

深入探讨(25分钟)

  • 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)

需求与期望(10分钟)

  • 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)

收尾(5分钟)

  • Is there anything else you'd like to share?
  • Can we follow up if we have questions?
undefined
  • 你还有其他想分享的内容吗?
  • 如果我们有后续问题,可以联系你吗?
undefined

Phase 2: Define

第二阶段:定义

Synthesize observations and frame the right problem.
整合观察结果,明确核心问题。

Point of View (POV) Statement

观点陈述(POV)

markdown
undefined
markdown
undefined

POV Statement

POV陈述

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.
undefined
用户: [特定用户类型/角色]
需求: [动词 - 他们需要完成的事]
洞察: [原因 - 关于背后动机的意外发现]

完整陈述: [用户]需要[需求],因为[洞察]。
示例: 忙碌的职场父母需要快速准备健康餐食, 因为他们想为孩子树立良好的饮食习惯, 但又因时间与成本的权衡而感到愧疚。
undefined

How Might We (HMW) Questions

我们如何(HMW)问题

Transform POV into actionable opportunity statements:
markdown
undefined
将POV转化为可落地的机会陈述:
markdown
undefined

How Might We Questions

我们如何(HMW)问题

POV: [Your POV statement]
POV: [你的POV陈述]

HMW Brainstorm

HMW头脑风暴

Generate HMW questions by asking:
LensQuestionHMW
Amplify the goodWhat's working?HMW do more of [good thing]?
Remove the badWhat's painful?HMW eliminate [pain point]?
Explore the oppositeWhat if we flipped it?HMW [opposite approach]?
Question assumptionsWhat's assumed?HMW if [assumption] wasn't true?
Change status quoWhat's expected?HMW change when/where/who?
Break it into partsWhat are components?HMW address just [component]?
通过以下角度生成HMW问题:
视角问题HMW
放大优势哪些方面有效?我们如何强化[优势点]?
消除痛点哪些方面存在困扰?我们如何消除[痛点]?
反向思考如果反过来会怎样?我们如何采用[反向方法]?
挑战假设存在哪些假设?如果[假设]不成立,我们该如何做?
改变现状普遍预期是什么?我们如何改变时间/地点/参与人员?
拆分问题问题包含哪些组成部分?我们如何仅解决[某一组成部分]?

Selected HMW Questions

选定的HMW问题

  1. HMW [question 1]?
  2. HMW [question 2]?
  3. HMW [question 3]?
Priority HMW: [The one to ideate on]
undefined
  1. 我们如何[问题1]?
  2. 我们如何[问题2]?
  3. 我们如何[问题3]?
优先级HMW: [用于构思的核心问题]
undefined

Phase 3: Ideate

第三阶段:构思

Generate a wide range of creative solutions.
生成大量创意解决方案。

Ideation Rules

构思规则

RuleDescription
Defer judgmentNo criticism during brainstorming
Go for quantityMore ideas = better ideas
Build on others' ideas"Yes, and..."
Encourage wild ideasThink big, no constraints
Be visualSketch, don't just talk
One conversationListen, build, riff
Stay focusedKeep the HMW visible
规则描述
延迟评判头脑风暴期间不做批评
追求数量想法越多,优质方案出现的概率越高
基于他人想法延伸采用“是的,而且……”的思路
鼓励疯狂想法大胆思考,不受限制
可视化表达用草图呈现,而非仅口头描述
有序讨论倾听、延伸、互动
聚焦主题始终围绕HMW问题

Brainstorming Session Template

头脑风暴会议模板

markdown
undefined
markdown
undefined

Ideation Session

构思会议

HMW: [The How Might We question] Duration: 30-45 minutes Participants: [Names]
HMW: [我们如何解决的问题] 时长: 30-45分钟 参与者: [姓名]

Warm-Up (5 min)

热身环节(5分钟)

[Quick creative exercise to loosen up]
[快速创意练习,活跃思维]

Silent Brainstorm (10 min)

静默头脑风暴(10分钟)

  • Write one idea per sticky note
  • Work individually
  • Aim for 10+ ideas each
  • 每张便签写一个想法
  • 独立完成
  • 每人至少产出10个想法

Share & Build (15 min)

分享与延伸(15分钟)

  • Share ideas one by one
  • Build on others' ideas
  • No criticism, only "Yes, and..."
  • 逐一分享想法
  • 基于他人想法延伸
  • 不做批评,仅用“是的,而且……”

Cluster & Theme (10 min)

聚类与主题提炼(10分钟)

  • Group similar ideas
  • Name each cluster
  • Identify promising directions
  • 将相似想法分组
  • 为每组命名
  • 识别有潜力的方向

Ideas Generated

生成的想法

ClusterIdeasCount
[Theme 1][List][N]
[Theme 2][List][N]
主题想法数量
[主题1][列表][N]
[主题2][列表][N]

Top Ideas to Prototype

优先原型的想法

  1. [Idea 1]
  2. [Idea 2]
  3. [Idea 3]
undefined
  1. [想法1]
  2. [想法2]
  3. [想法3]
undefined

Ideation Techniques

构思技巧

TechniqueDescriptionWhen to Use
Classic BrainstormFree associationStarting point
BrainwritingSilent written ideasQuiet/remote groups
SCAMPERSubstitute, Combine, Adapt, Modify, Put to other use, Eliminate, ReverseImproving existing
AnalogiesHow would X solve this?Breaking mental models
Worst IdeaIntentionally bad ideasWhen stuck
Mash-upCombine unrelated conceptsRadical innovation
技巧描述适用场景
经典头脑风暴自由联想初始构思阶段
书面头脑风暴静默书写想法安静/远程团队
SCAMPER法替代、组合、适配、修改、复用、消除、反转优化现有方案
类比法如果是X会如何解决这个问题?打破思维定式
最差想法法故意提出糟糕的想法陷入思维瓶颈时
混搭法结合不相关概念激进创新

Phase 4: Prototype

第四阶段:原型

Build quick, cheap representations to learn.
快速制作低成本的方案原型以学习验证。

Prototype Philosophy

原型设计理念

"If a picture is worth 1,000 words, a prototype is worth 1,000 meetings." — IDEO
"如果一张图片胜过千言万语,那么一个原型胜过千次会议。" — IDEO

Prototype Types

原型类型

TypeFidelityTimeBest For
Paper SketchVery LowMinutesEarliest exploration
StoryboardLow30 minUser journey, scenarios
Paper PrototypeLow1-2 hoursScreen flows, UI
Role PlayLow30 minService experiences
Wizard of OzMediumHoursComplex interactions
Clickable MockupMediumDaysDigital products
Physical ModelVariesVariesTangible products
类型保真度耗时适用场景
纸面草图极低数分钟早期探索阶段
故事板30分钟用户旅程、场景模拟
纸面原型1-2小时界面流程、UI设计
角色扮演30分钟服务体验模拟
奥兹巫师法数小时复杂交互模拟
可点击原型数天数字产品
实体模型可变可变有形产品

Prototype Planning Template

原型规划模板

markdown
undefined
markdown
undefined

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]
  • [材料1]
  • [材料2]

Key Questions to Answer

核心待解答问题

  1. [Question 1]
  2. [Question 2]
  3. [Question 3]
  1. [问题1]
  2. [问题2]
  3. [问题3]

Success Criteria

成功标准

  • [How we'll know it worked]
undefined
  • [我们如何判断原型有效]
undefined

Storyboard Template

故事板模板

markdown
undefined
markdown
undefined

Storyboard: [Concept Name]

故事板:[概念名称]

Scene 1: [Setup]

场景1:[背景设定]

[Sketch/Description] What's happening: [Action] User says/thinks: "[Quote]"
[草图/描述] 发生的事: [动作] 用户所说/所想: "[引用]"

Scene 2: [Trigger]

场景2:[触发点]

[Sketch/Description] What's happening: [Action] User says/thinks: "[Quote]"
[草图/描述] 发生的事: [动作] 用户所说/所想: "[引用]"

Scene 3: [Interaction]

场景3:[互动环节]

[Sketch/Description] What's happening: [Action] User says/thinks: "[Quote]"
[草图/描述] 发生的事: [动作] 用户所说/所想: "[引用]"

Scene 4: [Resolution]

场景4:[解决结果]

[Sketch/Description] What's happening: [Action] User says/thinks: "[Quote]"
undefined
[草图/描述] 发生的事: [动作] 用户所说/所想: "[引用]"
undefined

Phase 5: Test

第五阶段:测试

Learn what works, what doesn't, and iterate.
了解方案的优劣,进行迭代优化。

Testing Principles

测试原则

PrincipleDescription
Show, don't tellLet the prototype speak
Create experiencesHave users interact, not just look
Ask "why?"Dig into reactions
Embrace failureEvery test teaches something
IterateBuild-test-learn cycles
原则描述
展示而非讲述让原型自己“说话”
创造体验让用户互动,而非仅观看
追问“为什么”深入挖掘用户反应背后的原因
拥抱失败每一次测试都能带来收获
持续迭代遵循制作-测试-学习的循环

Test Session Template

测试会议模板

markdown
undefined
markdown
undefined

Test Session

测试会议

Prototype: [Name/Version] Participant: [Code or name] Date: [ISO date]
原型: [名称/版本] 参与者: [代号或姓名] 日期: [ISO格式日期]

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

观察记录

MomentObservationQuoteInsight
[When][What happened]"[Said]"[Meaning]
时刻观察内容用户引用洞察
[时间点][发生的事]"[引用]"[背后含义]

Key Learnings

核心收获

  1. [Learning 1]
  2. [Learning 2]
  3. [Learning 3]
  1. [收获1]
  2. [收获2]
  3. [收获3]

What to Keep

保留的元素

  • [Element that worked]
  • [有效的元素]

What to Change

需要修改的元素

  • [Element to modify]
  • [需要调整的元素]

Questions Raised

待探索的新问题

  • [New question to explore]
undefined
  • [需要进一步研究的问题]
undefined

Iteration Framework

迭代框架

markdown
undefined
markdown
undefined

Iteration Review

迭代回顾

Prototype Version: [N] Tests Conducted: [Number]
原型版本: [N] 测试次数: [数量]

Synthesis

结果整合

FindingFrequencySeverityAction
[Finding][X/N]H/M/LKeep/Change/Remove
发现出现频率严重程度行动
[发现][X/N]高/中/低保留/修改/移除

Next Iteration

下一版本迭代

Priority Changes:
  1. [Change 1]
  2. [Change 2]
Hypothesis to Test: If we [change], then [expected outcome] because [reason].
undefined
优先级修改:
  1. [修改1]
  2. [修改2]
待验证假设: 如果我们做出[修改],那么[预期结果],因为[原因]。
undefined

Workshop Agenda Templates

工作坊议程模板

Half-Day Workshop (4 hours)

半天工作坊(4小时)

markdown
undefined
markdown
undefined

Design Thinking Workshop

Design Thinking工作坊

Duration: 4 hours Participants: 6-12 people
时长: 4小时 参与者: 6-12人

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
undefined
0:00 - 0:15 欢迎与破冰
  • 自我介绍
  • 创意热身练习
0:15 - 0:45 共情分享(30分钟)
  • 分享调研/访谈结果
  • 共情地图练习
0:45 - 1:15 定义阶段(30分钟)
  • 整合洞察
  • 制作POV陈述
  • 生成HMW问题
1:15 - 1:30 休息(15分钟)
1:30 - 2:15 构思阶段(45分钟)
  • 头脑风暴
  • 聚类分组
  • 投票筛选
2:15 - 3:15 原型制作(60分钟)
  • 团队制作低保真原型
  • 准备展示
3:15 - 3:45 分享与反馈(30分钟)
  • 各团队展示
  • 集体反馈
3:45 - 4:00 总结(15分钟)
  • 关键决策
  • 后续步骤
undefined

Full-Day Sprint (8 hours)

全天设计冲刺(8小时)

markdown
undefined
markdown
undefined

Design Sprint (1-Day)

设计冲刺(1天版)

Duration: 8 hours (condensed from 5-day sprint) Participants: 5-8 people cross-functional
时长: 8小时(从5天版浓缩而来) 参与者: 5-8人跨职能团队

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
9:00 - 9:30 设定目标
  • 冲刺目标
  • 挑战陈述
9:30 - 10:30 专家访谈/闪电演讲
  • 利益相关者视角
  • 用户洞察
10:30 - 11:00 HMW问题生成
  • 从洞察中生成HMW问题
  • 投票选出优先级问题
11:00 - 12:00 方案草图
  • 个人“疯狂8”练习
  • 方案草图

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
undefined
12:00 - 1:00 午餐
1:00 - 1:30 决策环节
  • 评审草图
  • 投票
  • 确定原型制作方向
1:30 - 4:00 原型制作
  • 制作可测试原型
  • 准备测试脚本
4:00 - 5:00 用户测试
  • 3-5次用户测试
  • 收集反馈
5:00 - 5:30 复盘
  • 学习收获
  • 后续步骤
undefined

Integration with Other Methods

与其他方法的整合

Upstream

上游环节

  • User Research - Feeds into Empathize phase
  • Stakeholder Analysis - Identifies who to interview
  • Strategic Analysis - Business context for innovation
  • 用户调研 - 为共情阶段提供输入
  • 利益相关者分析 - 确定访谈对象
  • 战略分析 - 提供创新的商业背景

Downstream

下游环节

  • Lean Startup - Build-Measure-Learn loops
  • Agile Development - Iterative implementation
  • Business Model Canvas - Modeling the solution
  • 精益创业 - 制作-衡量-学习循环
  • 敏捷开发 - 迭代式实施
  • 商业模式画布 - 方案建模

.NET/C# Context

.NET/C#场景应用

When applying Design Thinking to software products:
csharp
// 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
);
将Design Thinking应用于软件产品时:
csharp
// 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
);

Related Skills

相关方法

  • stakeholder-analysis
    - Identifying interview subjects
  • journey-mapping
    - Empathize phase visualization
  • business-model-canvas
    - Modeling solutions
  • prioritization
    - Selecting which ideas to prototype
  • stakeholder-analysis
    - 确定访谈对象
  • journey-mapping
    - 共情阶段可视化工具
  • business-model-canvas
    - 方案建模
  • prioritization
    - 筛选原型想法

Version History

版本历史

  • v1.0.0 (2025-12-26): Initial release
  • v1.0.0 (2025-12-26): 初始版本