Decision intelligence, documented
Every case separates what was known at the time from what became known later. You see the options that were rejected, the evidence that was missing, and the outcome measured against a stated period. Not war stories. Structured reasoning you can compare against your own situation.
What makes a case different from an essay
A decision can be reasonable and still produce a poor outcome. A good outcome can be luck. Separating these three moments is what stops a past decision from looking obvious once you already know how it ended.
The information actually available to the decision-maker — including what was missing.
The reasoning built on that information, including the options that were rejected and the reason each was rejected.
The outcome and subsequent evidence — kept visibly separate so it cannot be read back into the reasoning.
Recently published
Adoption sat at 4% of target after two quarters. Four options on the table, three rejected. The decision to discontinue was defensible on the evidence available — the error was waiting two months longer than the criteria required.
A Series B team with one open requisition and a delivery commitment eight months out. The decision turned on who would do the mentoring, and that question had no good answer.
An offer on the table at roughly half the last valuation, against a bridge at a 60% markdown. The reasoning was documented at the time. It did not survive contact with the following year.
See all 9 casesCurated collections
Four cases where the question was not whether the work was good, but whether continuing it was the right use of the next six months.
4 casesThree cases where a known information event sat just beyond the decision deadline, and the decision-maker chose not to wait.
3 casesHiring, cutting and restructuring when the budget envelope is fixed and the consequences land on individuals.
3 casesWhat it costs to lock a price, raise one, or walk away from a counterparty you depend on.
3 casesFor readers
Filter by decision type, industry, stakes and documented outcome. A logistics procurement case and a SaaS pricing case can share the same underlying trade-off — fixed budget line against a trending input market — and the library is built so you can find that.
Search the libraryFor creators
Non-exclusive licence, redaction and anonymity supported, and a revenue pool with a published allocation rule you can read before you agree to anything. We do not pay by page view.
Submit a case