Identity-Led Product Focus
Define what the product must be, then reject features that dilute it
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 99%
Ahmed links Whoop's differentiation to a clear identity: continuous health monitoring rather than a general-purpose smartwatch. That identity defines exclusions—no screen, calls, apps, or step-count emphasis—and also justifies expensive choices, such as a charger that works while the device remains on the body. The decision test begins with the core job and the conditions required to perform it. A feature that protects continuous monitoring can merit cost and delay; an attractive feature that opens unrelated product meetings and competitive categories can be rejected. Focus becomes harder after success because more resources make adjacent opportunities look affordable while hiding their mental and organizational cost. The framework therefore treats a “not building” list as strategic infrastructure and requires leaders to recheck scope as the company grows.
Origin
Extracted from The Diary of a CEO. Will Ahmed explains how Whoop's 24/7 health-monitoring identity led it to reject a screen and invest in on-body charging despite repeated pressure to become a watch.
Core principles
- 01A clear product identity defines both what to build and what to refuse
- 02First principles can justify an expensive feature when it protects the core job
- 03A screen or adjacent capability can create hidden scope and competition
- 04Success increases the temptation to abandon the focus that produced it
- 05Distinctiveness often requires uncomfortable discipline
How to run it
- 1
Define the Core Job
Write the single job at which the product intends to excel. Make the wording specific enough to exclude plausible adjacent products.
Pro tip Ahmed frames Whoop around continuous health monitoring, not wearable computing in general.
Watch out A declared identity is a hypothesis until customers and evidence support it.
- 2
Derive the Non-Negotiable Condition
Ask what must remain true for the product to perform that job. Use first principles rather than copying category conventions.
Pro tip For Whoop, effective health monitoring implied 24/7 wear.
- 3
Write the Exclusion List
Name features, categories, and behaviors the product will deliberately avoid. Explain how each could dilute the core job or widen the competitive field.
Pro tip Make exclusions visible in roadmap discussions.
- 4
Evaluate the Full Focus Cost
For every proposal, estimate not only money but also meetings, mental attention, new dependencies, and follow-on scope. Compare that cost with its contribution to the core job.
Pro tip Ask what requests become inevitable once the first adjacent feature exists.
- 5
Fund Core Enablers
Accept expense or delay when a feature directly protects the product's defining condition. Document the first-principles link so the choice survives short-term pressure.
Pro tip Differentiate costly focus from costly ornament.
- 6
Recheck After Success
Review whether new resources and customer reach are encouraging unfocused expansion. Keep ambitious ideas separate from commitments until the organization can support full focus.
Pro tip Treat success as a reason for a stricter focus review, not a looser one.
In the wild
Ahmed says adding a screen and time display would pull Whoop into watches and invite notifications, colors, voice memos, and other scope. The company instead kept the product screenless and invested in a modular charger so users could continue wearing it.
→ Product decisions remained tied to continuous health monitoring rather than category convention.
Illustrative example: a focused writing tool considers adding full project management. The team maps the extra meetings, permissions, notifications, and support burden, then rejects it because those costs weaken the core writing experience without improving it.
→ The roadmap preserves distinctiveness instead of following a broad competitor feature list.
Common mistakes
Counting Only Build Cost
Adjacent products also consume leadership attention, team focus, and future roadmap capacity.
Copying Category Convention
Whoop's differentiated choices came from the monitoring job rather than assuming every wearable needed a screen or step count.
Letting Success Broaden Everything
Ahmed calls success a bad teacher when it encourages expansion without the intensity applied to the original product.
Is it for you?
Best for
It is best for product leaders competing against larger companies where a narrow, distinctive job can create an advantage.
Not ideal for
It is not ideal when the core job is still unvalidated or when focus is used to dismiss decisive customer or safety evidence.
From the transcript
“what you're not building”
“the second there's a screen there's this enormous scope creep”
“true Innovation often comes from a level of focus”
From the episode
Whoop Founder: How I Built A $3.6 BILLION Company & BEAT Apple! Will Ahmed