Jobs To Be Done for Marketers — Playbook #2
Jobs To Be Done for Marketers — Playbook #2. The goal isn’t clever—it’s clarity people can repeat after hearing it once.
A name is a handle for memory and meaning; pronounceable beats punny.
Steps
- Design constraints before concepts — Constraints produce coherence; they are not creative jail.
- Define the audience and their stakes — Name who loses what if nothing changes; real stakes sharpen choices.
- Document decisions in one page — People use what they can read in two minutes.
- List three proof points — Social, data, demos. Proof turns belief into trust.
- State the promise in plain words — Avoid poetry; say the outcome a buyer can point to later.
Why this matters: Constraints produce coherence; they are not creative jail. In branding, consistency is a function of decisions captured and reused.
Why this matters: Name who loses what if nothing changes; real stakes sharpen choices. In branding, consistency is a function of decisions captured and reused.
Why this matters: People use what they can read in two minutes. In branding, consistency is a function of decisions captured and reused.
Why this matters: Social, data, demos. Proof turns belief into trust. In branding, consistency is a function of decisions captured and reused.
Why this matters: Avoid poetry; say the outcome a buyer can point to later. In branding, consistency is a function of decisions captured and reused.
Toolkit
- Positioning line — For [audience] who struggle with [problem], we deliver [outcome], proven by [proof].
- Voice ladder — From formal to playful with examples for each channel.
- Messaging blocks — Headline • subhead • bullets • CTA mapped to page sections.
- Palette tokens — CSS variables / design tokens for color and spacing across apps.
How to use it: For [audience] who struggle with [problem], we deliver [outcome], proven by [proof]. Save the final in a shared doc; link from tickets so execution matches intent.
How to use it: From formal to playful with examples for each channel. Save the final in a shared doc; link from tickets so execution matches intent.
How to use it: Headline • subhead • bullets • CTA mapped to page sections. Save the final in a shared doc; link from tickets so execution matches intent.
How to use it: CSS variables / design tokens for color and spacing across apps. Save the final in a shared doc; link from tickets so execution matches intent.
Related Articles
- Website IA for SaaS Brands — Guide #2
- Onboarding Emails that Feel On‑Brand — Playbook #2
- Messaging Hierarchy for Landing Pages — Guide #2
- Palette Systems: Color With a Job
← Previous: Messaging Hierarchy for Landing Pages — Field Notes #2 Next: ICP vs Buyer Persona: What’s the Difference? — Field Notes #2 →