Library/T-01
Why Me?
For everything that reaches the owner, ask why it had to be that person.
Vest · Exit (open)T-01
The pattern it solves
The owner is the default destination for questions, approvals and fixes, whether or not their judgment is needed.
Signals you need it
Work stalls when the owner is away. The owner's day is mostly responding. The team says "check with the boss" for routine calls.
Use it when
Almost always first, for an owner-operator.
Do not use it when
The business has no team or vendors to hand anything to yet.
Naming where a tool does not apply is part of the tool.
What it takes in
Two weeks of owner touches (messages, approvals, interruptions, tasks), from memory, a log or the Touch Audit.
What you end up with
Every touch classified: needs the owner's judgment, or not — and if not, who or what should own it.
The steps
- 1.List every recurring touch.
- 2.For each, ask "why me?" and write the honest answer.
- 3.Mark whether the answer is judgment, habit, missing information, missing permission or missing rule.
- 4.Judgment stays. Missing information → T-07. Missing permission → T-02 / T-03. Missing rule → T-08. Habit → stop.
How it returns time
Moves the owner from handling instances to setting rules and handling exceptions.
What to measure
Owner touches per week before and after; share of touches that required judgment.
What to measure, before and after. Not what anyone achieved — there are no client results to report.
Where it comes from
Time Operators.
What it fixes
The leaks this addresses
Next
Tools that go with it
- T-02Decision Rights Map — Write down who decides what, so decisions stop defaulting upward.
- T-03Approval Thresholds — Set the line below which nobody needs to ask.
- T-04Responsibility Map (RACI) — For each step of a workflow, name who does it, who owns the result, who is consulted and who is told.
- T-08The Toil Test and the Rule of Three — Decide whether a recurring task should be automated, delegated or left alone.