Skip to content
lno home

The LNO framework by Shreyas Doshi

How much energy for which task

Leverage, Neutral, and Overhead. A way to decide how much attention the work requires — not only which work to pick up. Reserve excellence where quality compounds. Finish what is necessary. Spend as little as possible on the rest.

An independent educational tribute. Not affiliated with, endorsed by, or sponsored by Shreyas Doshi.

LNO is not only a prioritization framework. It is a framework for deciding how much effort, quality, and attention a task deserves.

Choosing what to do, deciding how well to do it, and asking whether the task should exist at all are three different decisions.

The framework

Three kinds of effort

Most priority systems choose the next task. LNO assigns an effort and quality budget after you know the task matters — or while you are deciding whether it should.

L

Leverage

Work that changes more than the hour you give it. Foundational, hard to reverse, and consequential for many later decisions.

Return
Multiplies
Standard
Excellent
  • Product strategy and the narrative that aligns a team
  • A pivotal customer insight
  • Architecture, security, or data boundaries
  • Hiring or coaching someone who will decide well without you

N

Neutral

Necessary work. Another hour makes it a little better, not a different outcome. Reliability matters. Polish past the bar does not.

Return
Linear
Standard
Good enough
  • A regular project update
  • A normal review or critique
  • Planning the week
  • Unblocking one implementation detail

O

Overhead

Work that consumes time without improving a meaningful outcome. It often looks legitimate because someone requested it.

Return
Below the hours
Standard
Adequate, or gone
  • The same status copied into a second tool
  • A ceremonial meeting with no decision
  • Formatting that no one will use to decide
  • Repetitive entry a template could hold

Overhead is not a moral failing, and Neutral is not a consolation prize. The label describes the marginal value of extra effort. A compliance task can be unexciting and still require a high minimum standard.

Practice

Classify a task

Answer from the work in front of you. The reading is a thinking aid, not an objective judgment. The same task can move when the stakes, the audience, or the timing change.

Load an example

Each example fills the form and shows a reading you can edit.

Write it the way you would hand it to someone else.

1If this were done exceptionally well, what would materially change?

Compare an excellent version with a merely adequate one.

2Does it affect strategy, revenue, retention, risk, or many future decisions?

Count consequences, not how busy or visible the task feels.

3Does the value persist after you finish?

Leverage keeps paying. Overhead expires when the ritual ends.

4What does extra craftsmanship buy?

Necessary is not the same as worth polishing.

5Could it be automated, delegated, templated, batched, or eliminated?

If the purpose is unclear, do not give the task a higher rank to compensate.

6What is pulling you toward this right now?

Overhead is often easier than the leveraged work you are avoiding.

Name the outcome, not the mood. “A readable update in twenty minutes” is a standard. “Do my best” is not.

What do you intend to do next?

Optional. If this disagrees with your answers, the reading will say so.

Your draft stays in this browser. Nothing is sent to a server.

Operating cadence

How to use it through a week

LNO fails when the label is a feeling you apply after the work is already polished. Decide the budget first.

  1. 01

    Capture the task

    Write the work in one concrete sentence. A vague item hides its real category.

  2. 02

    Classify it

    Call it Leverage, Neutral, or Overhead. The label may change when the stakes change. That is a feature.

  3. 03

    Name the minimum acceptable outcome

    Decide what done looks like before you start. This is the stopping rule, not a motivational note.

  4. 04

    Set the quality bar

    Excellent where quality compounds. Strictly good where it does not. Intentionally basic where the work is drag.

  5. 05

    Schedule Leverage in your best hours

    Leverage is usually proactive and resistant. If you leave it for the gaps, meetings and overhead will take the gaps.

  6. 06

    Timebox Neutral work

    Meet the bar and stop. A crisp update does not need a designed deck. A normal review does not need a treatise.

  7. 07

    Remove Overhead from the system

    The aim is not to finish overhead faster. It is to need less of it: delete, automate, delegate, template, or batch.

  8. 08

    Review the pattern weekly

    Ask where excellence actually went. A completed list of neutral and overhead work can still be a poorly spent week.

Say the standard before you start

Without a precommitment, conscientious people quietly expand every task toward leverage-level effort.

