Loading
You can already build the thing and defend the interaction. What you cannot yet do reliably is say what it is worth to a person whose job is earnings growth against a hold period. “We added a review gate” is a true sentence that buys nothing. “We cut the error rate that was generating support tickets and blocking adoption” is the same work, stated in the language the room keeps its books in. This course drills that translation, and drills the honest version of it.
Start lesson one: The fund, the clock, and who you are actually pitching →
There are two ways to lose this argument, and only one of them is obvious. The first is to stay in design language, get read as a cost centre, and be defunded on the next planning cycle. The second is worse and far more tempting: to reach for a business number that sounds decisive — a retention point, a churn reduction — and attach it to a UI change that plausibly did nothing. That trade buys one good quarter and spends the credibility of every case you write afterwards, because the moment somebody with a data team checks the attribution, the whole design function is the thing that overclaimed.
The honest version is not weaker. It is: here is the hypothesis, here is the mechanism I think connects the change to the number, here is what I will measure, and here is what would tell me I was wrong. That last clause is the one that makes the rest believable.
The whole spine is registered so the lesson numbers never move. The first module is ready; ask your teaching agent for the metric set once you have worked through it and started the case file.
The structure your proposal lands inside, before any of your arguments reach it.
The five numbers the room already thinks in, defined precisely enough to argue with.
One page, four fields, and the discipline of saying how you would know you were wrong.
This course argues against overclaiming, so it holds itself to the same rule: every number on these pages links to a source that was opened and read. Where a source sells the thing it is describing, the prose says so. If a claim looks unsupported, check the resource list and tell your teaching agent — a lesson that overclaims is a bug.