Shreyas Doshi
Former PM leader at Stripe, Twitter, Google, and Yahoo. The guest whose frameworks have become standard vocabulary in the Lenny’s audience: LNO tasks, the Pre-Mortem, “high agency,” and the distinction between outputs and outcomes.
Core Ideas
LNO Task Framework
Shreyas’s most widely adopted framework classifies every task a PM does into one of three categories:
| Type | Definition | Strategy | Example |
|---|---|---|---|
| Leverage | Tasks where exceptional execution produces disproportionate returns | Invest maximum effort; these define your impact | Annual planning, critical product decisions, key hires |
| Neutral | Tasks where quality matters but exceptional effort has diminishing returns | Do well, but do not over-invest | Routine presentations, standard meetings, operational reviews |
| Overhead | Tasks that must be done but where extra effort adds no value | Minimize time; delegate or batch | Expense reports, status updates, administrative email |
The insight is not that overhead tasks are unimportant — it is that most PMs spend too much energy on Neutral and Overhead tasks at the expense of Leverage tasks. The LNO framework is a daily prioritization tool: before each task, ask “Is this L, N, or O?” and allocate effort accordingly.
The Pre-Mortem: Tigers, Paper Tigers, and Elephants
Before launching a project, Shreyas recommends classifying risks into three categories:
| Risk Type | Description | Response |
|---|---|---|
| Tigers | Real risks that will kill the project | Must address before proceeding |
| Paper Tigers | Risks that feel scary but are unlikely or manageable | Acknowledge and move on; do not let them delay |
| Elephants | Risks everyone sees but nobody is willing to name | Surface explicitly; these are the most dangerous because they are unaddressed |
The pre-mortem exercise: imagine the project has failed. What went wrong? Classify each failure scenario as a Tiger, Paper Tiger, or Elephant. The exercise surfaces Elephants that team politeness would otherwise leave undiscussed.
High Agency
Shreyas distinguishes between high-agency and low-agency behavior in PMs:
- High agency: “This is blocked. Here is my plan to unblock it.” Finds a way around obstacles, takes ownership of problems beyond their formal scope, creates options rather than waiting for instructions.
- Low agency: “This is blocked. I’ll wait for someone to unblock it.” Treats obstacles as permanent, stays within formal boundaries, escalates rather than solves.
High agency is the single trait Shreyas values most in PMs, and the one he considers hardest to teach.
Outputs vs. Outcomes
Shreyas is emphatic that PMs should be measured on outcomes (metrics that changed, customer problems solved) rather than outputs (features shipped, documents written). This connects directly to OKR design: Key Results should be outcomes, not task completions.
Key Appearances
| Episode | Focus | Listen For |
|---|---|---|
| Prioritization deep dive | LNO framework, RICE alternatives, handling stakeholder pressure | The LNO framework walkthrough |
| Pre-mortem episode | Tigers/Paper Tigers/Elephants, risk classification | How to run the pre-mortem exercise |
| High agency discussion | What high agency looks like, how to develop it | Concrete examples of high vs low agency behavior |
Notable Quotes
“The best PMs are not the ones who ship the most features. They are the ones who make the fewest decisions — but the right ones.”
“If your OKRs are a list of things to ship, they are not OKRs. They are a task list with corporate formatting.”
Key Takeaway
Shreyas provides the mental models that separate execution-focused PMs from impact-focused PMs. The LNO framework for daily prioritization, the Pre-Mortem for project risk, and the high-agency mindset for career growth are immediately applicable tools.
Related
- Roadmap Prioritization — LNO and prioritization frameworks
- OKRs — Outputs vs outcomes distinction
- Product Sense — High agency as a component of product judgment
- Hiring PMs — How to evaluate for high agency in interviews