Collection
Leave work another person can use
Make results, failures, fixes and responsibilities inspectable.
Explore in any order.
What’s included
2 protocols · 4 templates
6 ideas
Build a checklist from real misses
'Check carefully' is a wish wearing a checkbox. A useful check names the action and the expected result. Build the list from errors that matter, then keep revising it when real work reveals a gap.
Read the idea TemplateWrite a bug report someone can use
A symptom is an observation. Its cause is still a hypothesis.
Read the idea TemplateSave the fix with its conditions
A solution without its conditions is a future misunderstanding. Record what failed, where the fix applied and how you knew it worked. Leave enough context for someone to decide whether the same fix belongs in a different case.
Read the idea TemplateKeep a work evidence log
When review season arrives, 'I did a lot' is not much of a case. Capture a few facts after meaningful work while you can still locate the evidence. The point is a reusable record, not a collection of heroic adjectives.
Read the idea ProtocolMap the handoffs, not just the boxes
A process diagram can look orderly while hiding the place where work actually gets stuck: the handoff. Follow one real case through the system. Record what changes hands, who accepts it and what happens when the input is incomplete.
Read the idea TemplateMake the capacity trade-off visible
A new request does not create new hours. You can be helpful without pretending that every commitment fits. State what you can do, what would have to move and whose decision is needed. Keep the boundary clear enough that nobody hears a reluctant yes.
Read the idea