📊The LNO Framework
Shreyas Doshi's deceptively simple task-classification system: Leverage, Neutral, Overhead. Use it daily.
PMs are drowning in tasks. The LNO framework helps you triage which tasks deserve perfectionism, which deserve adequacy, and which deserve a 5-minute satisficing pass. It's the most-used mental model among senior PMs.
Every task is one of three types. **Leverage** tasks (high-impact, often strategy or 0→1 work) deserve perfectionism — your A-game, multiple drafts. **Neutral** tasks (most operational PM work) deserve adequacy — get them done well, don't over-polish. **Overhead** tasks (status updates, meetings, admin) deserve minimum viable effort — do them fast and move on.
The three buckets
Leverage. A 10% improvement here compounds for years. Examples: writing the team's annual strategy, the discovery for a 0→1 product, hiring a key engineer, the launch narrative for a major product. Spend disproportionate time.
Neutral. Most of your work. Examples: typical PRDs, regular team syncs, weekly metric reviews. Aim for "good," not "perfect." Diminishing returns set in fast.
Overhead. Compliance work that has to happen but doesn't compound. Examples: status updates, expense reports, calendar admin. Spend minimum viable time.
How to apply LNO
Once a week, look at your task list. Categorize each as L, N, or O.
- L tasks should be done in your best 3-4 hours of the day (typically morning).
- N tasks fill the middle of the day.
- O tasks get batched and crushed in 30 min at the end of the day.
The trap most PMs fall into: spending L energy on N or O tasks (polishing a status update for 45 min when 10 min would do). The cost isn't the 35 min — it's that you've spent your peak energy on overhead and now have nothing left for the strategy doc.
The harder skill: knowing what's L
A lot of PMs misclassify N as L. The annual planning offsite feels like leverage; often it's just neutral or even overhead. True leverage tasks have a multi-year payback and tend to involve writing, hiring, or strategic bets.
Test: "if I did this 20% better, would the team's outcome 12 months from now be meaningfully different?" If yes, it's L. If no, it's N or O.
Pairing with the calendar
Shreyas's broader point: arrange your calendar around the L tasks first, then fit N and O in the remainder. The default — letting meetings fill the calendar and doing L work in the gaps — guarantees L work gets shortchanged.
Real-world examples
Stripe PMs are famously obsessive about narrative documents — the strategy briefs, the launch docs, the long-form thinking pieces. These are treated as L tasks and get peak energy. Status updates and admin get crushed in 15 min. The discipline shows up in the clarity of Stripe's product strategy.
Go deeper — recommended reading
Interview questions (1)
Q1How do you decide what to spend your time on as a PM?behavioralmid▼
I use Shreyas Doshi's LNO framework. Every task is Leverage (high-impact, compounds), Neutral (gets done well), or Overhead (just gets done).
In practice this means I do my hardest L work — annual strategy, major PRDs, hiring — in my first 3 peak hours of the day. N tasks fill the middle. O tasks get batched at end of day in 30 min.
The non-obvious move: most PMs misclassify N work as L. The annual planning offsite feels like leverage; often it's just neutral. I test by asking 'if this were 20% better, would the team's outcome 12 months out be meaningfully different?' That filter sorts most things.