What should a practical operational health check examine?
An operational health check should reveal where everyday work loses ownership, reliable information or a clear next step. Follow a recent order through the team and use specific examples to test the handoffs and controls. Choose one practical improvement, name an owner and review the result without hiding serious risks inside an average score.
Keep these in mind
- Use actual jobs and records to test the process.
- A ten-question checklist is an adaptation, not an official McKinsey assessment.
- Prioritize actions by customer impact, exposure and frequency.
Use frameworks to ask better questions
The McKinsey 7-S framework considers connected organizational factors rather than structure alone. A new system depends on suitable roles, skills and working habits. Review those conditions alongside the software.
The ten questions below are our practical small-team diagnostic. They are not McKinsey’s checklist, a certification or a statistically validated score. The goal is to find where today’s work depends on unclear ownership, missing context or fragile assumptions.
Choose three recent completed jobs and two difficult open jobs. Those examples give the discussion enough evidence to move beyond everyone saying the process usually works.
Ask ten concrete questions
For each question, use a simple status: evidence present, evidence missing or observed problem. Investigate a missing record to understand whether the action failed or simply went undocumented.
| Area | Question to test |
|---|---|
| 1. Intake | Can we identify the actual customer request? |
| 2. Ownership | Does every open job have an accountable person? |
| 3. Promise | Can we find the agreed scope and date? |
| 4. Change | Can staff identify the latest approved revision? |
| 5. Capacity | Does accepted work fit the limiting resource? |
| 6. Blockers | Does each delay have a reason and next step? |
| 7. Quality | What evidence shows the job met requirements? |
| 8. Money | Are expected and verified payments distinct? |
| 9. Cover | Can someone continue when the owner is away? |
| 10. Learning | Did a repeated problem lead to a process change? |
An illustrative finding and action
A service team checks five jobs. Four have clear ownership, but two changed delivery dates appear only in the owner’s messages. Dispatch used the original dates.
The problem is not simply that communication needs improvement. The specific gap is an approved-date change without a shared update route.
The person approving a changed date records it with the order and identifies affected teams. They confirm acknowledgment before the next dispatch plan. The operations lead owns the trial and reviews the next ten date changes.
This is narrow enough to verify. Buying a new platform before agreeing who approves and records the date would leave the underlying responsibility unclear.
Turn the audit into a short improvement cycle
Rank findings by consequence and recurrence. A rare safety-critical failure can deserve attention before a frequent formatting annoyance. Do not calculate one overall percentage that hides an unacceptable issue.
The EPA guidance on SOP preparation offers a source for controlled procedures. Use the relevant idea here: document the chosen method, assign ownership and keep revisions understandable. The broader checklist remains our editorial application.
- Select recent jobs that include normal work and exceptions.
- Check each question against evidence rather than memory alone.
- Record the specific gap and who is affected.
- Choose one important change with an owner and review date.
- Test the change on subsequent jobs and keep the result visible.
Review the system without blaming the team
People often build workarounds because the process does not fit the work. Ask why a detail stayed in a chat, why a person lacked authority or why a form was skipped. The answer may reveal an unnecessary step or an unrealistic expectation.
Choose a small improvement with an owner, a review date and a visible sign of success. For a lost handoff, that might mean every open request has a responsible person and a next step. Keep financial, safety and technical checks with the appropriate specialists.
The review is useful when it produces a dependable working habit rather than another dashboard to maintain.
Repeat the review after meaningful changes or recurring failures. The purpose is a more dependable way of operating, not an impressive audit score.
Common questions
Where should an operational health check begin?
Follow a recent order or customer request through the team. Ask whether ownership, current information, exceptions and completion are clear. Real examples reveal practical gaps more reliably than abstract scores alone.
What should happen after the health check?
Choose a small improvement, an owner and a way to judge the result. Review after a meaningful trial. Keep serious financial, safety or service risks visible rather than averaging them into an acceptable score.
Sources & further reading
Primary references for the facts and frameworks discussed. Worked examples and recommendations are Daltn’s own analysis.
- Enduring Ideas: The 7-S Framework, McKinsey ↗
Supports considering connected organizational factors; the ten-question diagnostic is not attributed to McKinsey.
- Guidance for Preparing Standard Operating Procedures, US EPA ↗
Supports documented procedures and controlled improvement.
Published by the team building Daltn. Comparisons are first-party analysis, not independent reviews. Our editorial approach.