Case Studies

Tools built rather than written about, and a case study for each: what the problem was, what the thing does, the screen it exists for, and what it cannot do. Written from the build, not from the plan — including the parts that did not work.

Case study
Rubric — a PM-shaped eval tool

Bring 50 real cases and a rubric written in plain English, and get a score you can rerun after any change. The screen that matters is the diff: which cases moved, and in which direction.
Case study
Scorecard — a launch prediction ledger

Write down what success looks like before you ship, and keep the verdict whichever way it lands. Unclear counts as an answer, and the ledger says how good your predictions have actually been.
Case study
Synthesizer — themes from interview transcripts

Reads a set of transcripts and returns themes and contradictions, where every claim is built from quotes checked word for word against the transcript they came from. A quote it invents is caught on the page, not by you, later.
Case study
Monday — a founder’s update drafter

Drafts the team update and the investor update from the same week, asks the two questions the tracker cannot answer, and never invents progress. It drafts; you send.
Case study
Confidence — a roadmap without dates

Records how sure you are instead of when it lands, and makes you say why whenever the number moves. Once things resolve it tells you whether your seventy percent means seventy percent.
Case study
RICE check — is the ranking real?

Shows which of the four inputs is actually setting the order, and how much of your ranking survives nudging every estimate by a single notch. Often: not much.
Case study
Metric map — what the number makes people do

Walks a north star through each group it lands on and gives the honest response and the shortcut side by side, then hands you the counter-metric that would catch the shortcut.