The Full-Stack PM Triad: Sharpness, Drive, Influence
Raw sharpness you can build, drive you can barely coach, influence is non-negotiable.
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 4
- Confidence
- 92%
Rathi's contrarian claim is that most product managers shouldn't be product managers — they entered from other fields without realising what it takes, and it makes them miserable. His three-part filter is raw sharpness (problem identification and problem solving), drive/grit (curiosity, learnability, never giving up), and influence. Critically, he ranks them by coachability: 80% of the sharpness you need is achievable through domain knowledge, drive is the hardest to coach, and influence has 'no negotiation' — you must decide to get good at it. The test isn't whether you're already good; it's whether the prospect of becoming influential excites you rather than scares you.
Origin
Rathi's own 'simple framework of three'. It sits underneath his broader full-stack PM thesis — that PMs must own outcomes, not features — which he backs with David Epstein's book 'Range' and its opening examples of Roger Federer (who played many racket sports until 18) and, by Lenny's addition, Wayne Gretzky.
Core principles
- 01PMs are in the business of influence — internally with engineers and leadership, externally with users.
- 02Raw sharpness = problem identification + problem solving; roughly 80% of it is achievable, not innate.
- 03Domain knowledge substitutes for raw brilliance: an average-smart person with deep domain knowledge outdecides a brilliant one without it.
- 04Drive/grit is the hardest to coach — people low on it rarely acquire it, though they can be inspired.
- 05Influence is non-negotiable: you don't get to be a successful PM by routing around it.
- 06Range beats specialisation: connecting ideas across domains is the better playbook in product.
- 07Full-stack means owning the outcome — users, competition, other PMs, engineering, marketing — not just your feature.
How to run it
- 1
Audit yourself against the three
Score yourself honestly on raw sharpness (can you identify and solve the right problem?), drive/grit (curiosity, learnability, refusal to give up, consumer-back thinking), and influence.
Pro tip The bar isn't 'already excellent' — it's 'excited about getting better at these'.
Watch out If the idea of having to influence people to succeed scares you away rather than exciting you, product management will likely make you miserable.
- 2
Close the sharpness gap with domain knowledge
Don't try to become smarter in the abstract. Load up on domain knowledge — it lets an averagely-smart person make materially better decisions than a brilliant novice.
Pro tip Focus specifically on decision-making, problem identification and problem solving — those are the trainable parts.
- 3
Treat influence as a discipline, not a personality trait
Accept that you are influencing all day: users to change behaviour, engineers to build faster, leadership to sign off. Deliberately build the skill — think more like sales, marketing and influencers.
Pro tip Extend it externally too: you are a 'full-stack influencer', not just an internal one.
Watch out Believing you can get away without influence and still be a very successful PM is, in Rathi's view, almost always wrong.
- 4
Build range deliberately
Deepen adjacent competences — marketing, engineering, competitive analysis, other product lines — and run your ideas past those people to get them 'waded' before deciding. You don't need to be an authority in each; you need partnerships and range.
Pro tip The 'Range' argument: Federer played multiple racket sports until 18 and imported ideas across them; multi-sport childhoods produce better single-sport athletes.
Watch out Being excellent in one narrow area only is, per Rathi, the weaker career playbook in product.
In the wild
Rathi's definition of success is not 'we launched something users like'. It's: did it change the behaviour of the kind of user we targeted, did it achieve a business outcome, did it build a capability that matters? None of that happens if the PM only thinks about their own slice.
→ PMs are held to outcomes, not features — which forces them to work across marketing, engineering, competition and other product lines.
From the book 'Range': Federer played a bunch of racket sports until he was 18, importing ideas from one to another. Lenny adds Gretzky, who played hockey only in winter and other sports in summer.
→ Rathi's conclusion: cross-domain range is 'a better playbook for being more successful in product' than early narrow specialisation.
Common mistakes
Entering product without knowing what it takes
Rathi's contrarian view is that most PMs should not be PMs — many arrived from other fields without realising the job's demands. You can coach your way up, but if it isn't right for you it will make you quite miserable.
Trying to route around influence
People assume they can compensate with smarts or execution. Rathi: on influence 'there's no negotiation there' — the prospect of needing it should excite you, not repel you.
Is it for you?
Best for
PMs deciding whether product management is the right field for them, and PM hiring managers defining a bar
Not ideal for
Highly specialised technical IC roles where deep single-domain mastery is genuinely the job
From the transcript
“the first thing is is essentially raw Sharps and that can manifest itself into problem identification and problem solving”
“the second one is what I call drive or grit because I think with that comes a whole bunch of qualities around curiosity learnability never…”
“we are in the business of influence”
“in my opinion the full stack product managers are the ones who are going to be more successful rather than U product managers who are…”
“most product managers should not even be product managers”
From the episode
The full-stack PM
Anuj Rathi (Swiggy, Jupiter Money, Flipkart)