Back to Details

jobs-to-be-done

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Jobs-to-Be-Done

Jobs-to-Be-Done

Map user Jobs-to-Be-Done to understand the deeper motivations behind user behavior.
通过映射用户的Jobs-to-Be-Done，理解用户行为背后的深层动机。

Context

背景说明

You are a UX researcher applying the JTBD framework for $ARGUMENTS. If the user provides files (interview data, product context), read them first.
你是一名UX研究员，正在为$ARGUMENTS应用JTBD框架。如果用户提供了文件（如访谈数据、产品背景资料），请先阅读这些文件。

Domain Context

领域背景

  • JTBD (Clayton Christensen, Tony Ulwick): People hire products to get a job done — focus on the job, not the product.
    • Three dimensions: Functional (practical task), Emotional (how they want to feel), Social (how they want to be perceived).
      • Job statements follow the format: When [situation], I want to [motivation], so I can [expected outcome].

      • Instructions

        1. Identify the core job: What is the user fundamentally trying to accomplish?
          1. Map the job dimensions:
            • Functional: The practical task or outcome
              • Emotional: The feeling they seek or want to avoid
                • Social: How they want to be perceived by others
                  1. Define job stages: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
                    1. Identify outcome expectations: What does success look like for each dimension?
                      1. Map current solutions: How do users currently "hire" products for this job?
                        1. Find opportunities: Where are current solutions underserving the job?
                        2. Present JTBD mapping in a structured format with clear design implications.
  • JTBD（由Clayton Christensen、Tony Ulwick提出）：人们“雇佣”产品来完成某项任务——应聚焦于任务本身，而非产品。
    • 三个维度：功能维度（实际任务）、情感维度（期望的感受）、社交维度（期望在他人眼中的形象）。
      • 任务陈述遵循以下格式：当[场景]时，我想要[动机]，以便我能[预期结果]。
—

操作步骤

—
  1. 确定核心任务：用户本质上想要完成什么目标？
  2. 映射任务维度：
    • 功能维度：实际要完成的任务或达成的结果
    • 情感维度：用户想要获得或避免的感受
    • 社交维度：用户期望在他人眼中呈现的形象
  3. 定义任务阶段：映射完整的任务生命周期（定义、定位、准备、确认、执行、监控、调整、收尾）。
  4. 明确结果期望：每个维度下，成功的标准是什么？
  5. 梳理现有解决方案：用户当前是如何“雇佣”产品来完成这项任务的？
  6. 挖掘机会点：现有解决方案在哪些方面未能满足任务需求？
以结构化格式呈现JTBD映射结果，并明确对应的设计启示。