The 30 Day Operations Review Kit
By Akkul Dhand · Published 26 October 2026
Find the few operational problems worth fixing first, with evidence and accountable action.
Who this is for: Owners and operators who need a bounded review of business performance rather than an open-ended transformation exercise.
Start with actual work. A polished process chart can describe a business that exists only in the meeting room.
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.
- Where does work wait longest?
- Which errors or complaints recur?
- Do reported volumes reconcile to completed work?
- Where is critical knowledge concentrated in one person?
- Which recurring problems already have attempted fixes?
2. Put the method to work
1. Days 1–5: define scope and baseline
Choose one value stream or a small set of processes. Agree the review question, boundaries, participants and access. Gather volume, turnaround, quality, cost and backlog evidence for a representative period. Record missing or inconsistent data.
2. Days 6–10: observe real delivery
Follow a sample of work from request to completion. Include routine, delayed and failed items; explain how the sample was chosen. Record actual handoffs, waiting, rework and exceptions. Speak with employees who perform the work, not only their managers.
3. Days 11–15: test the causes
Compare observations with the stated process. Test whether delays arise from demand, capacity, approval rules, training, systems or poor inputs. Separate a hypothesis from a demonstrated finding. Avoid turning one memorable incident into a general conclusion.
4. Days 16–20: prioritise findings
For each finding, document evidence, consequence, frequency, confidence and likely effort to fix. Flag immediate material control or safety concerns for the appropriate owner without waiting for the final report. Select a small number of high-impact actions.
5. Days 21–30: agree and start fixes
Assign owners, baselines, dates and guardrails. Pilot feasible changes and verify early results. Present unresolved questions and limitations alongside recommendations. Schedule a follow-up to check whether the change survived normal operating pressure.
3. A worked example
Illustrative example: a service team attributes late delivery to insufficient staff. A sample of completed and overdue cases shows that many wait for missing customer information before work starts. The first pilot improves intake checks and separates waiting time from processing time. Hiring remains an option, but the review tests the actual constraint first.
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.
| Finding | Evidence and sample | Business consequence | Action / owner | Verification measure |
|---|---|---|---|---|
| Incomplete intake delays work | Observed case sample; method recorded | Late completion and repeat contact | Pilot intake check; service lead | Waiting time, completeness and total turnaround |
5. Action plan
- Set a scope that can be observed in 30 days; do not promise to review the whole business.
- Reserve employee time and agree confidential handling of sensitive evidence.
- Hold a midpoint evidence review to challenge assumptions.
- Finish with a small action register and a dated follow-up.
6. Check whether it worked
- End-to-end turnaround, separated into processing and waiting where possible.
- Backlog age distribution and first-pass quality.
- Pilot results against the same scope and baseline definition.
This is a management review, not an independent assurance, financial or statutory audit. Do not imply assurance or generalise small samples without explaining their limits.
What you should leave with: A prioritised findings register, three to five agreed actions and a follow-up review date.