NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 14 — Case Studies and Final AssessmentLesson 3 of 8
Video lesson

Case Study: Late Deliveries — the Method Beyond IT

BeginnerVideo lesson
10 min readBeginner

Where you are: Module 14 — Case Studies and Final Assessment · Lesson 14.3 · Based on Chapter 14 (Case Study 4) of Dr. Tahseen Al Doori's Troubleshooting Essentials.

What you'll be able to do

  • Trace the book's non-technical Case Study 4 through all seven steps.
  • Translate troubleshooting ideas (symptom, evidence, isolation, rollback, verification) into business terms.
  • Explain how splitting data isolates a cause in the same way as half-splitting a system.
  • Evaluate the decisions made in the case and transfer the method to a problem of your own.

Watch: Case Study: Late Deliveries — the Method Beyond IT

The video shows a business with no computer fault at all: customer orders are arriving late. It walks through the same seven steps, narrows the data from every order down to two delivery routes, and shows that the fix is a familiar isolation technique wearing business clothes. As you watch, ask:

  • What is the "error message" in a business problem?
  • Which Chapter 6 technique does moving the routes back to the previous courier resemble?
  • How do you verify a fix when the outcome is a percentage, not a working device?

The case as the book tells it

StepWhat happened (book, Case Study 4)
1 IdentifyA business notices that 30% of customer orders arrived late this month, starting in mid-May.
2 TheoryA new courier, stock shortages or picking errors in the warehouse.
3 TestLate orders are analysed by courier and product: almost all late orders used the new courier on two routes.
4–5 Plan and implementThose routes are moved back to the previous courier while the issue is raised with the new one.
6 VerifyLate deliveries fall below the 3% target for the following month.
7 DocumentThe courier performance review is added to the monthly operations checklist.

Picking is the warehouse task of collecting the right items for each order before it is packed and shipped. A courier is the delivery company that carries the parcels.

The same method in business clothes

The book's key takeaway for Chapter 14 is that the method transfers to any system because it is based on logic, not on any particular technology. It helps to translate the vocabulary:

In IT troubleshootingIn this business case
Symptom: the device fails30% of orders arrive late
Error message and logsOrder and delivery records
When did it start?Mid-May
What changed?A new courier was introduced
Isolation: split the systemSplit the late orders by courier, then by route
Rollback: undo the last changeMove the affected routes back to the previous courier
Escalate to the vendor (Tier 4)Raise the issue with the new courier
Verify: the user confirmsLate deliveries fall below the 3% target
Document and preventAdd a courier review to the monthly checklist

Step by step, with the reasoning

Step 1: a measurable problem statement

"Deliveries seem slow" would be the business equivalent of "the internet is broken". The book's statement is specific and testable: a percentage (30%), a period (this month) and a start point (mid-May). There is also an implied baseline: the business has a target of 3% late, which tells us what normal looks like (Chapter 4).

Step 2: three theories, one of them a change

The three theories cover three different parts of the process: the people and process in the warehouse (picking errors), the supply of goods (stock shortages) and the delivery partner (a new courier). Notice that one theory is itself a change. Chapter 2's most powerful question, what changed?, applies to businesses as much as to laptops, and a new supplier is exactly the kind of change that precedes a new fault.

If the causes had been less obvious, a fishbone diagram from Chapter 12, with categories such as people, process, technology and environment, would be a good way to generate theories as a team.

Step 3: splitting the data

One analysis tested all three theories at once. Each theory predicts a different pattern (our reasoning):

If the cause were...Late orders would cluster by...
Stock shortagesProduct: the items that were out of stock
Picking errorsWarehouse factors, spread across couriers and routes
The new courierCourier, and possibly particular routes

The result was decisive: almost all late orders used the new courier on two routes. Splitting a large set of orders by one factor, then by another, is the data version of the half-split method: each split removes a large share of the possibilities until only a small area remains. From every order, to late orders, to the new courier, to two routes.

Steps 4 and 5: a scoped rollback plus escalation

