Why First, Not What
8 minWhy First, Not What
Most product copy starts with what the product is. "Acme is a real-time data sync engine for React apps." The reader scans it, registers nothing, and keeps scrolling. The copy failed not because it was wrong, but because it answered a question nobody asked yet.
Simon Sinek's framework from Start With Why is the fix. Every piece of copy operates on three layers: Why (the user's motivation), How (the mechanism), and What (the product). Most copy leads with What. Strong copy leads with Why.
The order matters because the reader cares about Why before they care about How, and How before What. Bury the Why at the bottom of the page and you lose the only sentence that could have kept them reading.
The three layers
| Layer | Question it answers | Example | |---|---|---| | Why | Why does this matter to me? | Stale dashboards kill trust. | | How | How does the product address it? | StrataSync keeps every client in sync automatically. | | What | What is the product? | A real-time data layer for React apps. |
Lead with What and the reader has no reason to keep reading. Lead with Why and the reader is already nodding before you name the product.
The diagnostic test
Read the first sentence of any hero or README. Does it explain what the product is, or why someone would want it?
"StrataSync is a real-time data sync engine for React apps."
Leads with What. The reader has no reason to care.
"Stale dashboards kill trust. StrataSync keeps every client in sync automatically."
Leads with Why. The reader recognises their own problem.
The What-first version describes the product accurately. The Why-first version makes the reader feel understood. Only one of them earns the next scroll.
More inversions
"Introducing CloudBase, the all-in-one backend platform."
"A powerful analytics dashboard for modern teams."
"Our AI-powered workflow automation tool."
"Stop stitching together five services. One backend, already connected."
"See which features drive retention before users leave."
"Your Monday shouldn't start with tasks a machine can finish by Friday."
Every Why-first version names a frustration or outcome the reader can picture. The product is mentioned only after the motivation is established.
When to skip the Why
Not every context needs a Why-first opening. Three exceptions:
Already-warm traffic. Existing users in product onboarding or settings screens already know why they're there. Lead with How or What: "Connect your Stripe account to start syncing invoices."
Pricing pages. The reader is shopping, not being convinced. Lead with the offer. The Why was on the homepage.
Reference documentation. Engineers reading API docs want What and How. The Why lives on the marketing site.
The common mistakes
The Why has to be the user's Why, not the company's. "Our team is obsessed with developer experience" is founder voice. "You shouldn't have to babysit your pipeline" is user voice. The distinction is the difference between a brand talking about itself and a brand talking to its reader.
The other failure: a Why that's too abstract. "We believe in a more connected world" is a corporate mission statement. The user's Why is concrete: their actual frustration, their actual day, their actual outcome. Stale dashboards kill trust. That's a Why someone can feel.