Library/T-09
Leverage Prioritization Matrix
Put every finding in order: what to do now, next, later, or deliberately leave alone.
Subtract · Automate · Vest · Exit (close)T-09
The pattern it solves
An audit produces a long list and nothing gets done, or the most interesting fix gets done first instead of the most valuable.
Signals you need it
More than a handful of findings. No agreement on where to start.
Use it when
At the end of any audit.
What it takes in
Findings, each with estimated hours per year and a rough effort.
What you end up with
Two labels per finding. **When:** Now (weeks 1–2), Next (weeks 3–8), Later (month 3+), or Freeze. **What:** its SAVE step.
The steps
- 1.Score each finding on impact (hours per year, how often, how much it depends on the owner) and ease (effort, cost, risk, how easy to undo, time to value).
- 2.High impact, high ease → Now. High impact, lower ease → Next. High impact, hard → Later. Low impact → Freeze (closing Exit: keep it running, stop improving it).
- 3.No more than 2–3 per horizon.
- 4.Attach the SAVE step to each.
How it returns time
Spends effort where it returns the most time first, and says out loud where to stop.
What to measure
Hours per year addressed by Now items; share of Now items installed on schedule.
What to measure, before and after. Not what anyone achieved — there are no client results to report.
Where it comes from
Adapted from the impact × effort grid, a general prioritization practice; the Now / Next / Later horizons match the Time Buyback Plan.
What it fixes
Every category in the library
This one is not aimed at a particular leak. It runs across all twenty.
- 01Recurring reports nobody acts on
- 02Agenda-less recurring meetings the owner attends
- 03Tool sprawl and shelfware
- 04Owner's inbox and message triage
- 05Quoting, proposals, and estimates
- 06Scheduling back-and-forth
- 07Invoicing, receivables, and payment chasing
- 08Re-keying data between systems
- 09Onboarding done from memory
- 10Repeated questions and tribal knowledge
- 11Approvals bottlenecked on the owner
- 12The "only I can do this" tasks
- 13Rework
- 14Waiting on external dependencies
- 15Context switching and fragmented attention
- 16Non-utilized talent
- 17Location- or device-locked work
- 18The disproportionate client or account
- 19The service line that no longer earns its place
- 20Commitments that outlived their reason
Next