故事 · 通用任务地图怎么来的
Origin Story · Where the universal job map came from
Anthony Ulwick 在做 ODI(结果驱动创新)时发现一个规律:不管客户雇产品去完成什么任务,
这个任务都走着同一条通用路径 —— 先想清楚要做什么(定义),再找到需要的东西(定位),
把场子布置好(准备),核对一遍没问题(确认),然后真正动手(执行),盯着进展(监控),
出岔子就调整(修改),最后收尾(结束)。
关键不在于「执行」做得多漂亮,而在于:把每一步都拿放大镜扫一遍,问「客户在这步卡在哪?」。
一扫就会发现,大多数厂商都把心思花在「执行」这一步上比参数,
而客户真正抓狂的地方,往往是前面的准备、确认,或后面的监控、收尾 ——
那里没人竞争,正是创新的空地。
While developing ODI (Outcome-Driven Innovation), Anthony Ulwick spotted a pattern: no matter what job a customer hires a product for,
the job always travels the same universal path — first you figure out what you're trying to do (Define), then track down what you need (Locate),
set things up (Prepare), double-check that everything is right (Confirm), do the actual work (Execute), watch how it's going (Monitor),
adjust when something drifts (Modify), and finally wrap it up (Conclude).
The point isn't to nail Execute — it's to run a magnifying glass over every step and ask "where does the customer get stuck here?"
Do that and the same thing keeps happening: every vendor is crowding into Execute and benchmarking specs,
while the customer's real frustration sits in the Prepare and Confirm steps before, or the Monitor and Conclude steps after —
an empty playing field, and exactly where new offers can break through.
1 8 步任务地图 · 点每一步看机会 The 8-Step Job Map · Click each step to see the opportunity
做饭Cooking2 这一步:通用问法 · 本案例 · 改善机会 This Step: Universal Question · This Case · Opportunity
通用问法(与方案无关)Universal question (solution-agnostic)
点地图上的步骤查看。Click a step on the map.
本案例里这一步是In this case, this step is
点地图上的步骤查看。Click a step on the map.
改善机会Improvement opportunity
点地图上的步骤查看。Click a step on the map.
3 现实里的「机会藏在前后步」 "The Opportunity Hides Around Execute" in the Real World
做饭:痛点在备菜:翻炒只要几分钟,备菜(洗、切、配)才是最累最久的。净菜配送、预切食材正是抓住「准备」这一步。
Cooking — pain is in the prep: the stir-fry takes minutes; washing, chopping, and portioning take most of the evening. Pre-washed veg and meal-kit prep are companies grabbing the Prepare step.
看病:痛点在准备与确认:手术由医生完成,患者抓狂的是挂号、排队、找科室、核对资料。线上预约、智能分诊改的全是「执行」之前。
Healthcare — pain is in Prepare and Confirm: the doctor handles Execute; what drives the patient crazy is booking, queuing, finding the right department, and lining up paperwork. Online booking and AI triage attack everything before Execute.
报销:痛点在确认与监控:填单不难,难在凑齐发票、对清规则、追审批进度。电子发票、自动校验、进度推送,全在执行前后。
Expense reports — pain is in Confirm and Monitor: filling out the form is easy; what's hard is rounding up receipts, matching policy rules, and chasing approvals. E-receipts, automated compliance checks, and status pings all attack the steps around Execute.
方案无关:地图描述的是「定位输入」,不是「打开冰箱门」。先抽象出步骤,再问每步卡在哪,机会才不被现有产品的形状框死。
Solution-agnostic: the map describes "locate the inputs," not "open the fridge." Abstract the step first, then ask where the customer gets stuck — otherwise the opportunity gets boxed in by whatever product already exists.
一句话In One Line
任务地图的杀伤力,在于它逼你把一个任务从头到尾走一遍,而不是只盯着最显眼的「执行」步。
一旦你把 8 步都拿放大镜扫一遍,会反复撞见同一件事 ——
痛点几乎总躲在执行前后:备菜、挂号、凑发票、追进度。
这正是机会的所在:执行步挤满了竞争者,前后步却空空荡荡。
它还与方案无关 —— 描述的是「定位所需输入」,不是「打开某个 App」,
所以它不会被现有产品的样子困住,反而能照出全新的解法。
先把任务地图铺开,逐步找卡点,再决定产品该长什么样。
The power of the job map is that it forces you to walk a job from end to end, not just stare at the loudest step in the middle.
Once you put a magnifying glass over all 8 steps, the same fact keeps showing up —
the pain almost always hides around Execute: prep, booking, rounding up receipts, chasing approvals.
That's exactly where the opportunity lives: Execute is crowded with competitors, while the steps around it are empty.
And the map is solution-agnostic — it describes "locate the required inputs," not "open this app" —
so it doesn't get trapped by the shape of today's products and can surface entirely new solutions.
Lay out the job map first, find the bottlenecks step by step, and only then decide what the product should look like.
常见误用Common Mistakes
把任务地图当用户旅程图。旅程图是和某个产品的交互;任务地图与方案无关,描述客户要完成的过程本身。
Treating the job map like a user-journey map. A journey map describes interactions with a specific product; the job map is solution-agnostic and describes the process the customer is trying to complete.
只优化「执行」那一步(大家都挤在这)。把准备、确认、监控、收尾都扫一遍,差异化机会常在前后步。
Only optimizing "Execute" (where everyone else already is). Sweep through Prepare, Confirm, Monitor, and Conclude too — the differentiating opportunities almost always sit around Execute, not inside it.
步骤里塞进具体方案(如「打开 App」)。步骤要抽象 ——「定位所需输入」而不是「打开冰箱门」,否则会被现有产品框死。
Baking a specific solution into the step (e.g. "open the app"). Keep the step abstract — "locate the required inputs," not "open the fridge door" — otherwise the existing product silently caps your thinking.