02:56
product management
Shreyas Doshi defines the real job of a product manager as three-part: to define the product, to orchestrate actions across the org, and to do both in service of making the product genuinely successful — not merely to solve customer problems or make customers happy, and he argues this last distinction is a foundational difference in how the job gets done, not a semantic one.
Doshi's definition: "it is to define the product and orchestrate actions across the org to enable its success" — three parts he says are extremely important.
Defining the product is the most important part: a PM must be the primary person responsible for deciding what product the team will build.
The role is defined functionally, not by title: regardless of title, someone who isn't primarily responsible for defining the product isn't doing the real PM role, and conversely someone without the PM title who is primarily defining the product is performing the PM role.
Orchestrating actions is where most PMs spend the majority of their time and is "absolutely essential," but doing this alone, without defining the product, means you're performing a project manager role, not the real PM role.
Common definitions of the PM role — impact, customer happiness, problem solving, customer obsession — are useful but "not direct enough."
The actual point of the job is to make the product successful, to make it win — not just to solve customer problems — and Doshi insists this is "a foundational difference," not "a semantics point."
It took Doshi almost 10 years as a PM to learn this distinction; he says he's lucky to have learned it at all, since some PMs never do.
Doshi's definition of product success: "some combination of user adoption, user satisfaction, and unique business impact."
The single takeaway he emphasizes: the main thing in the PM job is to define the product.
Doshi explicitly decouples time spent from role definition: orchestration consumes most of a PM's hours yet he ranks it below defining the product in importance, implying that being busy orchestrating is not evidence of doing the job's core work.
Customer-centric language (happiness, satisfaction, problem-solving, obsession) isn't rejected as wrong but reframed as an insufficiently direct proxy — customer satisfaction reappears in his own success definition, but as one component alongside adoption and business impact rather than as the goal itself.
He frames the choice between "make the product win" and "make customers happy" as behavior-altering, not just rhetorical — claiming a PM holding one goal internally will act differently day to day than one holding the other, though he doesn't spell out the specific behavioral differences in this clip.
The functional definition of the role makes org-chart title explicitly irrelevant as evidence of whether someone is doing real PM work; the test he offers is narrow and binary — are you the primary person deciding what gets built.
He frames this not as standard PM curriculum but as a hard-won personal realization that took him roughly a decade, and notes some PMs never reach it — positioning the definition as a rare, earned insight rather than common industry knowledge.
«here's my definition of the role of a product manager it is to define the product and orchestrate actions across the org to enable its success»
— 00:02
«you must be the primary person responsible for defining what product you're going to build»
— 00:21
«the second key part is to orchestrate actions this is the part that most PMS spend a majority of their time on and this is absolutely essential»
— 00:46
«you're not performing the real role of a real PM maybe you are performing a project manager role»
— 01:06
«why are we spending Millions tens of millions hundreds of millions of our company's money on this product we're not doing that just to solve customer problems we're doing that to make our product successful make our product win»
— 01:30
«it's not a semantics Point okay it is a foundational difference»
— 01:44
«it took me almost 10 years of being a PM to learn that if you do your job thinking that your main job is to make your product successful to make it win you will do it very differently than if you do your job thinking that your job is to make customers happy»
— 01:47
«in my book the definition is some combination of user adoption user satisfaction and unique business impact»
— 02:31
«the key thing I want you to remember from this is that the main thing in the PM job is to define the product»
— 02:37
Reception
Viewers found the video insightful and praised its clear definition of product management, though several asked thoughtful follow-up questions seeking more depth and clarity on specific concepts.
A short, single-framework talk built around one central reframing — product success over customer-satisfaction language — presented as Doshi's own decade-earned conclusion rather than a citation of external theory.
02:56