# Headline communicates an outcome, not just a feature

- **Pattern:** `ab-001719` (`marketing-content-quality.value-proposition.headline-communicates-outcome`)
- **Severity:** critical
- **Lifecycle:** active
- **Last modified:** 2026-04-18
- **Canonical URL:** https://auditbuffet.com/patterns/ab-001719
- **License:** CC-BY-4.0 — attribute to AuditBuffet Pattern Catalog (https://auditbuffet.com/patterns/ab-001719)

## Why it matters

Feature-based headlines describe what the product has. Outcome-based headlines describe what the visitor gets. The distinction matters because visitors are not buying a feature — they are buying a result: faster shipping, fewer support tickets, a design that doesn't embarrass them. When the headline names only a feature ("AI-powered analytics dashboard") or a technology attribute ("Real-time collaboration platform"), the visitor must do mental translation work to connect the feature to their own situation. Many of them won't bother. Headlines that name the outcome — "See what's actually driving revenue" — do that translation for the visitor, making the product immediately relevant without effort.

## Severity rationale

Critical because a feature-framed headline forces every visitor to translate the feature into a personal benefit before they can evaluate relevance — most won't, and will leave before the sub-headline can recover.

## Remediation

Read your current `<h1>` aloud and ask: "Is this about the product, or about me (the user)?" If it describes the product's capabilities rather than the user's future state, reframe it.

Transformation examples:
```
Before: "AI-powered project management"
After:  "Ship what your team actually finishes"

Before: "Real-time collaboration platform"
After:  "Your team, finally on the same page"

Before: "Enterprise-grade security"
After:  "Ship fast without compromising compliance"
```

The reframe is one step: find the outcome the feature enables, and lead with that. In `app/page.tsx`, locate the `<h1>` and update the string. If the headline is rendered from a CMS or from a constants file (`lib/constants.ts`, `content/home.mdx`), trace the source and update it there so all pages remain consistent.

## Detection

- **ID:** `headline-communicates-outcome`
- **Severity:** `critical`
- **What to look for:** Count all relevant instances and enumerate each. Read the primary `<h1>` on the home page (and any dedicated landing pages). Determine whether the headline describes an outcome the user achieves (e.g., "Ship faster", "Never lose a lead again", "Your team's shared inbox") or only describes a feature or attribute of the product (e.g., "Advanced analytics dashboard", "AI-powered platform", "Next-generation tooling").
- **Pass criteria:** The primary headline on the home page references a user outcome, a problem being solved, or a transformation — not merely the existence of a feature or the product's technical attributes. At least 1 implementation must be verified. A partial or placeholder implementation does not count as pass.
- **Fail criteria:** The headline describes only a feature, technology, or generic category without connecting it to a user benefit or outcome. Examples of failing headlines: "AI-Powered Project Management", "Real-time collaboration platform", "Enterprise-grade security".
- **Skip (N/A) when:** No home page or landing page detected. Signal: API-only project with no public-facing routes.
- **Detail on fail:** Quote the actual headline and explain what is missing. Example: `"Headline reads 'Next-generation project management' — describes category, not outcome. No user benefit is stated."` or `"Headline is 'Powered by AI' — describes technology attribute only."`
- **Remediation:** Feature-based headlines make visitors work to understand why they should care. Outcome-based headlines do that work for them.

  Reframe your headline around what the user achieves:
  - Instead of "AI-powered analytics" → "See what's actually driving revenue"
  - Instead of "Real-time collaboration" → "Your team, finally on the same page"
  - Instead of "Enterprise-grade security" → "Ship fast without compromising compliance"

  The test: after reading your headline, can a visitor answer "What will I be able to do (or stop worrying about) if I use this?" If not, rewrite it.

  Review the configuration in `src/` or `app/` directory for implementation patterns.

- **Cross-reference:** For a deeper analysis of landing page conversion structure, the Marketing Site Conversion Optimization Audit covers this in detail.

Taxons: content-integrity

HTML version: https://auditbuffet.com/patterns/ab-001719