Why first, not what

Lead with **Why** (the user's motivation), not **What** (the product). ## 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._ | ## The diagnostic test ## More inversions ## When to skip the Why Onboarding: users already know why. Lead with How. Pricing: the reader is shopping. Lead with the offer. Reference docs: engineers want What and How. ## Common mistakes The Why must be the _user's_ Why. "Our team is obsessed with developer experience" is founder voice. "You shouldn't have to babysit your pipeline" is user voice. "We believe in a more connected world" is a mission statement. _Stale dashboards kill trust_ lands because the reader has lived it.