L · Leverage
I will produce a decision that can guide the next two quarters. I will use evidence, name the risks, and ask two informed people to disagree.
N · Neutral
I will send a readable, accurate update in twenty minutes. No custom charts.
O · Overhead
I will use the existing template, spend no more than five minutes, and remove the repeat step.

Where it sits beside other systems

Use another system to choose the bet. Use LNO to decide how much of your own attention the surrounding tasks deserve.

  • Eisenhower

    Asks: Is this urgent, important, both, or neither?

    LNO adds: A quality and effort budget, not only a sequence.

  • Impact and effort

    Asks: Is this initiative worth the cost?

    LNO adds: A way to govern the small tasks that still arrive after you choose.

  • OKRs

    Asks: Which outcomes matter this period?

    LNO adds: A way to turn those outcomes into the hours of a specific day.

  • Getting Things Done

    Asks: How do I capture every commitment?

    LNO adds: A challenge to the idea that every commitment deserves the same craft.

In practice

The same hours, different work

These are patterns, not assignments. A task moves when the company, the audience, or the moment moves.

Product managers

The trap is treating visible coordination as if it were the product.

  • L LeverageA strategy, a pivotal customer insight, or a decision that unblocks several teams.
  • L LeverageAn operating principle people can reuse without asking you.
  • N NeutralA regular update, a normal review, or unblocking one implementation detail.
  • O OverheadRecopying status into another tool, or a meeting where you do not decide, learn, or unblock.

Context changes the category

Do not tattoo the label onto an activity. Ask what this instance is for.

Documentation

  • L · Leverage

    It lets other people proceed well without you.

  • N · Neutral

    You are maintaining a source people already use.

  • O · Overhead

    You are copying that source into another format because a process asked for a copy.

A meeting

  • L · Leverage

    It resolves a high-stakes conflict or makes a hard-to-reverse decision.

  • N · Neutral

    It coordinates an active project and ends with owners.

  • O · Overhead

    It performs status. No one decides, learns, or gets unblocked.

A deck

  • L · Leverage

    It is the artifact a financing, a launch, or a company bet will actually use.

  • N · Neutral

    It is a routine internal review, and a clear memo would also do.

  • O · Overhead

    It repeats a one-page note that already holds the decision.

A limit on the idea

Selective excellence is not carelessness

LNO is not permission to do sloppy work, skip accountability, or ignore operational detail. It is a way to stop applying an unnecessarily high standard to every task.

Meet the minimum standard that preserves trust and correctness — then avoid unnecessary polish.
  • Safety

    An effort budget never lowers the bar for keeping people safe.

  • Security

    A review can be brief. It cannot be careless where a miss is expensive.

  • Legal and compliance

    Low excitement is not low obligation. Meet the standard the obligation requires.

  • Financial accuracy

    Numbers other people rely on get correctness. They do not get decoration.

  • Customer trust

    A short answer is fine. A misleading one, or a broken commitment, is not.

  • Reliability

    Incidents, data loss, and broken systems are not overhead.

  • Commitments to teammates

    Someone is waiting. Clear and on time beats ornate and late.

Do not use it as an excuse

The useful question is the minimum that preserves trust, safety, and correctness. Meet that floor. Then refuse the surplus.

The label is contextual

A fundraising deck can be leverage before a round, neutral in an internal review, and overhead when it only repeats a memo. Reclassify when the moment changes.

Say the scope out loud

If people expect a polished artifact, do not surprise them. Name what you will deliver, and what you will not, before the format expands on its own.

Weekly review

Look at the pattern, not the hours

A finished list is not evidence of a well-spent week. Ask whether excellence went to the few tasks where it compounds.

Nothing saved yet. Kept in this browser only.

Attribution

Shreyas Doshi

Shreyas Doshi created and teaches the LNO framework. He is a product manager and educator. The framework comes from that practice, including his work at Google, Twitter, Yahoo, and Stripe: reserve excellent work for the few tasks where quality multiplies, do necessary work to a solid standard, and consciously keep overhead merely adequate — or remove it.

“Do a bad job” is his deliberately sharp instruction for overhead. It means the shortest adequate version, from someone whose normal competence is already enough. It does not mean ignoring safety, security, the law, the numbers, customers, or the people you work with.