The plan has two parts, and both echo earlier chapters.

  • Move those routes back to the previous courier. This is rollback from Chapter 6: if a problem began after a change, reverse it. Importantly, only the two affected routes are rolled back, not the whole contract. That limits the impact of the change and keeps the evidence clear.
  • Raise the issue with the new courier. The courier is an external party, the business equivalent of escalating to a vendor at Tier 4. The rollback restores service for customers while the root cause is pursued with the people who can fix it.

Step 6: verification against a target

In IT, verification means repeating the action that failed and asking the user. In a business process, it means measuring against the target over a meaningful period. Late deliveries fell below the 3% target for the following month. A month of data, like the two weeks in the Wi-Fi case, guards against a lucky few days.

Step 7: documentation that prevents recurrence

Adding a courier performance review to the monthly operations checklist is a Chapter 12 preventive measure, a form of monitoring. If a courier starts slipping again, the business finds out in weeks rather than after a month of unhappy customers.

Evaluating the decisions

DecisionTechnique or principleAssessment
Stated the problem with a percentage and a dateProblem statement; baselineStrong: measurable and testable
Included the recent change as a theoryWhat changed?Strong: the change proved to be the cause
Analysed late orders by courier and productIsolation by splitting dataStrong: one analysis tested all three theories
Moved only the two routes backScoped rollbackStrong: limited impact, clear cause and effect
Raised the issue with the new courierEscalation to an external partyCorrect: the root cause sits with the supplier
Measured for a month against the 3% targetVerification over timeStrong: meaningful evidence
Added a review to the monthly checklistMonitoring as preventionGood: catches recurrence early

Our commentary on what you might do differently: customers who received late orders were affected, so the Chapter 13 communication principles apply to them too. A short apology and a realistic delivery expectation for anyone waiting could limit the damage while the fix takes effect. And the record should note what the new courier said, so that the decision about the two routes can be reviewed later on evidence.

The seven steps are logic, not technology. State the problem in numbers, ask what changed, split the evidence until the cause has nowhere to hide, undo the change that caused it, verify against a target and build the check into routine.

Try it

A paper exercise with no equipment needed. Choose a non-technical problem you have seen at work, at university or at home (for example: a society's events are poorly attended, a team keeps missing a weekly report deadline, or a café's queue is long at certain times).

  1. Write a measurable problem statement with a number, a time period and a start point.
  2. List three theories, including at least one change.
  3. Describe the data split that would tell your theories apart, and the pattern each theory predicts.
  4. Write a plan that includes a way to undo it, and say who outside your team you might need to involve.
  5. Write a verification measure with a target and a period.
  6. Write one line for a checklist that would catch the problem if it came back.

Completion criteria: all six steps written; the problem statement is measurable; each theory predicts a different pattern; the verification has both a target and a period.

Knowledge check

Which Chapter 6 technique does moving the two routes back to the previous courier most resemble?

Why was analysing late orders by courier and product an efficient test?

How was the fix verified in Case Study 4?

What is the main lesson the book draws from Case Study 4?

Answers explained

  1. a — The problem began after a change (the new courier), and reversing that change is rollback; nothing was stripped back and restored, and bottom-up and top-down are orders of testing, not fixes.
  2. c — Distinct predicted patterns let one analysis separate the theories; the change still mattered, verification was still needed, and the analysis does not prove anyone blameless.
  3. b — Verification measured the outcome against the target for a month; promises, one day of checks or a quiet week are weak evidence.
  4. d — The chapter summary states that the methodology applies equally to business processes.

Key takeaways

  • The seven steps transferred unchanged from IT to a business process: the method is logic, not technology.
  • A measurable problem statement (30% late since mid-May, against a 3% target) made the problem testable.
  • Splitting the data by courier and product isolated the cause to the new courier on two routes.
  • A scoped rollback restored service while the issue was escalated to the courier; a month below target verified it; a checklist item prevents recurrence.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 14 Case Study 4, key takeaway and chapter summary, §2.3, §4.5–4.6, §6.1, §6.6, §12.3–12.4, §13.1, §13.4, Figure 13.1