"We do not punish mistakes — we punish the absence of thought."
Project Axiom is the culmination of everything I've learned about teaching product management. It is not a course. It is not a case study. It is a world — one built to make a single thing visible: the quality of your thinking under pressure.
The problem Axiom solves
I've taught product management across multiple institutions. In every cohort, I see the same failure mode: students who have learned to perform PM work without actually doing it.
They know the frameworks. They can recite the double diamond. They can produce a PRD that looks right. They've seen enough case studies that they can pattern-match to the "correct" answer.
But when you change a variable — when you give them a scenario that doesn't look like the cases they've seen, when you ask them to hold a position under sustained interrogation, when the stakeholders in the room have conflicting incentives — they reach for the pattern and the pattern fails them.
Axiom is designed to catch that. The simulation cannot be gamed by pattern-matching. It rewards coherent reasoning, and it makes the absence of reasoning visible, immediately and specifically.
The Six Pillars
Radical Continuity. Every decision you make in Axiom is recorded and visible. The simulation proceeds with the full weight of your history. You cannot start fresh. You cannot walk back a position without incurring cost. This is how product work actually operates: decisions compound, and the most consequential constraint you'll face tomorrow is the decision you made without enough thought today.
Cohesion over Correctness. There is no single right answer in Axiom. There are internally consistent answer sets, and internally inconsistent ones. You can take an unusual position — argue for a metric that no one else would choose, make a counterintuitive prioritization call — and do brilliantly, if you hold it with rigor and the rest of your reasoning is coherent with it. Incoherence is the only thing that reliably fails.
Tax on Mental Laziness. Vague answers are not scored as zero. They're scored as a choice. The simulation infers the most literal or conventional reading of what you said, and proceeds accordingly. If your answer was intentionally vague to avoid committing, the simulation commits for you — to something you may not have intended. This mirrors a real organizational dynamic: in the absence of clarity, people fill the gap with their own assumptions.
Fog of Strategy. You never have complete information in Axiom. The simulation withholds things — not arbitrarily, but as a model of real uncertainty. You'll reach a decision point and discover that you've been missing context you didn't know you were missing. The scenario isn't testing whether you could have found the right answer with full information. It's testing how well you perform when you know you're uncertain, and whether you know what you don't know.
Humanity of the Machine. The users in Axiom are people. They have names, histories, anxieties. At unexpected moments, the simulation surfaces a specific user's experience — a support ticket, a session recording, a message to the team. You cannot stay purely analytical. The pillar tests whether your reasoning holds when it has to sit alongside something that makes you feel.
The Legacy Audit. At the end of every Axiom scenario, the simulation runs a retrospective: given every decision you made, what does this product now say about what you value? Not what you intended to value — what the decisions revealed about your values. This is the most uncomfortable part of the simulation. It's also the most important.
The first scenario
The first full Axiom scenario is called Pulse. You play as the Head of Product at a mental health app that is, by all visible metrics, succeeding. Your dashboards are green. Your investors are happy. Your users are sick.
The scenario unfolds over three in-simulation weeks. You'll make decisions about which metrics to prioritize, how to respond to a safety incident, what to tell the board, and how to handle a design debate within your team. Every decision is recorded. The Legacy Audit at the end is specific to what you chose.
Pulse is nearly complete. Early cohorts have gone through rough versions. The feedback has been consistent: it's uncomfortable in exactly the right way.
What I hope Axiom does
I hope Axiom creates the experience of being caught — really, unambiguously caught — in the act of mental laziness. Not by me. By a system that has no stake in making you feel good.
That experience, I believe, is more educational than almost anything I can do in a classroom. Being told "you're not thinking carefully enough" is easy to dismiss. Having a system show you, concretely, what your uncaught assumption produced — that's harder to argue with.
The deeper hope is that the habits Axiom builds transfer. That the reflex of asking what would the world look like if I'm wrong? becomes automatic. That graduates of Axiom carry a different relationship with their own certainty — not less confident, but more honest about the architecture of their confidence.
That's the only goal. Everything else is scaffolding.