Jobs Stories
Jobs Stories without the jargon: a clear definition, a real method, and honest benchmarks. Aimed at marketers, growth teams, and strategists.
Key takeaways
- Jobs Stories is a topic within Marketing Concepts — a concrete choice, not a vague best practice.
- Use public benchmarks for orientation; measure your own baseline for targets.
- Pair every primary number with a counter-metric so the goal cannot be gamed.
- Break the goal into named inputs, each with a single accountable owner.
- Skipping the current-state audit is the fastest way to fix the wrong thing.
What Jobs Stories covers
Jobs Stories belongs to Marketing Concepts, the discipline of the foundational ideas, frameworks, and mental models marketers use to make strategy and execution decisions, and the goal here is a usable handle rather than a glossary line. That is the whole idea.
Most teams treat this as reporting; it is really a set of choices. Jobs Stories belongs to Marketing Concepts — the discipline of the foundational ideas, frameworks, and mental models marketers use to make strategy and execution decisions. The goal is to make it concrete enough to defend in a review. It goes wrong when it stays a phrase nobody has pinned down. Pin it to something you can state in a sentence and defend in a review.
Jobs Stories reframe customer research around the moment of struggle. Alan Klement's structured format and how it differs from user stories and personas.
Jobs Stories are a structured format for customer research and product design popularized by Alan Klement (Intercom alum, author of "When Coffee and Kale Compete"). The format: "When [situation], I want to [motivation], so I can [expected outcome]." Designed to focus the team on the moment of struggle the customer faces, the underlying motivation, and the outcome they want — without committing to a specific solution.
User stories (the agile-development standard) start with the user's identity: "As a [persona], I want [feature], so that [benefit]." Jobs Stories start with the situation: "When [context], I want [motivation], so I can [outcome]." The shift moves the team's attention from demographics to circumstances. A 30-year-old marketer in Brooklyn and a 50-year-old executive in Tokyo can face the same job in the same situation.
User story: "As a small business owner, I want a marketing tool that's easy to use, so I can save time."
Established references on the topic include HBR, Reforge, and Think with Google. A shared set of references is what makes a fast meeting possible. Everything below is an elaboration of that one point.
How Jobs Stories works in practice
Jobs Stories depends less on the tool and more on a clean definition and honest measurement, then improve them one at a time. Hold that thought.
Under the surface it is mostly bookkeeping and honest comparison. Take the goal apart, give every part a name and an owner, then watch it. Done right, each person can point to the lever they personally move.
| Element | What it is |
|---|---|
| Owner | The single person accountable for the number. |
| Counter-metric | The number you watch so you are not gaming the goal. |
| Signal | The measurable change that tells you it worked. |
| Decision | The action a given reading should trigger. |
Review it on a fixed cadence: a weekly glance, a monthly read, a quarterly reset. Easy to agree with in a meeting, easy to forget by Thursday.
How to apply Jobs Stories
The path is short: agree the definition, measure cleanly, test one change, write down the result. Use that as the anchor.
- Define the term out loud. Pin it to a single sentence in plain words. If colleagues define it differently, fix that before anything else.
- Instrument before you optimize. Check the tracking is honest and complete. An unreliable number makes optimization a coin flip.
- Change one thing and test it. Run a controlled comparison rather than a vibe. Isolate the variable so the result is causal, not a coincidence of seasonality or mix.
- Review on a cadence and write it down. Write down the change, the effect, and the next idea. Notes are what keep the team from repeating old work.
Do not jump ahead. Each step only works once the one before it is done. That single idea is what separates a tidy program from a busy one.
Grounding Jobs Stories in real numbers
Ground the numbers around it in public benchmarks rather than internal folklore. Worth saying plainly.
Public figures tell you the rough shape; your own data sets the target. Context decides whether a number means anything; copied figures usually do not. Let the benchmark below orient you; your baseline is what sets the target.
Claim: Apple states App Tracking Transparency prompts began with iOS 14.5 in April 2021. Source: [Apple]. Context: Most attribution gaps in mobile reporting trace back to this change.
Where a number here is not externally sourced, treat it as RGM analysis of patterns across audits. Treat it as a starting question for your own data.
Common mistakes with Jobs Stories
The usual failure modes are a fuzzy definition, a local optimization, and a missing counter-metric. Everything else follows from it.
The mistakes that quietly cost the most
- Reporting the number without naming the decision it should drive.
- Changing several things at once, so no result is attributable.
- Chasing a precise number when the decision only needs a rough direction.
Most are quiet failures; nothing breaks, the number just drifts. Naming them in advance is worth the few minutes it takes.
Quick answers
- How should a team treat Jobs Stories day to day?
- As a recurring decision, not a one-time setting. Name it, measure it, and revisit it on a cadence so the choice stays matched to the current goal.
- Can small teams use Jobs Stories?
- Yes. Smaller teams often apply it better because fewer handoffs mean the person who owns the lever also owns the number.
- Where do RGM observations fit here?
- Any pattern labelled RGM analysis comes from reviewing real accounts. It is offered as a tested hypothesis, never as a substitute for measuring your own data.
Frequently asked
What is Jobs Stories in simple terms?
Jobs Stories is a topic within Marketing Concepts, the discipline of the foundational ideas, frameworks, and mental models marketers use to make strategy and execution decisions. In plain terms, this page treats it as a recurring decision your team can make with a shared definition instead of restarting the debate each time.
Why does Jobs Stories matter?
It matters because it shapes how budget, effort, and attention get allocated. When jobs stories is defined and measured well, spend follows what works; when it is fuzzy, spend follows whoever argues hardest.
How do you measure Jobs Stories?
Pick one primary number, instrument it cleanly, and pair it with a counter-metric so you are not gaming the goal. Then compare against a pre-change baseline rather than an industry average.
What references help with Jobs Stories?
Useful reference points include HBR, Reforge, and Think with Google. Tools matter less than a clean definition and trustworthy measurement; a good tool on a bad definition still produces a misleading dashboard.
What is the most common mistake with Jobs Stories?
Optimizing it in isolation. A local improvement that ignores the downstream business effect can look like a win on the dashboard while costing money elsewhere.
How often should you review Jobs Stories?
Review it on a fixed cadence: a weekly glance, a monthly read, a quarterly reset. The point is a fixed rhythm, so slow drift gets caught before it becomes a quarter-sized problem.
Sources cited on this page
- HBR Marketing — hbr.org/topic/marketing
- Reforge — www.reforge.com/blog
- Think with Google — www.thinkwithgoogle.com