Shreyas Doshi's three-way split of how product organizations distribute power to the PM function, anchored to one diagnostic heuristic: does influence track competence?
Related to Three Conditions for Empowerment and Hollow Empowerment Declaration (Abdication Mistaken for Empowerment) — PM Guided is essentially a culture-level empowerment condition, where the org's default posture grants influence in proportion to demonstrated skill rather than as a blanket declaration or a title-based entitlement. Contrast with Product Leadership Archetypes: Operator, Craftsperson, Visionary, which classifies individual leaders rather than the org's power-distribution culture. See also Learnable vs. Teachable (Skill-Acquisition Distinction) for why engineer/designer engagement in a PM Guided culture can't simply be mandated.
PM Serviced culture is one where the product management function isn't deemed important enough to lead new product work, idea generation, or strategy — PMs are relegated to glorified project/program management while another function (usually sales or engineering) holds more power.
As an individual PM inside such a culture, you likely can't change the whole org, but you can change your own team's culture by demonstrating a very high degree of competence and building credibility from scratch (see Asking for Agency Already Forfeits It). This escape is framed as an individual, bottom-up act — building personal credibility on your own team — rather than a top-down or systemic fix, even for a senior hire.
A viewer comment on the source video, describing being "at the mercy of engineers" in a PM-Serviced team and asking whether quitting is the only answer, drew a reply saying yes from experience — reflecting the same logic: if you can't shift the people immediately around you, the honest next step may be to leave rather than wait for the culture to change.
PM Dominated culture is one where holding the PM title alone grants decision-making power regardless of competence — "meaning even an incompetent PM gets to call the shots." Shreyas Doshi flags this as a red flag when evaluating a company to join: these cultures are "not fun to work at" and are described as generally failing to produce winning products, even for PMs who might otherwise want the guaranteed power.
PM Dominated is framed as a decay pattern rather than a static trait: some were once winning-product startups that deteriorated their culture as they scaled, meaning unchecked PM power outlived the conditions that made it work in the first place.
PM Guided is the recommended culture, diagnosed by a single heuristic: does influence track competence? "An incompetent PM does not have very much influence, but a competent PM has a very high degree of influence." It is the only one of the three where influence and skill are causally linked, rather than structurally capped (Serviced) or structurally guaranteed (Dominated).
PM Guided cultures tend to coincide with visibly engaged engineers and designers — and that engagement "cannot be taught" and "cannot [be] force[d] on anyone," only observed, so it should be treated as an evaluation signal rather than something to instill via process or mandate (see Learnable vs. Teachable (Skill-Acquisition Distinction)). Doshi's overall recommendation: "seek PM Guided cultures, not PM Dominated."