LNO Framework
Match your effort to each task's leverage, neutrality, or overhead
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 99%
The LNO Framework sorts work by the impact returned for the effort invested. Leverage tasks produce tenfold or hundredfold impact, neutral tasks return roughly what you put in, and overhead tasks return much less than the effort they consume. The crucial insight is contextual: writing notes or filing a bug can fall into any of the three categories depending on the stakes. Once classified, effort should become deliberately uneven. Do leverage work at the time of day when energy and focus are highest, and allow perfectionism to improve it. Handle neutral work efficiently and overhead work with the minimum sufficient standard. This does not add hours; it transfers time and attention away from low-return polish. The framework also exposes avoidance, because the difficult task repeatedly postponed is often the real leverage task.
Origin
After three stressful years as a new Google PM, Doshi found related ideas in a blog post he can no longer locate and shaped them into the LNO Framework. It helped him stop treating an endless task list as if every item deserved equal care.
Core principles
- 01Tasks that look similar can produce radically different leverage
- 02Perfectionism belongs on leverage work
- 03Neutral and overhead work should fund time for leverage work
- 04Energy is an allocation variable, not just time
- 05The important task you avoid is often the leverage task
How to run it
- 1
Inventory the real workload
Write down the tasks currently consuming or competing for your time. Include small administrative work as well as the difficult strategic work you keep postponing.
Pro tip Look beyond the formal to-do list for unresolved conversations and decisions.
Watch out A list containing only urgent visible work will hide your highest-leverage obligations.
- 2
Classify by return on effort
Mark each task L if it can return tenfold or hundredfold impact, N if it returns roughly what you invest, and O if it returns far less. Classify the specific instance, not the generic activity.
Pro tip Ask what changes if this exact task is done exceptionally well.
Watch out Do not assume every PRD is leverage or every expense report is overhead without considering the consequences.
- 3
Protect peak energy for L tasks
Schedule leverage work when you are most productive and energetic. Give it sustained attention because the quality difference can multiply downstream impact.
Pro tip Change location if a new environment helps you cross the threshold into focused work.
Watch out Waiting for an empty week usually means the leverage task never starts.
- 4
Let perfectionism serve leverage
Polish a high-stakes strategy, PRD, decision record, or alignment conversation when precision will prevent large downstream costs. Make excellence selective rather than habitual.
Pro tip Spend extra time where ambiguity could cause teams to backtrack or misinterpret a decision.
Watch out Perfectionism applied indiscriminately starves the work where it actually pays.
- 5
Compress N and O work
Complete neutral tasks efficiently and overhead tasks to a minimum sufficient standard. Redirect the saved time to leverage work instead of expanding the workday.
Pro tip For routine meeting notes, send the decisions, owners, and action items immediately.
Watch out Do not confuse visible polish with impact.
In the wild
Doshi explains that a bug report is not inherently L, N, or O. A critical bug may justify an explicit report with detail and annotated screenshots because clarity changes the outcome. A low-stakes bug may need only one screenshot and a quick submission. The activity is identical, but the leverage of extra effort is not.
→ Effort scales with the consequence of the specific bug rather than with a fixed template.
After an ordinary meeting, Doshi would send the three action items and owners immediately. After a contentious CEO product review, he would spend one or two hours making the decision language exact so nobody could later misinterpret or relitigate it.
→ Low-stakes communication stays fast while high-stakes communication receives the precision its leverage warrants.
Common mistakes
Classifying activities instead of instances
Notes, bug reports, and PRDs do not have fixed leverage. Their category depends on the decision, audience, and consequences in that situation.
Doing L work after energy is depleted
Protecting only time is insufficient. The framework calls for doing leverage work when focus and energy are strongest.
Using LNO to justify careless work
Minimum sufficient effort still has to meet the task's real requirements. The framework removes unnecessary polish, not basic responsibility.
Is it for you?
Best for
Product managers, founders, and other people in creative, high-impact roles with an endless workload.
Not ideal for
Highly standardized operational work where most tasks have fixed procedures and similar consequences.
From the episode
Countdown of the top 10 episodes of the year