The Accountability Operating System
By Akkul Dhand · Published 26 October 2026
Turn recurring chasing into clear commitments, visible exceptions and timely decisions.
Who this is for: Leadership teams where work is discussed repeatedly but delivery remains unpredictable.
Accountability requires a clear commitment, an owner who can act and a fair review of the result. Fear is a poor substitute.
1. Diagnose before acting
Answer each question with a concrete example or piece of evidence. Mark unknowns openly. This is a discussion aid, not a validated scoring instrument.
- Does every important action have one named owner?
- Can the owner describe what “done” means?
- Were time, authority and dependencies considered before the commitment?
- Are blockers raised early enough for anyone to help?
- Does the review distinguish a bad estimate from avoidable non-delivery?
2. Put the method to work
1. Make the commitment specific
Describe the result, due date, evidence of completion and why it matters. Avoid actions such as “look into retention”. A useful commitment might be “submit the last quarter’s exit analysis and three prioritised actions by Friday”.
2. Confirm ownership and capacity
Name one accountable owner and identify contributors. Ask the owner to confirm their understanding and available capacity. Surface missing authority, competing priorities and required decisions before accepting the deadline.
3. Track the next milestone
Use a shared register with owner, due date, next milestone, dependency and evidence link. Agree what on track, at risk and blocked mean. A status colour without a definition is an opinion wearing a tie.
4. Review exceptions and decide
Keep the weekly review focused on changed risks, overdue commitments and decisions needed. Ask what has changed, what is recoverable and who needs to act. Do not make people repeat every task already visible in the register.
5. Close the loop fairly
Verify completion against the agreed evidence. When work misses, distinguish unclear scope, unrealistic planning, dependency failure, capability and repeated avoidable non-delivery. Correct the cause. Discuss individual performance privately and proportionately.
3. A worked example
Illustrative example: “improve onboarding” appears in meeting notes for three weeks. The team replaces it with a named owner, a checklist draft due Thursday, two manager trials next week and a final acceptance date. A blocked access step gets a separate decision owner. Completion means the trial has run and feedback has been addressed, not that a document exists.
4. Working sheet
The first row shows how to fill this in. Use the blank rows for your own business. Add evidence links and review dates to your working copy.
| Outcome and completion evidence | Owner | Due date / next milestone | Dependency or blocker | Decision needed |
|---|---|---|---|---|
| Trial onboarding checklist in two teams; feedback resolved | People operations lead | Draft Thursday; trial next week | IT account access | IT lead to confirm access turnaround |
5. Action plan
- Week 1: rewrite ten live actions into clear commitments.
- Week 2: run one short exception review.
- Week 3: analyse missed commitments and fix the largest recurring cause.
- Week 4: remove duplicate trackers and retain one agreed register.
6. Check whether it worked
- Commitments completed on time with accepted evidence / commitments due.
- Median age of unresolved blockers.
- Repeated misses by cause, alongside priority and workload changes.
Do not reward a high completion rate created by easy targets, hidden delays or repeatedly moving dates. Keep the original due date and show revised commitments separately.
What you should leave with: One commitment register, defined status rules and a weekly decision review.