Intercom Job Story Template
Source: https://s3.amazonaws.com/marketing.intercomcdn.com/assets/Intercom-Job-Story-template.pdf ↗
A short Intercom template that translates Jobs-To-Be-Done into a story format — the "When [situation], I want to [motivation], so I can [expected outcome]" structure that has become common in product teams.
The template is one page, which is its value: it compresses a long conversation into a format that everyone in a meeting can share.
For product direction the template is useful as a conversation tool, particularly when the team has spent too long discussing features and not enough time articulating the underlying stories.
Pair it with the Intercom JTBD book for the full context. A practical artefact, short enough to use tomorrow.
Central argument
The Intercom Job Story Template argues that user needs are best captured not as personas or feature requests but as situational narratives following the structure 'When [situation], I want to [motivation], so I can [expected outcome].' The central claim is that this format — derived from Clayton Christensen's Jobs-To-Be-Done theory — forces teams to anchor decisions in context and causality rather than demographics or assumed functionality. By compressing the JTBD conversation into a single shareable sentence, the template asserts that alignment in product teams comes from shared story, not shared specification.
Critique
The template's compression is also its blind spot: the 'When / I want / so I can' structure can create an illusion of alignment while masking deep disagreements about who the user actually is, how the situation was validated, or whether the stated motivation reflects observed behaviour or internal assumption. Because the format is so easy to fill in, teams can produce syntactically correct job stories that are empirically hollow — the template offers no mechanism for distinguishing a story grounded in research from one invented in a meeting room. The artefact, detached from the discovery process that should precede it, risks laundering guesswork into the appearance of user insight.
Why it matters for product
For a CPO managing multiple teams, the job story format is most valuable as a forcing function during roadmap reviews: if a team cannot articulate their initiative as a coherent job story, that is a diagnostic signal that feature thinking has outpaced problem understanding. It also creates a common language across design, engineering, and commercial stakeholders without requiring everyone to have read the underlying JTBD literature — reducing the translation cost that typically erodes strategic intent as it moves from product direction into delivery. The one-page constraint matters organizationally: it sets a precedent that clarity of problem framing is a prerequisite for investment, not a deliverable that comes after.