Sep 5, 2023 · 1h 18m · knowledge-project
Shreyas Doshi: Better Teams, Better Products
0:00 / 0:00
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this episode of The Knowledge Project, product leader Shreyas Doshi shares essential mental models for building great products and high-performing teams, exploring agency, organizational alignment, qualitative evaluation, and the power of written culture.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Shane holds 11.6% of the talking time here. How this is scored →
Shane as informed peer 4.6 Guest teaching 6.1 Guest disagreement 1.3 Shane pushing back 1.6
speaking balance: gold is Shane, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 1:04:30 Calling out corporate ROI machines
Shreyas critiques common corporate prioritization behavior, arguing teams manipulate the ROI ratio by pursuing trivial quick wins rather than impactful work.
Hardest push from Shane ▶ 14:11 Challenging evaluation without metrics in corporate environmentsShane rejects a purely intuitive framing by pressing on the practical reality of scarce resources and demanding how leaders get buy-in without measurable numbers.
Biggest teaching moment ▶ 1:03:50 Deconstructing the ROI denominator trapShreyas provides a mathematical and strategic deconstruction of ROI prioritization traps, educating listeners on why opportunity cost minimization is superior.
Shane holds their own ▶ 35:33 Shane's McDonald's problem analogyShane demonstrates deep operational experience by articulating his 'McDonald\'s problem' principle, establishing that professionals are paid for judgment rather than rule-following.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Shane as informed peer | Guest teaching | Guest disagreement | Shane pushing back | Why |
|---|---|---|---|---|---|---|
| Understanding the Three Levels of Product Work | 3 | 6 | 1 | 1 | Shane opens by prompting Shreyas to outline the three levels of product work. Shreyas provides an extended masterclass on execution, impact, and optics, explaining why misalignments between PMs and executives occur. | |
| Resolving Cross-Functional Conflict and Aligning Perspectives | 4 | 6 | 1 | 1 | Shane asks a probing question about why cross-functional teams litigate details when seeing problems through different lenses. Shreyas explains the need to step back and uncover underlying optics or execution concerns. | |
| Evaluating Progress Versus Measuring Progress | 4 | 7 | 2 | 1 | Shane references Shreyas' online writing on evaluating versus measuring. Shreyas challenges conventional corporate dogma ('if you cannot measure it, you cannot improve it') using parenting analogies and product realities. | |
| Demonstrating Impact and Utilizing Leading Indicators | 6 | 7 | 2 | 5 | Shane pushes back firmly, asking how managers can get resource buy-in in data-driven cultures without hard metrics. Shreyas addresses this by showing how to reframe goals using leading indicators and qualitative proof points. | |
| Balancing Quantitative Metrics and Qualitative Intuition at Scale | 5 | 5 | 1 | 2 | Shane proposes a hypothesis comparing how professional managers versus founders balance quantitative and qualitative signals. Shreyas agrees broadly but adds nuance regarding how scale degrades initial founder instincts. | |
| Inside Stripe's Product Culture and Shared Ownership | 4 | 6 | 1 | 1 | Shane asks Shreyas what core practices he took away from his five years at Stripe. Shreyas explains Stripe's egalitarian product ownership across functions and founders staying close to front-line customer issues. | |
| Asynchronous Writing Culture and Leadership Judgment | 6 | 5 | 1 | 3 | Shane asks how ties are broken when all functions are equal, noting that people dislike making subjective judgment decisions. Shreyas outlines the role of asynchronous doc writing and escalation hierarchies. | |
| Good Teams Versus Great Teams: Decision Philosophy and High Agency | 6 | 5 | 2 | 2 | Shreyas analyzes great teams through decision clarity, rule-bending, and agency. Shane contributes his own 'McDonald\'s problem' framework illustrating why employees are paid for judgment rather than robotic rule-following. | |
| The Agency Talent Matrix Framework | 4 | 7 | 1 | 1 | Shane asks Shreyas to detail his Agency Talent Matrix. Shreyas breaks down the four quadrants—cogs, frustrated geniuses, go-getters, and game changers—highlighting why he prefers hiring go-getters for ambiguous PM roles. | |
| Principles for Writing, Structuring, and Influencing | 6 | 6 | 1 | 2 | Shane shares his perspective on writing as thinking and audience empathy. Shreyas expands on permissionless communication and the pitfalls of burying insights in 20-page documents instead of leading with the core proposal. | |
| The Antithesis Principle in Career and Life Decisions | 5 | 7 | 2 | 1 | Shreyas introduces the Antithesis Principle, explaining that individuals should not require the conditions they observe the broad public needing. Shane summarizes the concept as building the capability to execute in non-ideal environments. | |
| Opportunity Cost Versus the Return on Investment Trap | 4 | 8 | 2 | 1 | Shreyas dissects how teams become ROI machines by artificially reducing the denominator (picking low-impact low-hanging fruit) and argues for evaluating decisions through opportunity cost and code immalleability. | |
| Systematically Growing Competence and Product Sense | 4 | 7 | 1 | 1 | Shane asks how to systematically build competence. Shreyas decomposes product sense into cognitive empathy, domain knowledge, and creativity, advising allocating 5-20% of career time to compounding outside learning. | |
| Defining Success: Time Optionality and Life Priorities | 3 | 4 | 0 | 0 | Shane asks his traditional closing question on defining success. Shreyas defines it as time optionality dedicated to the top three priorities on his personal stack rank. |
Statements from this episode (18)
Doshi: Team conflict stems from communicating at mismatched organizational levels
“Oftentimes conflict between people and teams arises mainly because we're not talking at the same level. And we might have you know, similar missions and similar goals and OKRs and whatnot. But if we are not aligned on the level at which we are talking, that ca…”
Doshi: Product managers lose executive audiences by leading with execution details
“If you come into this kind of product review as the product manager and you kind of drown the group in all sorts of execution level detail, which you think are the right things to share, because these are challenges you're facing right now. If you lead with th…”
Doshi: Dismissing Teams as Optics-Focused Destroys Cross-Functional Collaboration
“It was easy for me to judge Other individuals or other teams saying like, oh, these people are only focused on optics, whereas I am focused on impact and execution, which are the right things to be focused on. And when you start with that sort of feeling, it d…”
Doshi: Demanding metrics before taking action causes hidden organizational damage
“Used in the wrong context, they tend to you know, cause a lot of damage that we don't even realize, because we feel like we're being smart when we say, oh, this thing must be measured before we can improve it.”
Doshi: Qualitative evaluation is often enough when measurement costs are too high
“In some cases, the effort To measure something is so large that it sometimes dissuades us from performing the action that makes sense. The fundamental sort of observation here is that sometimes evaluating how something is going is enough.”
Doshi: Stripe B2B features used qualitative feedback to track long-term impact
“And I did this a lot at Stripe, for instance, when we were working on B to B products, that, you know, in some cases, they took a year or year plus to show direct revenue impact or volume impact, is I would call out some very big customers that we were able to…”
Doshi: Stripe co-founders regularly conducted user research with frontline staff
“Patrick and John, until a very, very long time, as the company was scaling, and to a point where you wouldn't expect the founder to do so they were talking to customers. They were talking to users, and not only that, in many cases, they would kind of, you know…”
Doshi: Playbooks become standard over time, outperformance always requires judgment
“If everybody could just follow playbooks then you know, and they might be wonderful playbooks, but over time, even wonderful playbooks become the industry standard. So now if you want to outperform, you need something else, and that something else is always ju…”
Doshi: Great teams need only a few high-agency people to drive impact
“You don't need the entire team to be extremely high agency, but the ability of at least a few individuals on the team to have and embody this high agency approach such that, oh, actually, yes, we do have this obstacle, but here's how we're going to creatively …”
Doshi: Hire High-Agency 'Go-Getters' Over 'Frustrated Geniuses' in Ambiguous Roles
“Given a choice between hiring a frustrated genius and hiring a go-getter if it is a role that has a high degree of ambiguity, I would rather hire the go-getter than the frustrated genius, because I know the go-getter will work hard to resolve the ambiguity ver…”
Doshi: Written culture enables permissionless organizational communication
“When you have a writing culture, it becomes more of a permissionless environment. You know, say non-writing culture where perhaps the way big decisions are made or proposals are shared, it's usually in some meeting where perhaps you know, we have a discussion …”
Doshi: Document-driven cultures handicap poor writers from exerting influence
“One of the challenges is that such a culture makes it hard for people who kind of Think they're not a good writer to be able to influence, right? Because ultimately, you know, any form of communication in an organizational setting is a form of influence”
Doshi: Overloading business docs to build 'bulletproof' cases loses readers
“The reason that some folks do this when they are writing is because they want to communicate everything they know about this topic. And of course, when we do that, the story we tell ourselves is, oh, I want to build a bulletproof case, right? So I'm going to p…”
Doshi: High Performers Should Train Themselves to Learn Without Entertainment
“What you should do, if you want to optimize and maximize outcomes, and your impact on the world, is you should turn yourself into the kind of person that doesn't need any sort of entertainment, right? To learn something, right?”
Doshi: High Performers Must Excel Even Under Mediocre or Absentee Managers
“When it comes to yourself, you should turn yourself into a person who can do really good work, even without having a great manager. Even if you have an okay or absentee manager, you should turn yourself into a person who can do really great work.”
Doshi: Optimizing for ROI Causes Product Teams to Build Safe Me-Too Products
“What that leads to is a lot of me too products. It leads to us kind of just meeting table stakes. It leads to kind of picking the safe things. Because the safe things are you know, easy to quantify and they're safe because they're easy to quantify. And look, I…”
Doshi: Software Code Is Too Inflexible to Rely on Easy Backtracking
“Our code is not as malleable that as we think. Right? We just think, oh, we're going to write this code, ship it, and then, ah, if it doesn't work, we're going to undo it. We're going to change it. We're going to learn, et cetera, and all of that is good. But …”
Doshi: Product sense decomposes into cognitive empathy, domain knowledge, and creativity
“Product sense has three components. The first is cognitive empathy. Which is, do I understand how you think as a user, how customers think, how they approach situations, what will resonate for them or not, right? That is cognitive empathy. Second is domain kno…”