第一性原理与产品心理学
建立每个 PM 决策背后的运营心智、心智模型与具备偏差意识的判断力。
Explainer
产品管理始于一种看待事物的方式。在框架、路线图与指标之前,PM 的工作是把模糊性翻译为可以累积的决策。这意味着同时把用户的现实、业务的经济性与系统的约束放在脑中,并选择接下来该学什么 —— 不回避你已知与你假设之间的差距。
PM 是翻译者,而非小 CEO
把 PM 视为「小 CEO」是一种误导。PM 通常没有团队的雇用/解雇权,也无法单方面决定工程产能。更有用的视角是翻译者:在用户真相与业务结果之间,在战略与工单之间,在今日的可能与下一注成功后将成为可能之间。影响力来自翻译的质量,而不是头衔。
- 把用户痛点翻译为最小的、可学习的问题陈述。
- 把业务目标翻译为团队可以瞄准的可观察的行为变化。
- 把技术约束翻译为团队可以辩论的产品取舍。
用户 vs 客户 vs 购买者 vs 拥护者
大多数 PM 错误从把四种不同的利益相关者塞进一个词开始。用户体验产品;客户付钱;购买者签字;拥护者在内部为产品发声。在 B2C 与 prosumer 中,他们常常重叠为一个人。在 B2B、医疗、政府和市场类产品中,他们是有不同激励、行动意愿差异巨大的不同利益相关者。
- 用户:从日常使用中获得价值或摩擦;承担切换成本。
- 客户:支付账单;关心 ROI、治理与安全。
- 购买者:签合同或批准上线;关心风险与政治。
- 拥护者:在组织内部推动 adoption;关心信誉与可见的胜利。
- 在绘制功能图之前,先按工作流绘制他们。
产品三角:可行性、可用性、可实现性
每一个产品决策都坐落在一个三角内:业务可行性(这能赚钱或省钱吗?)、用户价值与可用性(它真的比替代方案更好地解决了真实问题吗?)、技术可实现性(我们能否用我们的团队和栈来构建、运维和演进它?)。强 PM 在三个透镜之间自如切换;弱 PM 默认让其中之一支配 —— 通常是他们最熟悉的那个。
- 可行性:营收、成本、留存经济、监管与合同暴露。
- 价值与可用性:已被证明的需求、切换意愿、可学习性、可访问性。
- 可实现性:延迟、可靠性、安全、可观测性、维护、团队产能。
- 当利益相关者意见不合时,说出每个人在捍卫哪个角 —— 大多数分歧是角的冲突,不是事实之争。
结果 vs 输出 vs 活动
Marty Cagan 的区分是产品中最有用的之一。输出是你交付的东西;活动是你做的事情;结果是你引发的用户行为或业务表现的变化。大多数团队衡量活动(「这周我们做了 discovery 访谈」),一些团队衡量输出(「我们发布了 8 个功能」),只有最好的团队衡量结果(「新群组中每周活跃编辑者从 41% 升至 49%」)。以输出驱动的路线图看似高效,却很少推动业务。
- 活动最容易伪造,也最常出现在状态报告中。
- 输出感觉像进步,但只有当用户行为改变时才有意义。
- 结果迫使团队承认工作没有移动指标。
- 通过提问重述任何输出陈述:「因此哪种用户行为应当改变,我们如何知道?」
一类 vs 二类决策
Jeff Bezos 的区分:一类决策是单向门 —— 难以或无法逆转(架构选择、公开定价变化、并购)。二类决策是双向门 —— 容易逆转(大多数功能发布、文案修改、单一群组的定价实验)。把二类当一类对待是速度最常见的拖累。把一类当二类对待是灾难最常见的来源。
- 对二类决策默认行动;快上线、快学习,错了就回退。
- 在一类决策上慢下来;请进最强的声音,做 pre-mortem。
- 不确定时直接问:「如果错了,我们如何在 7 天内把它撤回?」
第一性原理思考
类比推理快但有损(「我们就照 Stripe 那样做」)。第一性原理推理慢但更耐用:把问题拆解到无可争辩的事实,再向上构建。PM 用它来挑战继承的假设(「我们一直按席位收费」),在没有基准时从零估算,以及发现并不适合团队真实约束的复制粘贴策略。
PM 应内化的心智模型
心智模型是可重复使用的思维捷径,把经验压缩起来。重点不是死记硬背,而是让六七个时刻挂在嘴边,以便在对话中即时挑选合适的那个。
- 反向思考:不要问「我们如何成功?」,而问「我们如何保证失败?」并避免那些路径。
- Pre-mortem:假设发布失败了,在上线前写出 post-mortem。
- 二阶思考:「然后呢?」绘制后果的后果。
- Steel-manning:在反对之前,先把对方观点说得比对方还强。
- 可证伪性:永远无法被证伪的信念不是有用的信念。
- 汉隆剃刀:能用缺乏上下文充分解释的事,就不要归因于恶意。
- 切斯特顿栅栏:在你弄清它为何被设立之前,不要拆掉它。
PM 的原型(以及为何它们重要)
PM 是科技领域中最广泛的角色之一。Growth PM 的日常与 Platform PM 截然不同。知道你的角色最接近哪个原型,能帮你选出值得投资的指标、伙伴与技能。
- 产品负责 PM:面向终端用户的界面;与设计强协作;关注激活与留存指标。
- Growth PM:实验密集;聚焦漏斗;与市场和数据合作;AARRR 指标。
- Platform / Infra PM:面向内部或开发者;关注易用性、可靠性、采用率;与工程协作能力路线图。
- Technical PM:面对深度技术(API、SDK、数据产品、ML 系统);常以接近协议的方式书写规格。
- Data / ML PM:ground truth、评估、模型行为、数据集权属;与研究协作。
- Internal Tools PM:员工是用户;ROI 是节省的小时数与避免的错误;政治是最难的部分。
决策框架:DACI、RAPID、RACI
产品中的速度,主要是关于谁决定什么的清晰度。DACI(Driver、Approver、Contributors、Informed)与 RAPID(Recommend、Agree、Perform、Input、Decide)对产品决策最有用。RACI 在运营上线中更常见。选一个并坚持使用 —— 形式不及命名一个唯一 Approver / Decide 的纪律重要。
- Driver / Recommend:撰写提案;通常是 PM。
- Approver / Decide:做决定;只有一个人,明确指名。
- Contributors / Input:提供专业意见;他们的工作是被听到,而不是否决。
- Informed:保持知情;不需要表态。
利益相关者地图
利益相关者地图是最被低估的 PM 工件。把利益相关者放进权力 × 兴趣的 2x2 矩阵。高权力 / 高兴趣的人,需要成为计划的共同作者。高权力 / 低兴趣的人,需要被告知,但不必每个细节都征询。低权力 / 高兴趣的人,通常是你的传道者。低权力 / 低兴趣的人,是噪音。
- 在每个季度开始时刷新地图。
- 说出每位利益相关者的个人利害 —— 职业风险、团队负担、品牌影响。
- 规划深思熟虑的接触点,而不是偶遇式的走廊更新。
PM 的操作系统
出色的 PM 以周节奏运转 —— 而非靠英雄主义。一种简单节奏:周一回顾结果(指标相对计划如何?);周中做发现与异步书面工作;周三或周四开跨职能工作会议;周五写一份周报。用一页纸的周报替代状态会议;用分诊队列替代临时请求。
- 默认采用异步书面沟通;把同步留给决策与分歧。
- 维护公开的「now / next / later」,让利益相关者自助获取答案。
- 保留一份私人「未知」清单:每个你尚未验证的假设。
- 为深度工作排专门时段;日历俄罗斯方块是状态游戏,而非生产力策略。
Framework atlas
Reference cards for each method in this mission
Expand a card for when to deploy it, misuse patterns, sequencing guidance, and (where relevant) shorthand formulas.
Decision-making · Atlassian / IntuitDACI(DACI)
A four-role decision framework that names exactly one Driver, exactly one Approver, a small set of Contributors, and a list of Informed parties for every meaningful decision.
When to use
- Cross-functional decisions involving 3+ teams.
- Decisions where you've felt 'no one is in charge' before.
- Recurring quarterly planning or roadmap calls.
When not to
- Truly trivial Type-2 decisions inside a single team.
- When the team is small enough that ad-hoc decisions are cheaper than the framework overhead.
How to apply
- Name the decision in one sentence with a deadline.
- Assign a single Driver who is responsible for moving the decision to a yes/no.
- Assign a single Approver — the person who will make the final call.
- List Contributors and explicitly note their expertise window.
- List Informed parties and how they will be told.
- Letting Approver be a list of people: that is a committee, not an approver.
- Treating Contributors as veto-holders.
- Skipping the Informed list — usually the source of last-minute drama.
Decision-making · Bain & CompanyRAPID(RAPID)
Recommend, Agree, Perform, Input, Decide. Heavier than DACI but useful when decisions cross legal/regulatory boundaries or have material financial consequences.
When to use
- Decisions with regulatory or contractual exposure.
- Decisions where 'Agree' (a soft veto, often legal/security) is meaningfully different from 'Input'.
When not to
- Day-to-day product trade-offs.
- Where DACI's simpler structure is enough.
How to apply
- Recommend: who frames the proposal.
- Agree: who must sign off (legal, security, finance).
- Perform: who executes the decision once made.
- Input: who provides expertise.
- Decide: who makes the final call.
- Confusing Agree with Decide; Agree is a veto on a specific dimension, not the call.
- Routing too many decisions through RAPID — the overhead defeats the purpose.
Risk surfacing · Gary KleinPre-Mortem
Imagine the launch failed, then write the post-mortem in advance. Surfaces the risks people are too polite or too anchored to raise during normal planning.
When to use
- Any Type-1 decision.
- Launches with reputational, regulatory, or financial exposure.
- When the team is unusually optimistic — 'this can't fail' is the alarm.
When not to
- Reversible micro-experiments where the cost of failure is one cohort and one week.
How to apply
- Set the scene: 'It's six months from now and the project has clearly failed.'
- Each person writes silently for 5 minutes: why did it fail?
- Cluster the failure modes; rank by likelihood and impact.
- Add the top 3-5 to your discovery and execution plans as risks to retire.
Personal prioritization · Dwight D. EisenhowerEisenhower Matrix
A 2x2 of urgent vs important. Urgent + important: do now. Important but not urgent: schedule. Urgent but not important: delegate. Neither: drop. Useful for personal triage as much as feature triage.
When to use
- Triage of an overflowing inbox or backlog.
- Differentiating reactive support work from strategic work in your week.
When not to
- Real product roadmap prioritization — use RICE/ICE/Kano instead, since 'important' is too vague at scale.
How to apply
- List every open ask or commitment.
- Tag each as urgent or not urgent, important or not important.
- Triage: do, schedule, delegate, drop.
- Treating 'urgent because someone asked loudly' as 'urgent because deadline'.
- Letting the 'schedule' bucket become a procrastination graveyard.
Team alignment · Andy Grove / Jeff BezosDisagree and Commit
Once a decision is made, even those who disagreed must commit fully. Surfaces dissent before the decision; produces unity after. The opposite of 'malicious compliance'.
When to use
- After a Type-2 decision where you've heard the dissent and made the call.
- When the team has a culture of relitigating decisions in side channels.
When not to
- When the dissent is about safety, ethics, or regulatory compliance — those should not be silenced.
How to apply
- Make the decision-making process clear up front (DACI).
- Explicitly invite dissent before the call.
- Once made, ask: 'Can you commit?' — accept yes or 'I disagree but will commit'.
- Set a review date so the disagreement has a future audience.
Mental model · G.K. ChestertonChesterton's Fence
Don't remove a constraint, process, or feature until you understand why it was put there. Many 'obviously dumb' systems are scar tissue from past failures.
When to use
- Inheriting a codebase, product, or process that 'should obviously be simplified'.
- Stakeholder pushback that seems irrational — find the original incident.
When not to
- When the original reason is documented and clearly no longer applies.
How to apply
- Identify the fence (rule, feature, ceremony).
- Talk to the longest-tenured person who remembers it.
- Search post-mortems and incident reports.
- If the original reason is gone, remove with a clear migration plan.
Product Psychology
Cognitive biases that distort product decisions
Confirmation Bias
The tendency to seek, interpret, and remember information that supports existing beliefs while discounting contradictory evidence.
Product Risk
Teams cherry-pick supportive interview quotes and ignore data that would invalidate the favored solution.
Research Countermove
Before discovery, write down what evidence would falsify the hypothesis. Track wins and losses for the hypothesis with equal rigor.
Survivorship Bias
Overweighting visible successes while ignoring the users, products, or companies that failed and dropped out of the dataset.
Product Risk
A team copies practices from breakout products without seeing the dozens of failed products that used the same tactics.
Research Countermove
Study churned users, failed experiments, lost deals, and abandoned workflows with the same rigor as power users and case studies.
Anchoring
The first number, framing, or example heard exerts disproportionate influence on subsequent judgments.
Product Risk
A loud stakeholder's number becomes the implicit forecast, and every estimate gets adjusted relative to it instead of from facts.
Research Countermove
Have estimators write numbers privately before discussion; use base rates and historical reference classes; explicitly call out the anchor in the meeting.
Sunk Cost Fallacy
Continuing investment in a course of action because of resources already spent rather than expected future return.
Product Risk
Multi-quarter initiatives keep getting funded because killing them would 'waste' the prior work, even when the forward expected value is negative.
Research Countermove
Run a 'fresh-eyes' review every quarter: 'If we were starting today with what we know, would we fund this?' If no, redirect.
IKEA Effect
People disproportionately value things they have built themselves. Internal teams systematically over-rate their own products and processes.
Product Risk
PM and engineering favor in-house tools, dashboards, or features over better-fitting third-party options because they remember the cost of building.
Research Countermove
Use blind comparisons in evaluations. Have someone outside the team rate the artifact. Include the maintenance cost forecast, not just the build cost.
Curse of Knowledge
Once you understand something, it becomes hard to imagine not understanding it; experts systematically overestimate how clear their explanations are.
Product Risk
PMs assume users will 'get' a workflow because the team gets it; copy and onboarding read fluently to the team and incomprehensibly to first-time users.
Research Countermove
Run unmoderated tests with users who have never seen the product. Treat 'I don't know what to do here' as the most valuable data of the week.
Loss Aversion
Losses feel roughly twice as painful as equivalent gains feel pleasurable. Users will do irrational work to avoid losing something they have.
Product Risk
Teams under-weight removal cost when sunsetting features; users churn over a small removed capability they barely used.
Research Countermove
When removing or migrating, frame the change as a gain users earn (more reliable, faster, less buggy). Provide transition periods. Communicate before the change, not after.
Availability Heuristic
Recent or vivid examples dominate judgment regardless of whether they're representative.
Product Risk
One angry executive escalation reshapes the roadmap because it's emotionally fresh, even though hundreds of users had a different problem.
Research Countermove
Aggregate evidence in a recurring view (support themes, NPS verbatims, churn reasons). Force the question: 'How big is this problem in the dataset, not in my inbox?'
Planning Fallacy
Systematic underestimation of how long tasks will take and how much they will cost, even when the estimator has experienced the same kind of task underrunning before.
Product Risk
Sprint commits, quarterly OKRs, and launch plans regularly slip; trust in the team's word erodes over time.
Research Countermove
Use reference-class forecasting: how long did the last 3 similar projects actually take? Multiply optimistic estimates by the historical slip factor. Plan for the unknown unknowns explicitly.
Action Bias
A preference for action over inaction, even when the available actions have negative expected value.
Product Risk
Teams ship features to 'be seen doing something' after a metric drop, before the cause is understood; the feature itself becomes the new variable to debug.
Research Countermove
When metrics drop, isolate the cause before shipping a fix. Track which 'fixes' actually moved the metric vs which were activity for activity's sake.
Authority Bias
Disproportionate weight given to the opinions of authority figures regardless of the underlying evidence.
Product Risk
An executive's casual comment becomes a quarterly goal because nobody pushes back on it.
Research Countermove
Separate the message from the messenger. Restate the executive's idea as a hypothesis, then evaluate it on the evidence the same way as any other hypothesis.
Bandwagon Effect
Beliefs and practices spread because others are adopting them, regardless of whether they fit the local context.
Product Risk
Teams adopt frameworks (OKRs, Shape Up, ICE) because peer companies do, then blame the framework when context-mismatch causes failure.
Research Countermove
Before adopting any practice, articulate the specific problem it solves for *you*. If you can't, you're cargo-culting.
Status Quo Bias
Preference for the current state of affairs; alternatives are viewed as losses relative to the status quo.
Product Risk
Legacy product behaviors are protected even when data shows they hurt new users; 'we can't break existing users' becomes an unconditional veto.
Research Countermove
Quantify the cost of the status quo. Often the supposed risk of change is dwarfed by the ongoing cost of stagnation.
Dunning-Kruger Effect
Low ability in a domain often correlates with overconfidence; competent practitioners are paradoxically more aware of what they don't know.
Product Risk
Junior PMs ship confident roadmaps in domains they barely understand; senior PMs hedge so much they look indecisive.
Research Countermove
For confident-feeling claims, ask: 'What's the strongest argument against this?' If you can't make one, you don't understand the area yet.
Rhyme-as-Reason Effect
Catchy or rhyming statements feel more truthful than equivalently precise but less elegant statements.
Product Risk
Memorable research summaries get repeated as roadmap-driving truths even when the underlying evidence is weak.
Research Countermove
Translate any catchy phrase into a falsifiable assumption tied to observed behavior or data.
Organizational anti-patterns
When ceremonies look like rigor but aren't
The Feature Factory
Roadmap progress is measured in features shipped per quarter. Outcomes are reported only when convenient. Discovery is whatever week 1 of the sprint is.
Output is easy to count; outcomes take time and honesty. Activity becomes a proxy for impact in performance reviews.
Re-base every roadmap item on a target metric movement. Kill the feature count metric in reviews. Celebrate killed bad bets the same as shipped good ones.
Stakeholder Ventriloquism
PM justifies decisions with 'the CEO wants it' or 'sales said'; no first-hand user evidence is presented; team feels like a delivery service.
PM is conflict-avoidant or under-informed and uses authority laundering to push items.
Translate every stakeholder ask into a user problem and an evidence list before bringing it to engineering. If the evidence is weak, push back upstream.
Solutioneering
Specs jump straight to UI mocks. The first slide is a screen, not a problem. Discovery, if any, happens after design starts.
Solutions are concrete and exciting; problems are abstract and uncomfortable.
Write the problem statement, the user, the current alternative, and the success metric on page 1 of every spec, before any UI.
The Roadmap as Wishlist
The roadmap has 40 items, all H2 priorities, no sequencing rationale. Every quarter, the team commits to all of it and finishes a third.
PM uses the roadmap to placate stakeholders rather than to make a bet.
Cap the roadmap at 'now / next / later' with no more than 3-5 themes per quarter. Force trade-off conversations up front, not at the end.
Discovery Theater
Team runs 'discovery' that consists of a few user interviews after the spec is written. Findings are summarized to confirm the existing plan.
Discovery has been adopted as a ritual rather than a learning loop.
Define the riskiest assumption and the falsification criterion *before* the interviews. Reserve the right to change the spec or kill the project based on findings.
Outcome Theater
Every project is suddenly tied to a vague outcome ('improve user experience'); nobody can agree on which metric, baseline, or threshold counts as success.
Teams have heard 'be outcome-focused' but lack rigor in defining and measuring outcomes.
Force the trio: metric, baseline, target, by-when. If you can't write all four for an initiative, it's an output dressed up as an outcome.
Worked examples
Walkthroughs translated from real trade-off rooms
Reframing 'Make signup easier'
A B2B SaaS PM gets a request from sales: 'We're losing trial users at signup. Make signup easier.'
- Resist the solution: 'easier' is not falsifiable.
- Define the user behavior: 'reach first valuable action within 10 minutes of email click.'
- Pull the data: 38% of trials drop off between email confirm and team invite step.
- Run 5 unmoderated tests on the existing flow; observe friction points.
- Propose two scoped experiments: lazy team invite (Type-2, ship in a week) vs. SSO at signup (Type-1, scope it out properly).
TakeawayThe feature request 'make signup easier' became two falsifiable bets attached to a measurable behavior, with one fast Type-2 experiment to learn before the Type-1 commitment.
Saying no to an executive ask using the Product Triangle
CEO wants a chat widget added to the marketing site this quarter to 'engage prospects'.
- Acknowledge the goal: more qualified pipeline.
- Walk the triangle: Viability — what's the expected lift on qualified pipeline? Usability — does the prospect actually want a synchronous chat right now? Feasibility — staffing chat in three time zones during a launch quarter.
- Present two alternatives: a smaller asynchronous form with reply SLA, or a chat widget gated to qualified accounts only.
- Frame the decision with DACI: Driver: PM; Approver: CEO; Contributors: Sales, CS, Design, Eng.
TakeawaySaid no to the literal ask, said yes to the underlying goal, and gave the CEO a real decision instead of a polite refusal.
Catching a confirmation bias in a discovery sprint
Team is convinced the next big bet is collaborative editing. After 8 interviews, the deck of quotes is overwhelmingly supportive.
- Pause and write the falsifying criterion: 'If fewer than 30% of users describe a recent collaborative-editing pain spontaneously, the demand is weaker than we think.'
- Re-tag the interview corpus by spontaneity: how many quotes were unprompted vs. prompted?
- Find that most supportive quotes were prompted; only 18% were unprompted.
- Reframe the bet: collaborative editing is desired in concept but not yet a top-of-mind pain. Move it from Q1 to Q3 and back-fill with a real top-of-mind pain.
TakeawayConfirmation bias quietly inflated the perceived demand. A simple falsification check rebalanced the roadmap.
Resources / Case Studies
Curated reading for this mission
Ben Horowitz
A 1996 memo on the operating standards expected of strong product managers vs the failure modes of weak ones.
Anchors the product mindset around responsibility for outcomes rather than activity or process theater.
Marty Cagan (SVPG)
The canonical text on modern product management. Covers product discovery, the product trio, outcomes vs outputs, and the role of the empowered product team.
Defines the vocabulary the rest of the industry uses. Required reading.
Marty Cagan & Chris Jones (SVPG)
Companion volume to INSPIRED. Focuses on what product leaders must do to enable empowered product teams to find and solve real problems.
Closes the gap between PM craft and the organizational system that lets that craft compound.
Lenny Rachitsky
Concrete decomposition of a PM's week, with time allocations for discovery, delivery, alignment, and management.
Demystifies the job for new PMs and gives experienced PMs a benchmark for where they may be over- or under-investing.
Shreyas Doshi
How high-agency PMs operate: refusing the false constraints, finding leverage, and translating ambiguity into action.
The single most concentrated talk on the operating mindset that distinguishes great PMs from competent ones.
Julie Zhuo
Practical, candid guide to the early years of management — applicable to senior PMs whose work is increasingly through other people.
Bridges the IC PM and Lead PM transition without the usual MBA fluff.
Annie Duke
Decision-making under uncertainty, drawn from poker. Separates outcome quality from decision quality.
Teaches PMs to evaluate decisions on the inputs available at the time, not on hindsight, which is the foundation of honest postmortems.
Daniel Kahneman
The definitive popular treatment of cognitive biases, dual-system thinking, and prospect theory.
Underwrites every bias section in this curriculum and most of behavioral economics in product.
Teresa Torres
Operationalizes discovery as a weekly habit rather than a phase. Introduces the Opportunity Solution Tree.
Sets a practical baseline for PM-design-eng trios that want to move from feature requests to demand-led product decisions.
Marty Cagan (SVPG)
Cagan's articulation of how product teams should be structured and held accountable: empowered teams, outcomes, and discovery as a continuous practice.
Crystallizes the operating model assumed in the rest of the curriculum.
Jeff Bezos (1997 Shareholder Letter)
The Type-1 / Type-2 distinction, in Bezos's own words, embedded in his 2015 letter to shareholders.
Provides the reusable frame for matching decision speed to reversibility — a daily PM tool.
Lenny Rachitsky
Long-form interviews with senior PMs and founders covering discovery, growth, monetization, and leadership.
The single best ongoing audio source for current PM practice across companies and stages.