A performance dashboard that people stop arguing with
A dashboard becomes a single source of truth when every number carries one written definition, one named owner and a path back to the record.
Case notes
A case note is slower and longer than a field note. It takes one piece of work I actually did and walks through it end to end, with every identifying detail removed. Each note below holds the same four parts, in the same order, including the part nobody enjoys writing.
01 / The format
A field note argues a point. A case note does something narrower and harder. It follows one problem from the day it landed to the day it stopped being urgent, and it stays in the order things actually happened rather than the order that makes the writer look competent.
The structure does not vary. Holding the same four parts every time is what stops a note drifting into a story about how well it went. Three of the parts are comfortable to write. The fourth is not, and it is the reason the format exists.
Not the tidy version assembled afterwards. What was visible in the first week, what everyone believed was wrong, and what turned out to be wrong instead.
The design and the decisions inside it. The constraints it had to survive, the options I considered and put down, and the reason I put them down.
How the work behaved once ordinary people used it in an ordinary week. Where it held, where it needed a second version, and what it never fixed.
Every note has this section, because every piece of work has something in it worth admitting. A note without this part is an advertisement.
02 / What a case note leaves out
Three rules decide what survives into a published note:
That third rule is why this index is short rather than padded. A method that only makes sense with the real names attached was never a method. It was a story.
Meanwhile, the topic hubs