03:46
product leadership
Shreyas Doshi defines PM leadership specifically as making successful products via others and building self-managing teams, while distinguishing it from the broader role of "product leader" (which anyone owning a product's outcomes can hold, regardless of title), and argues the core job in either case is to create clarity through strategy/vision ownership, product editing, meta execution, and PM coaching.
PM leadership is defined narrowly: "make successful products via others and build self-managing teams."
A "product leader" and a "PM leader" are different vocabulary terms that can overlap but don't have to: a product leader doesn't have to be a PM or manage PMs exclusively, and could be an engineer, designer, or someone on the business side leading a mixed team of PMs, engineers, and designers.
The main job of a leader responsible for a product is to create clarity — at both the macro and micro level — on what to build, how to build it, and how to expand it.
Clarity is created by leading strategy and vision, though the leader need not be the sole formulator; they must still feel ownership over it.
In smaller, earlier-stage companies, the ultimate product leader is sometimes the CEO, not the CPO.
Product editing is essential: the leader isn't necessarily writing product proposals themselves but must be a great editor of what the team produces.
Meta execution is another key task: the leader isn't responsible for day-to-day sub-team execution, but is responsible for the team structure that enables efficiency and effectiveness.
PM coaching is called out as its own distinct, key aspect of the job.
Consistently successful product leaders tend to spike on: critical thinking (including analytical and strategic thinking), product sense, influence (particularly via listening), and cognitive empathy.
These skills matter for being consistently successful across companies, product types, domains, and product stages.
PM Leadership (role definition) — Doshi's specific definition of the PM leadership role as making successful products via others and building self-managing teams. Apply: Use this as the narrow test for whether a role is "PM leadership": does the person achieve product success primarily through others and by building teams that can self-manage?
Product Leader vs. PM Leader (vocabulary distinction) — A distinction where "product leader" is anyone responsible for a product regardless of functional background (engineer, designer, business side), while "PM leader" specifically implies leading/managing PMs; the two can overlap or differ. Apply: When labeling a role, ask whether the person primarily manages PMs (PM leader) or simply owns product outcomes across a mixed team (product leader) rather than assuming the terms are interchangeable.
Create Clarity (macro and micro) — The main job of a product-responsible leader, defined as creating clarity at both the macro and micro level on what to build, how to build it, and how to expand it. Apply: As a product leader, continually check whether your team has clarity at both the big-picture and detailed level on the what/how/expansion questions, and treat resolving ambiguity there as your primary output.
Leading Strategy and Vision — The mechanism through which a product leader creates clarity — leading strategy and vision even if not its sole formulator, but ultimately owning it. Apply: Even when delegating the drafting of strategy or vision to others, take personal ownership of the result so it's something you genuinely stand behind.
Product Editing — A key task where the leader isn't creating product proposals or directly executing them, but must be a great editor of whatever the team produces. Apply: Focus your time on reviewing and sharpening the team's product proposals and output rather than authoring them yourself.
Meta Execution — Responsibility for the structure that lets a team execute efficiently and effectively, as opposed to responsibility for day-to-day sub-team execution itself. Apply: Design and own your team's operating structure, and delegate the daily execution management within that structure to someone else on the team.
PM Coaching — A distinct, named key aspect of the product leadership job, separate from clarity-creation, editing, or meta execution. Apply: Set aside explicit time and effort to coach the PMs you lead as its own responsibility, not as a byproduct of other tasks.
Critical Thinking (analytical + strategic thinking) — A skill Doshi says consistently successful product leaders spike on, encompassing both analytical thinking and strategic thinking. Apply: Develop analytical and strategic thinking as a combined core competency rather than treating them as separate skills to build.
Product Sense — One of the named skills consistently successful product leaders spike on. Apply: Treat product sense as a distinct skill to cultivate alongside critical thinking and interpersonal skills.
Influence via Listening — A skill defined specifically through how well the leader listens, rather than through persuasive communication broadly. Apply: Build influence by improving your listening ability rather than focusing primarily on how you communicate or persuade.
Cognitive Empathy — A named skill essential for consistently successful product leaders across companies, product types, domains, and stages. Apply: Practice cognitive empathy — understanding others' perspectives and reasoning — as a distinct, essential leadership skill.
Doshi explicitly decouples "product leader" from the PM function or title — the role can be filled by an engineer, designer, or someone on the business side, not just a manager of PMs.
He flags an organizational reality that cuts against title-based thinking: in smaller/earlier-stage startups, the CEO — not a formally titled CPO — is often the actual ultimate product leader.
Two of his named responsibilities (product editing, meta execution) both frame the leader's leverage as coming from shaping what others produce or how the team is structured, rather than from personally authoring proposals or running day-to-day execution.
He defines "influence" narrowly through the lens of listening ("influence and particularly listening, how well they listen") rather than through persuasion or communication more broadly.
«I define the role as make successful products via others and build self-managing teams.»
— 00:09
«a product leader can be somebody who's kind of responsible for a product but doesn't have to be a PM themselves or doesn't have to be exclusively managing PMs.»
— 00:28
«their main job is to create clarity and it's to create clarity at the macro level and the micro level»
— 01:09
«sometimes by the way that ends up being if it's a smaller company it's actually the CEO not the CPO the ultimate product leader sometimes is the CEO»
— 01:51
«you need to be a great editor right you need to be a great editor of whatever it is that the team is building»
— 02:19
«consistently successful product leaders tend to spike on critical thinking which also includes is analytical thinking, strategic thinking, product sense, influence and particularly listening, how well they listen and cognitive empathy.»
— 03:10
Reception
Viewers praised the video's clarity and efficiency, finding it concise and information-dense.
In under four minutes, Doshi delivers a terminology-dense personal framework for product leadership — separating role from title, and job tasks (clarity, strategy/vision, editing, meta execution, coaching) from skills (critical thinking, product sense, influence, cognitive empathy) — matching audience comments that single out its high "nuggets per second" clarity.
03:46