Primeiros princípios e psicologia de produto
Desenvolva a mentalidade operacional, modelos mentais e o julgamento consciente de vieses por trás de cada decisão de PM.
Explainer
A gestão de produto começa por uma forma de ver. Antes dos frameworks, dos roadmaps ou das métricas, o trabalho do PM é traduzir ambiguidade em decisões que se acumulam. Isso significa segurar ao mesmo tempo a realidade do usuário, a economia do negócio e as restrições do sistema, e escolher o que aprender em seguida sem desviar do fosso entre o que você sabe e o que você assume.
O PM como tradutor, não mini-CEO
O enquadramento de 'PM como mini-CEO' é enganador. PMs raramente têm autoridade de contratar/demitir sobre seu time e nunca controlam unilateralmente a capacidade de engenharia. O enquadramento mais útil é o de tradutor: entre verdade do usuário e resultados de negócio, entre estratégia e tickets, entre o que é possível hoje e o que será possível depois da próxima aposta dar certo. A influência vem da qualidade da tradução, não do título.
- Traduza a dor do usuário no menor enunciado de problema possível de aprender.
- Traduza objetivos de negócio em mudanças de comportamento observáveis que o time consiga mirar.
- Traduza restrições técnicas em trade-offs de produto que o time consiga debater.
Usuário vs cliente vs comprador vs champion
A maioria dos erros de PM começa colapsando quatro stakeholders diferentes em uma palavra só. O usuário experimenta o produto; o cliente paga; o comprador assina; o champion advoga internamente. Em B2C e prosumer, costumam colapsar em uma só pessoa. Em B2B, saúde, governo e marketplaces, são stakeholders distintos com incentivos conflitantes e disposição a agir muito diferente.
- Usuário: tira valor ou fricção do uso diário; arca com o custo de troca.
- Cliente: paga a conta; se importa com ROI, governança, segurança.
- Comprador: assina o contrato ou aprova o rollout; se importa com risco e política.
- Champion: empurra a adoção dentro de uma org; se importa com credibilidade e vitórias visíveis.
- Mapeie-os por workflow antes de mapear funcionalidades.
O triângulo do produto: viabilidade, usabilidade, factibilidade
Toda decisão de produto vive dentro de um triângulo: viabilidade de negócio (isso ganha ou economiza dinheiro?), valor e usabilidade para o usuário (resolve mesmo um problema real melhor do que as alternativas?) e factibilidade técnica (conseguimos construir, operar e evoluir isso com nosso time e stack?). PMs fortes circulam livremente entre as três lentes; PMs fracos deixam uma dominar por padrão — geralmente aquela com a qual estão mais confortáveis.
- Viabilidade: receita, custo, economia de retenção, exposição regulatória e contratual.
- Valor e usabilidade: demanda comprovada, disposição para trocar, facilidade de aprendizado, acessibilidade.
- Factibilidade: latência, confiabilidade, segurança, observabilidade, manutenção, capacidade do time.
- Quando os stakeholders divergem, nomeie qual canto do triângulo cada um defende — a maioria das discordâncias é choque de cantos, não de fatos.
Resultados vs entregáveis vs atividades
A distinção do Marty Cagan é uma das mais úteis em produto. Entregáveis são as coisas que você envia; atividades são as coisas que você faz; resultados são as mudanças em comportamento de usuário ou desempenho de negócio que você causa. A maioria dos times mede atividades ('fizemos entrevistas de descoberta esta semana'), alguns medem entregáveis ('lançamos 8 features'), e só os melhores medem resultados ('editores ativos semanais subiram de 41% para 49% no novo cohort'). Roadmaps guiados por entregáveis parecem produtivos mas raramente movem o negócio.
- Atividades são as mais fáceis de fingir e as mais comuns em relatórios de status.
- Entregáveis parecem progresso mas só importam se um comportamento de usuário muda.
- Resultados forçam o time a admitir quando o trabalho não moveu a métrica.
- Reformule qualquer afirmação de entregável perguntando: 'Que comportamento de usuário deveria mudar por causa disso, e como saberíamos?'
Decisões tipo 1 vs tipo 2
A distinção do Jeff Bezos: decisões tipo 1 são portas de mão única — difíceis ou impossíveis de reverter (escolhas de arquitetura, mudanças públicas de preço, M&A). Decisões tipo 2 são portas de mão dupla — fáceis de reverter (a maioria dos lançamentos de feature, mudanças de copy, experimentos de preço em uma única cohort). Tratar decisões tipo 2 como tipo 1 é o freio mais comum à velocidade. Tratar decisões tipo 1 como tipo 2 é a fonte mais comum de desastre.
- Por padrão, parta para a ação em decisões tipo 2; envie rápido, aprenda rápido, reverta se errar.
- Desacelere em decisões tipo 1; chame as vozes mais fortes, faça um pre-mortem.
- Quando estiver em dúvida, pergunte explicitamente: 'Como reverteríamos isso em 7 dias se estiver errado?'
Pensamento por primeiros princípios
Raciocinar por analogia é rápido e perde informação ('vamos fazer o que a Stripe faz'). Raciocinar a partir de primeiros princípios é mais lento e mais durável: decomponha um problema em fatos que não dá para discutir, e construa de volta. PMs usam isso para desafiar suposições herdadas ('sempre cobramos por assento'), para estimar do zero quando não existe benchmark, e para detectar estratégias copia-cola que não cabem nas restrições reais do time.
Modelos mentais que PMs deveriam internalizar
Modelos mentais são atalhos de pensamento reutilizáveis que comprimem experiência. O ponto não é decorá-los, mas manter meia dúzia na ponta da língua para escolher o certo no meio de uma conversa.
- Inversão: em vez de perguntar 'como ter sucesso?', pergunte 'como garantiríamos o fracasso?' e evite essas coisas.
- Pre-mortem: assuma que o lançamento falhou e escreva o post-mortem antes de enviar.
- Pensamento de segunda ordem: 'e depois?' Mapeie as consequências das consequências.
- Steel-manning: enuncie a posição contrária mais forte do que o oponente conseguiria antes de discordar.
- Falseabilidade: uma crença que nunca pode ser refutada não é uma crença útil.
- Navalha de Hanlon: nunca atribua à maldade o que falta de contexto explica adequadamente.
- Cerca de Chesterton: não remova uma restrição antes de entender por que ela foi posta lá.
Arquétipos de PM (e por que importam)
PM é um dos papéis mais amplos em tech. O dia a dia de um Growth PM é radicalmente diferente de um PM de Plataforma. Saber a qual arquétipo seu papel se aproxima ajuda a escolher as métricas, parceiros e habilidades certas para investir.
- Product Lead PM: superfícies voltadas ao usuário final; alta parceria com design; métricas de ativação e retenção.
- Growth PM: experimentação intensa; foco em funil; parceria com marketing e dados; métricas AARRR.
- PM de Plataforma / Infra: interno ou voltado a desenvolvedores; ergonomia, confiabilidade, adoção; parceria com engenharia em roadmaps de capacidades.
- Technical PM: superfície profundamente técnica (APIs, SDKs, produtos de dados, sistemas ML); muitas vezes escreve specs em termos quase-protocolares.
- Data / ML PM: ground truth, avaliação, comportamento de modelo, direitos sobre datasets; parceria com pesquisa.
- Internal Tools PM: funcionários são os usuários; ROI são horas economizadas e erros evitados; a política é a parte difícil.
Frameworks de decisão: DACI, RAPID, RACI
Velocidade em produto é, em boa parte, clareza sobre quem decide o quê. DACI (Driver, Approver, Contributors, Informed) e RAPID (Recommend, Agree, Perform, Input, Decide) são os mais úteis para decisões de produto. RACI é mais comum para rollouts operacionais. Escolha um e use de forma consistente — o formato importa menos que a disciplina de nomear um único Approver / Decide.
- Driver / Recommend: escreve a proposta; geralmente o PM.
- Approver / Decide: bate o martelo; só uma pessoa, nomeada explicitamente.
- Contributors / Input: trazem expertise; o trabalho deles é serem ouvidos, não vetar.
- Informed: ficam por dentro; não precisam opinar.
Mapeamento de stakeholders
Um mapa de stakeholders é o artefato PM mais subutilizado. Plote os stakeholders num 2x2 de poder e interesse. Alto poder / alto interesse precisam ser coautores do plano. Alto poder / baixo interesse precisam ser informados, não consultados em cada detalhe. Baixo poder / alto interesse normalmente são seus evangelizadores. Baixo poder / baixo interesse é ruído.
- Atualize o mapa no início de cada trimestre.
- Nomeie o que cada stakeholder tem em jogo pessoalmente — risco de carreira, carga do time, impacto na marca.
- Planeje pontos de contato deliberados, não atualizações casuais de corredor.
O sistema operacional do PM
Grandes PMs operam num ritmo semanal — não em heroísmos. Um ritmo simples: revisão de resultados na segunda (onde estão as métricas vs plano?), descoberta e trabalho escrito assíncrono no meio da semana, sessão cross-funcional na quarta ou quinta, nota semanal na sexta. Substitua reuniões de status por uma nota semanal de uma página; substitua pedidos ad-hoc por uma fila de triagem.
- Por padrão, comunicação escrita assíncrona; reserve o sync para decisões e divergências.
- Mantenha um 'now / next / later' público para que stakeholders se autosirvam.
- Mantenha um log privado de 'incógnitas': cada suposição que você ainda não testou.
- Bloqueie tempo para trabalho profundo; tetris de agenda é jogo de status, não estratégia de produtividade.
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.