jobs-to-be-done
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseJobs to Be Done - Customer Motivation Framework
Jobs to Be Done - 客户动机框架
Understand why customers really buy by uncovering the "job" they're hiring your product to do
通过挖掘客户雇佣你的产品来完成的“任务”,理解客户真正的购买原因
When to Use This Skill
何时使用该方法
- Understanding customer motivation beyond demographics and feature requests
- Finding product-market fit by identifying the real progress customers seek
- Discovering why customers switch (or don't) between solutions
- Identifying true competition that isn't obvious from industry categories
- Creating marketing messages that resonate with real customer struggles
- Prioritizing features based on unmet customer needs
- Conducting customer research that reveals actionable insights
- 理解客户动机(超越人口统计特征和功能需求)
- 寻找产品市场契合点(识别客户追求的真实进展)
- 探究客户转换(或不转换)解决方案的原因
- 识别行业类别中不明显的真正竞争对手
- 打造能引起客户真实痛点共鸣的营销信息
- 基于客户未被满足的需求确定功能优先级
- 开展能产出可落地洞见的客户调研
Methodology Foundation
方法论基础
| Aspect | Details |
|---|---|
| Source | Competing Against Luck (2016), The Innovator's Solution (2003) |
| Expert | Clayton Christensen (Harvard Business School), Tony Ulwick (Strategyn) |
| Core Principle | "People don't buy products; they hire them to get jobs done. Understanding the job—not the customer or the product—is the key to predictable innovation." |
| 方面 | 详情 |
|---|---|
| 来源 | 《与运气竞争》(2016)、《创新者的解答》(2003) |
| 专家 | Clayton Christensen(哈佛商学院)、Tony Ulwick(Strategyn) |
| 核心原则 | "人们购买的不是产品,而是雇佣产品来完成某项任务。理解任务——而非客户或产品——是实现可预测创新的关键。" |
What Claude Does vs What You Decide
Claude 能做什么 vs 你需要决定什么
| Claude Does | You Decide |
|---|---|
| Structures production workflow | Final creative direction |
| Suggests technical approaches | Equipment and tool choices |
| Creates templates and checklists | Quality standards |
| Identifies best practices | Brand/voice decisions |
| Generates script outlines | Final script approval |
| Claude 能做的事 | 你需要决定的事 |
|---|---|
| 构建产出工作流 | 最终创意方向 |
| 提供技术方法建议 | 设备与工具选择 |
| 创建模板和检查清单 | 质量标准 |
| 识别最佳实践 | 品牌/风格决策 |
| 生成脚本大纲 | 最终脚本审批 |
What This Skill Does
该方法的作用
This skill helps you shift from asking "Who is my customer?" to asking "What job is my customer trying to get done?"
The result is a fundamentally different understanding of why people buy:
- Uncover the real job - The progress customers are trying to make in their lives
- See all three dimensions - Functional, emotional, and social needs
- Understand the forces - What pushes people to change and what holds them back
- Map the job - Break it down into steps where you can add value
- Identify true competition - Everyone solving the same job, regardless of category
This transforms feature-driven product development into progress-driven innovation.
这个方法能帮你从“我的客户是谁?”转变为“我的客户想要完成什么任务?”
最终你会对人们的购买原因产生完全不同的理解:
- 挖掘真实任务 - 客户在生活中想要取得的进展
- 覆盖三个维度 - 功能性、情感性和社会性需求
- 理解驱动力量 - 推动人们改变的因素和阻碍他们的因素
- 绘制任务地图 - 将任务拆解为你可以创造价值的步骤
- 识别真正的竞争对手 - 所有解决同一任务的主体,无论所属类别
这将把以功能为导向的产品开发转变为以进展为导向的创新。
How to Use
使用方法
Prompt Examples
提示词示例
Help me identify the Job to Be Done for customers who buy [product/service].
Use the Christensen JTBD framework. Consider functional, emotional, and social dimensions.I'm seeing customers use my product for [unexpected purpose]. Help me understand
what job they might be hiring it for using JTBD analysis.Create a Job Map for [specific customer goal]. Break it into the 8 universal steps
and identify where customers might struggle most.Analyze the forces of progress for someone switching from [current solution] to [my product].
What's pushing them, pulling them, causing anxiety, and creating habit inertia?Write Job Stories (not user stories) for my [product]. Focus on situation,
motivation, and expected outcome rather than user type and action.帮我识别购买[产品/服务]的客户的Jobs to Be Done。
使用Christensen的JTBD框架,考虑功能、情感和社会维度。我发现客户将我的产品用于[意外用途]。请用JTBD分析帮我理解他们可能在雇佣产品完成什么任务。为[特定客户目标]创建任务地图。将其拆解为8个通用步骤,并找出客户最可能遇到困难的环节。分析用户从[当前解决方案]转换到[我的产品]的进展驱动力。
推动他们的因素是什么?吸引他们的因素是什么?引发焦虑的因素是什么?造成习惯惯性的因素是什么?为我的[产品]撰写任务故事(而非用户故事)。聚焦场景、动机和预期结果,而非用户类型和动作。Instructions
操作指南
The Core Framework
核心框架
┌─────────────────────────────────────────────────────────────┐
│ JOBS TO BE DONE │
├─────────────────────────────────────────────────────────────┤
│ │
│ "When [CIRCUMSTANCE], I want to [JOB], so I can [OUTCOME]" │
│ │
│ ┌───────────┐ ┌───────────┐ ┌───────────┐ │
│ │FUNCTIONAL │ + │ EMOTIONAL │ + │ SOCIAL │ │
│ │ JOB │ │ JOB │ │ JOB │ │
│ └───────────┘ └───────────┘ └───────────┘ │
│ │
│ What they're How they want How they want │
│ trying to DO to FEEL to be SEEN │
│ │
└─────────────────────────────────────────────────────────────┘┌─────────────────────────────────────────────────────────────┐
│ JOBS TO BE DONE │
├─────────────────────────────────────────────────────────────┤
│ │
│ "当[场景]时,我想要[完成任务],这样我就能[达成结果]" │
│ │
│ ┌───────────┐ ┌───────────┐ ┌───────────┐ │
│ │功能性任务│ + │情感性任务│ + │社会性任务│ │
│ └───────────┘ └───────────┘ └───────────┘ │
│ │
│ 他们想要完成的事 他们想要的感受 他们希望被如何看待 │
│ │
└─────────────────────────────────────────────────────────────┘Step 1: Understand the Three Dimensions
步骤1:理解三个维度
Every job has three dimensions. Products that address all three are far more likely to be "hired."
| Dimension | Question | Example (Fitness App) |
|---|---|---|
| Functional | What are they trying to accomplish? | Get exercise guidance and track workouts |
| Emotional | How do they want to feel? | Feel confident, accomplished, in control of health |
| Social | How do they want to be perceived? | Be seen as fit, disciplined, health-conscious |
Key Insight: Many products fail because they nail the functional job but ignore the emotional and social dimensions.
Exercise: For your product, fill in:
- "Customers hire us to DO _______________"
- "Customers hire us to FEEL _______________"
- "Customers hire us to BE SEEN AS _______________"
每个任务都包含三个维度。能同时满足这三个维度的产品更有可能被客户“雇佣”。
| 维度 | 问题 | 示例(健身应用) |
|---|---|---|
| 功能性 | 他们想要完成什么? | 获取锻炼指导并追踪训练情况 |
| 情感性 | 他们想要有什么感受? | 感到自信、有成就感、能掌控健康 |
| 社会性 | 他们希望被如何看待? | 被视为健康、自律、注重养生的人 |
关键洞见:许多产品失败是因为它们只做好了功能性任务,却忽略了情感和社会维度。
练习:针对你的产品,填写以下内容:
- "客户雇佣我们来完成 _______________"
- "客户雇佣我们来获得 _______________感受"
- "客户雇佣我们来被视为 _______________"
Step 2: Identify the Forces of Progress
步骤2:识别进展驱动力
Four forces determine whether a customer will "switch" to your solution:
┌─────────────┐
│ PUSH │
│ Problems │
│ with status │
│ quo │
└──────┬──────┘
↓
┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ HABIT │←────│ CUSTOMER │────→│ PULL │
│ Comfort │ │ DECISION │ │ Attraction │
│ with old │ └──────────────┘ │ of new │
│ way │ │ solution │
└─────────────┘ ↑ └─────────────┘
┌──────┴──────┐
│ ANXIETY │
│ Fear of │
│ change │
└─────────────┘Switch happens when: Push + Pull > Habit + Anxiety
| Force | What to Ask | Example |
|---|---|---|
| Push | What's frustrating about their current situation? | "I keep losing track of my workouts in notebooks" |
| Pull | What's appealing about the new solution? | "The app shows my progress visually" |
| Anxiety | What fears do they have about changing? | "What if I can't figure out how to use it?" |
| Habit | What's comfortable about the status quo? | "I've always used notebooks, it's familiar" |
Tactical Application:
- Increase Push: Help customers see the true cost of their current solution
- Increase Pull: Demonstrate the progress they can make
- Reduce Anxiety: Provide guarantees, trials, social proof
- Reduce Habit: Make switching easy, offer migration tools
四个因素决定客户是否会“转换”到你的解决方案:
┌─────────────┐
│ 推力 │
│ 当前状态的问题 │
└──────┬──────┘
↓
┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ 习惯惯性 │←────│ 客户决策 │────→│ 拉力 │
│ 对旧方式的舒适感 │ └──────────────┘ │ 新解决方案的吸引力 │
└─────────────┘ ↑ └─────────────┘
┌──────┴──────┐
│ 焦虑感 │
│ 对改变的恐惧 │
└─────────────┘转换发生的条件:推力 + 拉力 > 习惯惯性 + 焦虑感
| 力量 | 要问的问题 | 示例 |
|---|---|---|
| 推力 | 他们当前的处境有什么令人沮丧的地方? | "我总是在笔记本上丢失训练记录" |
| 拉力 | 新解决方案有什么吸引人的地方? | "这个应用能可视化展示我的进展" |
| 焦虑感 | 他们对改变有什么恐惧? | "如果我不会用怎么办?" |
| 习惯惯性 | 当前状态有什么舒适之处? | "我一直用笔记本,已经习惯了" |
实际应用:
- 增强推力:帮助客户看到当前解决方案的真实成本
- 增强拉力:展示他们能取得的进展
- 减少焦虑感:提供保证、试用、社交证明
- 减少习惯惯性:让转换变得容易,提供迁移工具
Step 3: Map the Job
步骤3:绘制任务地图
Break down any job into the universal 8-step Job Map:
| Step | Description | Questions to Ask |
|---|---|---|
| 1. Define | Determine goals and plan | "What are you trying to accomplish?" |
| 2. Locate | Gather inputs needed | "What do you need to get started?" |
| 3. Prepare | Set up and organize | "How do you get ready?" |
| 4. Confirm | Verify readiness | "How do you know you're ready?" |
| 5. Execute | Perform the core job | "What are the key steps?" |
| 6. Monitor | Check progress | "How do you know it's working?" |
| 7. Modify | Make adjustments | "What do you change if needed?" |
| 8. Conclude | Wrap up and clean up | "How do you finish up?" |
Example: Job = "Prepare a nutritious dinner on a busy weeknight"
| Step | Activity | Struggle Points |
|---|---|---|
| Define | Decide what to make | Too many options, dietary restrictions |
| Locate | Get ingredients | Missing items, trip to store |
| Prepare | Prep ingredients | Takes too long, messy |
| Confirm | Check recipe | Confusing instructions |
| Execute | Cook the meal | Timing multiple dishes |
| Monitor | Watch for doneness | Burning, undercooking |
| Modify | Adjust seasoning | Unsure how to fix mistakes |
| Conclude | Serve and clean | Pile of dishes |
Innovation Opportunity: Each struggle point is an opportunity to create value.
将任何任务拆解为通用的8步任务地图:
| 步骤 | 描述 | 要问的问题 |
|---|---|---|
| 1. 定义 | 确定目标并制定计划 | "你想要完成什么?" |
| 2. 筹备 | 收集所需输入 | "开始前你需要什么?" |
| 3. 准备 | 搭建和整理 | "你如何做好准备?" |
| 4. 确认 | 验证准备就绪情况 | "你怎么知道自己准备好了?" |
| 5. 执行 | 完成核心任务 | "关键步骤是什么?" |
| 6. 监控 | 检查进展 | "你怎么知道它在正常运行?" |
| 7. 调整 | 做出修改 | "需要时你会做什么调整?" |
| 8. 收尾 | 完成并清理 | "你如何结束任务?" |
示例:任务 = "在忙碌的工作日晚上准备一顿营养晚餐"
| 步骤 | 活动 | 痛点 |
|---|---|---|
| 定义 | 决定做什么 | 选择太多,有饮食限制 |
| 筹备 | 获取食材 | 缺少食材,需要去商店 |
| 准备 | 预处理食材 | 耗时太长,很麻烦 |
| 确认 | 查看食谱 | 说明混乱 |
| 执行 | 烹饪食物 | 多个菜品的时间协调 |
| 监控 | 观察熟度 | 烧焦、未煮熟 |
| 调整 | 调味调整 | 不知道如何补救错误 |
| 收尾 | 上菜和清理 | 一堆餐具 |
创新机会:每个痛点都是创造价值的机会。
Step 4: Discover Desired Outcomes
步骤4:发现期望结果
For each job step, identify what customers use to measure success:
Format: [Direction] + [Metric] + [Object]
Examples:
- "Minimize the time it takes to find ingredients"
- "Minimize the likelihood of burning the food"
- "Increase the confidence that family will enjoy it"
- "Minimize the effort required to clean up"
Quantify Importance & Satisfaction:
Survey customers on:
- How important is this outcome? (1-10)
- How satisfied are you with current solutions? (1-10)
Opportunity Score = Importance + (Importance - Satisfaction)
High opportunity = High importance, Low satisfaction
针对每个任务步骤,确定客户衡量成功的标准:
格式:[方向] + [指标] + [对象]
示例:
- "最小化 寻找食材所需的时间"
- "最小化 食物烧焦的可能性"
- "提升 家人会喜欢这顿饭的信心"
- "最小化 清理所需的精力"
量化重要性与满意度:
向客户调研:
- 这个结果有多重要?(1-10分)
- 你对当前解决方案的满意度如何?(1-10分)
机会得分 = 重要性 + (重要性 - 满意度)
高机会 = 高重要性,低满意度
Step 5: Redefine Your Competition
步骤5:重新定义竞争对手
JTBD reveals that competition extends far beyond your industry.
Traditional View: Same product category
JTBD View: All solutions hired for the same job
Example: Job = "Feel energized in the morning"
| Solution | Category | Same Job? |
|---|---|---|
| Coffee | Beverage | ✓ |
| Energy drink | Beverage | ✓ |
| Morning jog | Fitness | ✓ |
| Cold shower | Personal care | ✓ |
| Meditation app | Wellness | ✓ |
| Upbeat playlist | Entertainment | ✓ |
Strategic Implication: You're not competing with similar products. You're competing with every way customers currently get the job done.
JTBD揭示竞争对手远不止同行业的产品。
传统视角:同一产品类别
JTBD视角:所有被雇佣来完成同一任务的解决方案
示例:任务 = "早上感到精力充沛"
| 解决方案 | 类别 | 是否完成同一任务? |
|---|---|---|
| 咖啡 | 饮品 | ✓ |
| 能量饮料 | 饮品 | ✓ |
| 晨跑 | 健身 | ✓ |
| 冷水澡 | 个人护理 | ✓ |
| 冥想应用 | 健康养生 | ✓ |
| 欢快的播放列表 | 娱乐 | ✓ |
战略启示:你不是在和同类产品竞争,而是在和客户当前完成该任务的所有方式竞争。
Step 6: Write Job Stories
步骤6:撰写任务故事
Replace user stories with Job Stories for better product decisions.
User Story (Traditional):
"As a [user type], I want [action], so that [benefit]."
Job Story (JTBD):
"When [situation/context], I want to [motivation], so I can [expected outcome]."
Comparison:
| User Story | Job Story |
|---|---|
| "As a busy parent, I want a quick meal option" | "When I get home exhausted from work and the kids are hungry NOW, I want to put something nutritious on the table in under 20 minutes, so I can feed my family without guilt or stress" |
| "As a fitness enthusiast, I want to track workouts" | "When I finish a workout and want to see my progress, I want to quickly log what I did, so I can feel accomplished and know I'm improving" |
Job Stories capture:
- Circumstance (the trigger)
- Motivation (the real goal)
- Outcome (the definition of success)
用任务故事替代用户故事,做出更好的产品决策。
传统用户故事:
"作为[用户类型],我想要[动作],以便[获益]。"
JTBD任务故事:
"当[场景/情境]时,我想要[动机],以便[预期结果]。"
对比:
| 用户故事 | 任务故事 |
|---|---|
| "作为忙碌的家长,我想要快速的餐食选择" | "当我下班回家筋疲力尽,而孩子们现在就饿了,我想要在20分钟内把有营养的食物摆上桌,这样我就能毫无愧疚或压力地喂饱家人" |
| "作为健身爱好者,我想要追踪训练情况" | "当我完成训练后想要查看自己的进展时,我想要快速记录我的训练内容,这样我就能感到有成就感,并且知道自己在进步" |
任务故事捕捉:
- 场景(触发因素)
- 动机(真实目标)
- 结果(成功的定义)
Examples
示例
Example 1: The Milkshake Story (Classic)
示例1:奶昔故事(经典案例)
Situation: Fast-food chain wants to improve milkshake sales. Traditional research (focus groups, demographics) fails.
JTBD Analysis:
Morning Customers (Commuters):
- Job: Make the boring commute more interesting and stay full until lunch
- Functional: One-hand consumption, filling, lasts the whole drive
- Emotional: Feel satisfied, not bored
- Social: N/A (alone in car)
- Competition: Bananas, bagels, donuts
Afternoon Customers (Parents):
- Job: Be a good parent by treating the kids
- Functional: Quick, manageable for children
- Emotional: Feel like a caring parent
- Social: Be seen as fun/generous by the child
- Competition: Ice cream, candy, toys
Implications:
- Morning: Make it thicker (lasts longer), add texture (interest), self-serve kiosk (faster)
- Afternoon: Smaller size, quicker to consume, kid-friendly packaging
场景:快餐连锁店想要提升奶昔销量。传统调研(焦点小组、人口统计)失败。
JTBD分析:
晨间客户(通勤者):
- 任务:让无聊的通勤变得有趣,并且一直保持饱腹感直到午餐
- 功能性:可以单手食用,饱腹感强,能撑完全程通勤
- 情感性:感到满足,不无聊
- 社会性:无(独自在车内)
- 竞争对手:香蕉、百吉饼、甜甜圈
午后客户(家长):
- 任务:通过犒劳孩子来做个好家长
- 功能性:快速,适合孩子食用
- 情感性:感到自己是个贴心的家长
- 社会性:在孩子眼中被视为有趣/大方的人
- 竞争对手:冰淇淋、糖果、玩具
启示:
- 晨间:做的更浓稠(持续时间更长),增加口感(更有趣),自助 kiosk(更快)
- 午后:更小份,食用更快,儿童友好包装
Example 2: SaaS Product Discovery
示例2:SaaS产品发现
Situation: A project management tool sees unexpected adoption by freelancers.
JTBD Interview Findings:
The Job: "Appear professional and organized to clients"
Forces:
- Push: "I was embarrassed when I lost a client email and missed a deadline"
- Pull: "This makes me look like I have my act together"
- Anxiety: "What if it's overkill? What if I can't figure it out?"
- Habit: "I've always just used sticky notes and Gmail"
Three Dimensions:
- Functional: Keep track of tasks and deadlines
- Emotional: Feel in control, confident
- Social: Appear professional, reliable to clients
Job Stories:
-
"When a client sends multiple emails about different projects, I want to quickly organize everything by project, so I can respond promptly without missing anything."
-
"When I'm on a call with a client asking for a status update, I want to instantly see where everything stands, so I can sound professional and knowledgeable."
Product Decisions Based on This:
- Add "client view" so freelancers can share professional-looking status updates
- Create quick-capture feature for emails
- Build "instant status" dashboard for calls
场景:一款项目管理工具意外被自由职业者广泛采用。
JTBD访谈发现:
任务:"在客户面前显得专业且有条理"
驱动力量:
- 推力:"当我丢失客户邮件并错过截止日期时,我感到很尴尬"
- 拉力:"这让我看起来很靠谱"
- 焦虑感:"如果它功能过剩怎么办?如果我不会用怎么办?"
- 习惯惯性:"我一直只用便利贴和Gmail"
三个维度:
- 功能性:跟踪任务和截止日期
- 情感性:感到掌控一切、自信
- 社会性:在客户面前显得专业、可靠
任务故事:
-
"当客户发送多封关于不同项目的邮件时,我想要快速按项目整理所有内容,这样我就能及时回复,不会遗漏任何信息。"
-
"当我在和客户的通话中被要求提供状态更新时,我想要立即查看所有事项的进展,这样我就能听起来专业且了解情况。"
基于此的产品决策:
- 添加“客户视图”,让自由职业者可以分享专业的状态更新
- 创建邮件快速捕捉功能
- 为通话打造“即时状态”仪表板
Checklists & Templates
检查清单与模板
JTBD Discovery Interview Guide
JTBD发现访谈指南
markdown
undefinedmarkdown
undefinedJTBD Interview for: [Product/Service]
JTBD访谈对象:[产品/服务]
Opening
开场
"I'd like to understand the story of how you came to use [product].
Walk me through what was happening in your life when you first started looking."
"我想了解您使用[产品]的来龙去脉。
请您回顾一下,当您刚开始寻找这类产品时,生活中正在发生什么?"
Timeline Questions
时间线问题
- "When did you first realize you needed something like this?"
- "What was happening in your life at that moment?"
- "What did you try first? How did that work out?"
- "When did you first hear about [our product]?"
- "What almost stopped you from trying it?"
- "What was the moment you decided to actually use it?"
- "What did you have to give up or change?"
- "您第一次意识到需要这类产品是什么时候?"
- "那时您的生活中正在发生什么?"
- "您首先尝试了什么?效果如何?"
- "您第一次听说[我们的产品]是什么时候?"
- "什么差点阻止您尝试它?"
- "您决定真正使用它的那一刻发生了什么?"
- "您不得不放弃或改变了什么?"
Forces Questions
驱动力问题
Push: "What was frustrating about how you were doing it before?"
Pull: "What about [product] was appealing?"
Anxiety: "What were you worried about?"
Habit: "What was hard about changing?"
推力:"您之前的做法有什么令人沮丧的地方?"
拉力:"[产品]的什么地方吸引了您?"
焦虑感:"您当时有什么担忧?"
习惯惯性:"改变的困难之处是什么?"
Outcome Questions
结果问题
"If [product] worked perfectly, what would be different in your life?"
"How do you know when you've succeeded at [the job]?"
"如果[产品]能完美运行,您的生活会有什么不同?"
"您怎么知道自己已经完成了[任务]?"
Wrap-Up
收尾
"If [product] disappeared tomorrow, what would you do instead?"
undefined"如果[产品]明天就消失了,您会用什么替代它?"
undefinedJob Analysis Template
任务分析模板
markdown
undefinedmarkdown
undefinedJob Analysis: [Customer Segment]
任务分析:[客户群体]
The Job (One Sentence)
任务(一句话)
"Help me _________________ so I can _________________"
"帮我_________________,这样我就能_________________"
Three Dimensions
三个维度
| Dimension | The Job | Evidence |
|---|---|---|
| Functional | ||
| Emotional | ||
| Social |
| 维度 | 任务 | 证据 |
|---|---|---|
| 功能性 | ||
| 情感性 | ||
| 社会性 |
Forces of Progress
进展驱动力
| Force | Description | Strength (H/M/L) |
|---|---|---|
| Push | ||
| Pull | ||
| Anxiety | ||
| Habit |
| 力量 | 描述 | 强度(高/中/低) |
|---|---|---|
| 推力 | ||
| 拉力 | ||
| 焦虑感 | ||
| 习惯惯性 |
Job Map
任务地图
| Step | What They Do | Struggle Points | Desired Outcomes |
|---|---|---|---|
| Define | |||
| Locate | |||
| Prepare | |||
| Confirm | |||
| Execute | |||
| Monitor | |||
| Modify | |||
| Conclude |
| 步骤 | 客户行为 | 痛点 | 期望结果 |
|---|---|---|---|
| 定义 | |||
| 筹备 | |||
| 准备 | |||
| 确认 | |||
| 执行 | |||
| 监控 | |||
| 调整 | |||
| 收尾 |
Competition (All Solutions for This Job)
竞争对手(所有解决该任务的方案)
- [Solution] - How it gets the job done
- [Solution] - How it gets the job done
- [Solution] - How it gets the job done
- [解决方案] - 它如何完成任务
- [解决方案] - 它如何完成任务
- [解决方案] - 它如何完成任务
Key Insights
关键洞见
Opportunities
机会
undefinedundefinedJob Story Template
任务故事模板
markdown
undefinedmarkdown
undefinedJob Stories for: [Feature/Product]
任务故事:[功能/产品]
Job Story 1
任务故事1
When [situation/trigger]:
I want to [motivation]:
So I can [expected outcome]:
当 [场景/触发因素]:
我想要 [动机]:
这样我就能 [预期结果]:
Job Story 2
任务故事2
When [situation/trigger]:
I want to [motivation]:
So I can [expected outcome]:
当 [场景/触发因素]:
我想要 [动机]:
这样我就能 [预期结果]:
Job Story 3
任务故事3
When [situation/trigger]:
I want to [motivation]:
So I can [expected outcome]:
当 [场景/触发因素]:
我想要 [动机]:
这样我就能 [预期结果]:
Notes
备注
- Key circumstance details:
- Emotional state:
- Social context:
---- 关键场景细节:
- 情绪状态:
- 社会环境:
---Skill Boundaries
方法边界
What This Skill Does Well
该方法擅长的事
- Structuring audio production workflows
- Providing technical guidance
- Creating quality checklists
- Suggesting creative approaches
- 构建音频制作工作流
- 提供技术指导
- 创建质量检查清单
- 提出创意方法建议
What This Skill Cannot Do
该方法不擅长的事
- Replace audio engineering expertise
- Make subjective creative decisions
- Access or edit audio files directly
- Guarantee commercial success
- 替代音频工程专业知识
- 做出主观创意决策
- 直接访问或编辑音频文件
- 保证商业成功
References
参考资料
- Books: Competing Against Luck (Christensen), Jobs to be Done: Theory to Practice (Ulwick)
- Institute: Christensen Institute for Disruptive Innovation
- Framework: Outcome-Driven Innovation (Strategyn)
- Source:
sources/books/christensen-jobs-to-be-done.md
- 书籍: 《与运气竞争》(Christensen)、《Jobs to be Done: Theory to Practice》(Ulwick)
- 机构: 克里斯滕森颠覆性创新研究所
- 框架: 结果驱动创新(Strategyn)
- 来源:
sources/books/christensen-jobs-to-be-done.md
Related Skills
相关技能
- positioning-dunford - Position your product for the job it does best
- category-design - Create categories around jobs that need solving
- buyer-personas - Complement JTBD with who has these jobs
- grand-slam-offers - Design offers that address the full job
- conversion-copywriting - Use job language in your copy
- positioning-dunford - 为产品定位最适合的任务
- category-design - 围绕需要解决的任务创建类别
- buyer-personas - 用目标人群补充JTBD
- grand-slam-offers - 设计能满足完整任务的方案
- conversion-copywriting - 在文案中使用任务相关语言 ",