State the job without the product
When: Roadmap conversations happen entirely in feature language. The team can describe what the product does but struggles to say what progress the customer is trying to make. Competitor analysis only lists products in the same category, and nobody has asked what else customers hire for the same job.
The action: Write the job statement with no mention of the product, the technology, or the category. Verb, object of the verb, context. Test it by asking whether the statement was true before the product existed and would remain true if the product disappeared. Then list everything customers currently hire to get that job done, including doing nothing.
Forces: A solution-free statement feels abstract to teams paid to ship features, against the cost of optimising a product for a job nobody holds. Statements pitched too broad become mission statements and statements pitched too narrow become feature specs, and finding the level is judgement work. The exercise threatens roadmap items with sunk sponsorship.
Signals: Within weeks, at least one roadmap item is redescribed in terms of the progress it serves, or cut because it serves none. The competitor list changes to include non-obvious alternatives. New feature proposals arrive with a job attached.
When not to: When the job is trivial and fully known, as in commodity or compliance work where the buyer's progress is not in question. When the team is using the exercise to relitigate a decision already made on other grounds, since a job statement is an instrument for discovery, not a debating trophy.
Instance: Ulwick's account of the Cordis angioplasty work, in which restating the market around the job of restoring blood flow rather than around catheter features reordered the product line and its share.
Licensed under CC BY-SA 4.0.