Story Structures That Sell — Field Notes #2
Story Structures That Sell — Field Notes #2. If your brand feels fuzzy to you, it’s fog to your audience. Let’s make it obvious and repeatable.
Voice is the personality; tone is the mood. Document both or drift wins.
Steps
- State the promise in plain words — Avoid poetry; say the outcome a buyer can point to later.
- Document decisions in one page — People use what they can read in two minutes.
- Define the audience and their stakes — Name who loses what if nothing changes; real stakes sharpen choices.
- List three proof points — Social, data, demos. Proof turns belief into trust.
- Design constraints before concepts — Constraints produce coherence; they are not creative jail.
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.
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: 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: Social, data, demos. Proof turns belief into trust. In branding, consistency is a function of decisions captured and reused.
Why this matters: Constraints produce coherence; they are not creative jail. In branding, consistency is a function of decisions captured and reused.
Toolkit
- Messaging blocks — Headline • subhead • bullets • CTA mapped to page sections.
- Voice ladder — From formal to playful with examples for each channel.
- Positioning line — For [audience] who struggle with [problem], we deliver [outcome], proven by [proof].
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: 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: 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.
Related Articles
- Category Design for Mortals — Playbook #2
- Voice & Tone Guides People Actually Use — Guide #2
- Personas That Don’t Lie — Pro Tips #2
- Differentiation Without Feature Fights — Case Files #2
← Previous: Category Design for Mortals — Playbook #2 Next: UX Writing That Sounds Like You — Guide #2 →