'The LNO Framework: Why Not All Work Is Equal and What to Do About It'

The LNO framework (Leverage, Neutral, Overhead) is a way to categorize your daily work so you can deliberately protect the tasks that actually move outcomes and ruthlessly compress the ones that do not.

The Trap Has a Uniform

Picture a PM on a Tuesday. She has responded to forty-three Slack messages before noon. She attended three syncs, one to give a status update she had already written in Confluence, one to "stay aligned" with a partner team whose decisions did not require her input, and one that could have been an email from the beginning. She blocked ninety minutes for the pricing strategy document that actually requires her judgment. She opened it twice and closed it both times.

That PM is not lazy. She is caught in a trap that looks exactly like diligence.

The LNO framework, originated by Shreyas Doshi, former PM leader at Stripe and Twitter, does not fix the trap automatically. What it does is make the trap visible, which is harder than it sounds.

What Leverage, Neutral, and Overhead Actually Mean

Leverage

Leverage tasks are the ones where your specific judgment produces a result that compounds beyond the hours you put in. A well-written strategy document that shapes six months of engineering decisions is Leverage. A crisp one-pager that kills a bad idea before it consumes a quarter of roadmap is Leverage. A hiring decision, made carefully, that brings someone onto the team whose output multiplies everyone else's, that is Leverage.

The defining characteristic is the multiplier. One hour of genuine Leverage work can redirect dozens of hours of other people's effort. That ratio is almost never available in Neutral or Overhead work.

Leverage is also, nearly always, uncomfortable. It involves ambiguity, real consequences, and the absence of a clear process to follow. There is no meeting invite that tells you it is time to think about strategy.

Neutral

Neutral tasks are necessary and real, they keep the machine running without accelerating it. Writing a spec that documents a decision already made is Neutral. Attending a sprint review to stay informed is Neutral. Preparing a roadmap slide for a stakeholder who asked for an update is Neutral.

These tasks are not a waste. If you skip them entirely, things break. The mistake is treating Neutral work as if it has the same return as Leverage, blocking your three most focused hours for it, running it at full creative effort, letting it crowd out everything else.

Neutral is best executed at minimum viable quality. "Good enough" is not a cop-out here; it is correct judgment.

Overhead

Overhead tasks are the ones where your presence, effort, or output adds nothing that a written update, a delegate, or simply nothing at all could not replace. Attending a weekly sync where you speak for two minutes and listen to fifteen minutes of content you will never use is Overhead. Responding immediately to a non-urgent Slack message at 9 PM is Overhead. Sitting in a meeting to represent your team's interests when the decision does not involve your team is Overhead.

Overhead feels like professionalism. That is what makes it dangerous.

It carries the social texture of being responsive, being present, being a good team citizen. None of that is wrong in principle. The problem is when Overhead displaces Leverage, when you spend the week being maximally available and minimally useful.

The Comparison Table

Where the Framework Came From, and What It Cost to Learn

Shreyas Doshi began articulating the LNO framework while at Stripe, where the PM culture was unusually rigorous about how product people spent their time. His observation was specific: there was a class of weekly syncs where his attendance added nothing that a written update could not cover equally well. His presence satisfied an organizational norm, not an actual informational need. Those meetings were Overhead.

The decision to stop attending them was not comfortable. Opting out of meetings carries social cost, it reads as disengagement to people who have not done the math. What Doshi found on the other side was time. The hours recovered from Overhead went toward the strategy and culture-building work that later shaped how Stripe thought about product management at scale. That influence is traceable. The hours spent in those weekly syncs are not.

This is not a story about working less. It is a story about what becomes possible when you stop mistaking attendance for contribution.

How to Audit a Single Week

You do not need a new system. You need forty minutes and your existing calendar.

Step one: Label every event and task block from last week. L, N, or O beside each item. Do not rationalize, if your primary role in a meeting was to receive information you could have read, that is O. If you were the decision-maker or the person whose specific judgment shaped the output, that is L.

Step two: Count the hours in each category. Most PMs, on their first audit, find something in the range of fifty to sixty percent Overhead, thirty to forty percent Neutral, and under fifteen percent Leverage. If your number is dramatically different, audit your instinct to upgrade O items to N.

Step three: Look at your Leverage hours specifically. Not just how many, but when. Were they in your best cognitive hours or the remnants? Were they protected from interruption or constantly broken up? Leverage work done in thirty-minute fragments is not Leverage work at its actual potential.

Step four: For every Overhead item, ask one question. What would actually break if I sent a written update instead of attending, delegated this, or simply did not do it this week? If the honest answer is "nothing material," you have found time.

The Judgment Turn

Here is what the framework does not say, and what you should hear anyway.

Most productivity advice tells you to do more of the important things. That is not wrong, but it skips the reason you are not doing them. The reason is that Overhead is socially rewarded. Responding quickly looks like commitment. Attending every meeting signals investment. Being perpetually reachable communicates that you care. None of this is false, but none of it is Leverage.

The career-defining work sits in the Leverage category. It is also the work that is easiest to defer because it does not come with a deadline, a meeting invite, or anyone following up to ask why you have not done it yet. Nobody pings you to say "you have not written the product strategy this week." Seventeen people ping you about the status update.

The LNO framework's real function is not to help you organize your time. It is to give you explicit permission to leave Overhead tasks undone or done poorly. That permission matters because without a named framework, deprioritizing a meeting or an async response feels like negligence. With it, the same decision feels like a deliberate allocation.

You still have to make the choice. The framework does not make it for you. What it does is make the cost of the wrong choice legible, not in abstract terms, but in the specific, compounding loss of hours that should have been strategy and were instead presence.

Key Takeaways

1. Leverage work has an output multiplier above 1:1, one hour shapes many others. Neutral maintains the machine at 1:1. Overhead costs time without proportional return.
2. Overhead feels like professionalism. That is the trap. Constant responsiveness is not a virtue when it displaces the thinking that only you can do.
3. Your Leverage hours are worth more in your best cognitive window than twice as many hours in fragmented, reactive time.
4. A weekly audit, forty minutes, honest labels, reveals the actual distribution. Most PMs are surprised. The surprise is the data.
5. The framework's value is permission: permission to leave Overhead undone, to do Neutral at minimum viable quality, and to protect Leverage work as the first priority rather than the last.

Related Articles

• When the Backlog Fight Is Actually a Strategy Fight
• Applying the Return on Time Invested Framework for Experiment Prioritization
• Why Your Roadmap Is Never Actually Data-Driven

What is on your calendar right now that you could not justify as Leverage if you had to explain it out loud?