One promise, many moving parts: a fault is fixed once, and some are fixed again.
Find · Ways to fix it
3ways lead
6 strong candidates of 26
What you record builds the shortlist.
1Leading
Get ready before the work arrives
Set up or automate in advance so work is faster when it arrives
Why it leads: Your split by “Parts needed” shows “yes” cases take about 5.7 days longer (255 against 105 cases).
The split points to this pattern: the work waits for materials, people or information that could have been fetched before it started.
How it helps: Get what the “Parts needed: yes” cases need ready before they reach the step that waits for it.
From your records
Get ready before the work arrives
No close past fix on file yet
Watch out for
Prepare the plan before the moment arrives, since in one study that let leaders move fast when a window opened.
Ask whether there is a ready group of people to start with, because in one study a predefined patient pool helped.
2Leading
Do steps at the same time
Do two or more things at the same time instead of sequentially
Why it leads: Your split by “Parts needed” shows “yes” cases take about 5.7 days longer (255 against 105 cases).
The split points to this pattern: steps run serially by convention though no true dependency exists between them.
How it helps: Start the extra work for the “Parts needed: yes” cases alongside the rest instead of after it.
From your records
Do steps at the same time
No close past fix on file yet
3Leading
Work in planned batches
Switch from constant processing to planned cycles or grouped runs
Why it leads: Your split by “Parts needed” shows “yes” cases take about 5.7 days longer (255 against 105 cases).
The split points to this pattern: work is held and released in planned cycles where the batch serves setup economics; the window itself creates queues.
How it helps: Gather the “Parts needed: yes” cases into planned batches so the extra work is done together.
From your records
Work in planned batches
No close past fix on file yet
Give the work to whoever is best placedStill in · may still fit
Link the systems so information flowsStill in · may still fit
Match capacity to demandStill in · may still fit
Let them do it themselvesFading · fits less well
Cut out a step or handoffFading · fits less well
Pull work through instead of pushing itFading · fits less well
Have a fallback readyFading · fits less well
Let the problem shape the fixFading · fits less well
Watch it as it happensFading · fits less well
Make hidden information visibleFading · fits less well
Let a system do the manual stepFading · looks unlikely to fit
Do it the same way every timeFading · looks unlikely to fit
Stop the error before it startsFading · looks unlikely to fit
Keep the work movingFading · looks unlikely to fit
Make the right way the easy wayFading · looks unlikely to fit
Give it an ownerFading · looks unlikely to fit
Change the channelFading · looks unlikely to fit
Put steps side by sideFading · looks unlikely to fit
A place for everythingFading · looks unlikely to fit
Fix before it failsFading · looks unlikely to fit
Build it into an existing stepFading · looks unlikely to fit
Ways to fix it · 3 lead · 6 in play
An example project, made up to show the work. Its 360 faults, their causes, the cases you can replay and the eight weekly readings after the change was kept are all made up, and the Dig was run on those made-up faults: nothing here is yours, nothing you do here is saved, and Find, Improve and eXecute all open.
The cases you can replay are 48 of the 360 made-up faults in the example’s file. Each moves through the steps at the pace its own row gives, and the Dig compares all 360.
Start to finishtypical 9.2 business days · most 6.3–12.2 business days
Columns
from “Reported” to “Fixed”
Cases counted
360
Calendar
(business days: 8-hour days, 5-day weeks)
How worked out
Typical is the middle case of those counted; “most” is the middle half of them, with the fastest and slowest tails left out.
1
A customer reports a fault
30 min typical
10 min1.5 h
about 1% of the typical time
1
A customer reports a fault
Step name
A customer reports a fault
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Call centre
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
A phone call or the app
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Dispatch: The fault, with the address
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not collected yet
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 30 min (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
10 min to 1.5 h, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
1A customer reports a fault30 min
2
The fault is triaged and a visit booked
1 business day typical
2 h3 business days
about 11% of the typical time
2
The fault is triaged and a visit booked
Step name
The fault is triaged and a visit booked
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Dispatch
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
The fault, with the address
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Field engineer: A booked visit
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not collected yet
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 1 business day (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
2 h to 3 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
2The fault is triaged and a visit booked1 business day
3
The engineer visits and diagnoses
2 business days typical
1 business day5 business days
about 22% of the typical time
3
The engineer visits and diagnoses
Step name
The engineer visits and diagnoses
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Field engineer
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
A booked visit
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Parts desk: A parts list, when one is needed
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not collected yet
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 2 business days (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
1 business day to 5 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Visits are booked before the fault is understood
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
3The engineer visits and diagnoses2 business days
4
The parts are ordered from the regional depot
1 business day typical
2 h2 business days
about 11% of the typical time
4
The parts are ordered from the regional depot
Step name
The parts are ordered from the regional depot
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Parts desk
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
A parts list
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Regional depot: A parts order
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not collected yet
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 1 business day (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
2 h to 2 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
4The parts are ordered from the regional depot1 business day
5
The parts arrive
3 business days typical
1 business day10 business days
about 33% of the typical time
5
The parts arrive
Step name
The parts arrive
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Regional depot
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
A parts order
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Field engineer: The parts
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not worth paying for · waiting
Read by your coach; correct it if it is wrong.
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 3 business days (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
1 business day to 10 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
The depot sends once a day; Orders for the cut-off are held to the next day
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
5The parts arrive3 business days
6
The repair is made
1 business day typical
2 h3 business days
about 11% of the typical time
6
The repair is made
Step name
The repair is made
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Field engineer
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
The parts, or a van that already holds them
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to The customer: A working service
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Worth paying for
Read by your coach; correct it if it is wrong.
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 1 business day (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
2 h to 3 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
6The repair is made1 business day
7
The repair is checked
1 h typical
20 min3 h
↺ goes back to step 3
about 1% of the typical time
7
The repair is checked
Step name
The repair is checked
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Field engineer
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
Not collected yet
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Call centre: A result of the check
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not collected yet
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 1 h (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
20 min to 3 h, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
Goes back to step 3 (the fix did not hold)
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
7The repair is checked1 h
8
The customer confirms it is fixed
1 business day typical
2 h3 business days
about 11% of the typical time
8
The customer confirms it is fixed
Step name
The customer confirms it is fixed
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Call centre
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
A result of the check
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to The customer: A closing call or message
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Has to happen
Read by your coach; correct it if it is wrong.
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 1 business day (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
2 h to 3 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
Start to finishtypical 9.2 business days · most 6.3–12.2 business days
Columns
from “Reported” to “Fixed”
Cases counted
360
Calendar
(business days: 8-hour days, 5-day weeks)
How worked out
Typical is the middle case of those counted; “most” is the middle half of them, with the fastest and slowest tails left out.
1
A customer reports a fault
30 min typical
10 min1.5 h
about 1% of the typical time
1
A customer reports a fault
Step name
A customer reports a fault
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Call centre
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
A phone call or the app
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Dispatch: The fault, with the address
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not collected yet
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 30 min (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Time split by Parts needed
yes 255
30 min
no 105
30 min
The file’s own typical for this step is 30 min.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Parts ordered before cut-off
no 154
30 min
yes 101
30 min
The file’s own typical for this step is 30 min.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Repeat visit
no 297
30 min
yes 63
30 min
The file’s own typical for this step is 30 min.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Fault type
No heating 121
30 min
Leak 103
30 min
Appliance fault 70
30 min
Electrical fault 66
30 min
The gaps between Fault type groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Fault type matters.
The file’s own typical for this step is 30 min.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Branch
Quayside 98
30 min
Eastgate 96
30 min
Northfield 91
30 min
Millbrook 75
30 min
The gaps between Branch groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Branch matters.
The file’s own typical for this step is 30 min.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Engineer team
Team A 127
30 min
Team B 121
30 min
Team C 112
30 min
The gaps between Engineer team groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Engineer team matters.
The file’s own typical for this step is 30 min.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
10 min to 1.5 h, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
1A customer reports a fault30 min
2
The fault is triaged and a visit booked
1 business day typical
2 h3 business days
about 11% of the typical time
2
The fault is triaged and a visit booked
Step name
The fault is triaged and a visit booked
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Dispatch
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
The fault, with the address
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Field engineer: A booked visit
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not collected yet
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 1 business day (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Time split by Parts needed
yes 255
1 business day
no 105
1 business day
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Parts ordered before cut-off
no 154
7.9 h
yes 101
1 business day
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Repeat visit
no 297
7.9 h
yes 63
1 business day
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Fault type
No heating 121
1 business day
Leak 103
1 business day
Appliance fault 70
1 business day
Electrical fault 66
7.8 h
The gaps between Fault type groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Fault type matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Branch
Quayside 98
7.9 h
Eastgate 96
1 business day
Northfield 91
7.8 h
Millbrook 75
1 business day
The gaps between Branch groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Branch matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Engineer team
Team A 127
1 business day
Team B 121
7.9 h
Team C 112
7.9 h
The gaps between Engineer team groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Engineer team matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
2 h to 3 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
2The fault is triaged and a visit booked1 business day
3
The engineer visits and diagnoses
2 business days typical
1 business day5 business days
about 22% of the typical time
3
The engineer visits and diagnoses
Step name
The engineer visits and diagnoses
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Field engineer
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
A booked visit
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Parts desk: A parts list, when one is needed
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not collected yet
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 2 business days (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Time split by Parts needed
yes 255
2.2 business days
no 105
2.2 business days
The file’s own typical for this step is 2 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Parts ordered before cut-off
no 154
2.2 business days
yes 101
2.2 business days
The file’s own typical for this step is 2 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Repeat visit
no 297
2.1 business days
yes 63
4.5 business days
The file’s own typical for this step is 2 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Fault type
No heating 121
2.2 business days
Leak 103
2.1 business days
Appliance fault 70
2.2 business days
Electrical fault 66
2.3 business days
The gaps between Fault type groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Fault type matters.
The file’s own typical for this step is 2 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Branch
Quayside 98
2.2 business days
Eastgate 96
2.3 business days
Northfield 91
2.1 business days
Millbrook 75
2.2 business days
The gaps between Branch groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Branch matters.
The file’s own typical for this step is 2 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Engineer team
Team A 127
2.1 business days
Team B 121
2.2 business days
Team C 112
2.2 business days
The gaps between Engineer team groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Engineer team matters.
The file’s own typical for this step is 2 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
1 business day to 5 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Visits are booked before the fault is understood
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
3The engineer visits and diagnoses2 business days
4
The parts are ordered from the regional depot
1 business day typical
2 h2 business days
about 11% of the typical time
4
The parts are ordered from the regional depot
Step name
The parts are ordered from the regional depot
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Parts desk
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
A parts list
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Regional depot: A parts order
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not collected yet
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 1 business day (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Time split by Parts ordered before cut-off
no 154
1 business day
yes 101
1 business day
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Repeat visit
no 208
8 h
yes 47
1 business day
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Fault type
No heating 106
1 business day
Leak 60
7.5 h
Appliance fault 45
7.7 h
Electrical fault 44
1 business day
The gaps between Fault type groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Fault type matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Branch
Quayside 70
1 business day
Eastgate 69
1 business day
Northfield 62
1 business day
Millbrook 54
7.6 h
The gaps between Branch groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Branch matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Engineer team
Team A 86
1 business day
Team B 86
8 h
Team C 83
7.9 h
The gaps between Engineer team groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Engineer team matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
2 h to 2 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
4The parts are ordered from the regional depot1 business day
5
The parts arrive
3 business days typical
1 business day10 business days
about 33% of the typical time
5
The parts arrive
Step name
The parts arrive
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Regional depot
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
A parts order
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Field engineer: The parts
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not worth paying for · waiting
Read by your coach; correct it if it is wrong.
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 3 business days (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Time split by Parts ordered before cut-off
no 154
5.8 business days
yes 101
1.9 business days
The Dig pins this cause to this step.
What it must reach. If cases where “Parts ordered before cut-off” is no took as long as the rest at step 5 (5.8 business days down to about 1.9 business days), the typical for all cases would move from 9.2 business days to about 8 business days.
The file’s own typical for this step is 3 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Repeat visit
no 208
4.9 business days
yes 47
4.6 business days
The file’s own typical for this step is 3 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Fault type
No heating 106
4.8 business days
Leak 60
4.6 business days
Appliance fault 45
5.1 business days
Electrical fault 44
4.8 business days
The gaps between Fault type groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Fault type matters.
The file’s own typical for this step is 3 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Branch
Quayside 70
5 business days
Eastgate 69
5.4 business days
Northfield 62
3.7 business days
Millbrook 54
4.6 business days
The gaps between Branch groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Branch matters.
The file’s own typical for this step is 3 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Engineer team
Team A 86
4.8 business days
Team B 86
5 business days
Team C 83
5.1 business days
The gaps between Engineer team groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Engineer team matters.
The file’s own typical for this step is 3 business days.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
1 business day to 10 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
The depot sends once a day; Orders for the cut-off are held to the next day
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
5The parts arrive3 business days
6
The repair is made
1 business day typical
2 h3 business days
about 11% of the typical time
6
The repair is made
Step name
The repair is made
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Field engineer
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
The parts, or a van that already holds them
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to The customer: A working service
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Worth paying for
Read by your coach; correct it if it is wrong.
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 1 business day (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Time split by Parts needed
yes 255
7.9 h
no 105
1 business day
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Parts ordered before cut-off
no 154
1 business day
yes 101
7.7 h
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Repeat visit
no 297
7.9 h
yes 63
7.9 h
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Fault type
No heating 121
7.7 h
Leak 103
1.1 business days
Appliance fault 70
1 business day
Electrical fault 66
7.8 h
The gaps between Fault type groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Fault type matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Branch
Quayside 98
1 business day
Eastgate 96
1 business day
Northfield 91
7.8 h
Millbrook 75
7.9 h
The gaps between Branch groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Branch matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Engineer team
Team A 127
1 business day
Team B 121
7.7 h
Team C 112
1 business day
The gaps between Engineer team groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Engineer team matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
2 h to 3 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
6The repair is made1 business day
7
The repair is checked
1 h typical
20 min3 h
↺ goes back to step 3
about 1% of the typical time
7
The repair is checked
Step name
The repair is checked
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Field engineer
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
Not collected yet
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to Call centre: A result of the check
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Not collected yet
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 1 h (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Time split by Parts needed
yes 255
1 h
no 105
1 h
The file’s own typical for this step is 1 h.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Parts ordered before cut-off
no 154
1 h
yes 101
1 h
The file’s own typical for this step is 1 h.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Repeat visit
no 297
1 h
yes 63
1 h
The Dig pins this cause to this step.
The file’s own typical for this step is 1 h.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Fault type
No heating 121
1 h
Leak 103
1 h
Appliance fault 70
1 h
Electrical fault 66
1 h
The gaps between Fault type groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Fault type matters.
The file’s own typical for this step is 1 h.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Branch
Quayside 98
1 h
Eastgate 96
1 h
Northfield 91
1 h
Millbrook 75
1 h
The gaps between Branch groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Branch matters.
The file’s own typical for this step is 1 h.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Engineer team
Team A 127
1 h
Team B 121
1 h
Team C 112
1 h
The gaps between Engineer team groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Engineer team matters.
The file’s own typical for this step is 1 h.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
20 min to 3 h, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
Goes back to step 3 (the fix did not hold)
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
7The repair is checked1 h
8
The customer confirms it is fixed
1 business day typical
2 h3 business days
about 11% of the typical time
8
The customer confirms it is fixed
Step name
The customer confirms it is fixed
Why we collect it. It is how you and your coach refer to this step on every screen. When. Your coach names it from your words while you walk through a recent case; you can rename it here.
Who does it
Call centre
Why we collect it. Who does a step tells the coach where work changes hands, and hand-offs are where time tends to be lost. When. Your coach will ask while you walk through a recent case.
What arrives, from where
A result of the check
Why we collect it. What arrives, and from where, shows what each step depends on and where work waits for something. When. Your coach will ask while you walk through a recent case.
What leaves, to where
to The customer: A closing call or message
Why we collect it. What leaves, and where it goes, shows what each step hands on and joins one step to the next. When. Your coach will ask while you walk through a recent case.
Nature of work
Has to happen
Read by your coach; correct it if it is wrong.
Why we collect it. Whether a step is worth paying for, has to happen, or is not worth paying for tells the instruments where effort is wasted. When. Your coach reads it from your words and asks you to agree or correct it.
Moment of truth — does the customer feel it?
Not collected yet
Why we collect it. A moment of truth is a step your customer feels, so delay or error there costs you their trust and counts for more. When. Your coach will ask which steps your customer notices.
Time: hands-on, waiting, start to end
Typical 1 business day (your estimate)
Why we collect it. The time a step holds is what the board draws and what the Dig compares; a time from your file is never typed over, and your own estimate sits beside it, marked as yours. When. This comes from your file once it has a date for when the step started and finished, or from your best guess until then.
Time split by Parts needed
yes 255
7.9 h
no 105
7.7 h
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Parts ordered before cut-off
no 154
7.9 h
yes 101
1 business day
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Repeat visit
no 297
1 business day
yes 63
7.8 h
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Fault type
No heating 121
7.7 h
Leak 103
7.8 h
Appliance fault 70
1 business day
Electrical fault 66
1 business day
The gaps between Fault type groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Fault type matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Branch
Quayside 98
8 h
Eastgate 96
1 business day
Northfield 91
1 business day
Millbrook 75
7.6 h
The gaps between Branch groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Branch matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Time split by Engineer team
Team A 127
1 business day
Team B 121
7.6 h
Team C 112
1 business day
The gaps between Engineer team groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Engineer team matters.
The file’s own typical for this step is 1 business day.
Why we show it. This shows how long the step holds the cases of each group of the cause you are looking at, so you can see where one group waits longer than the rest. When. It appears in the Dig, once your file has been looked at for causes.
Where the time comes from
Basis
What you told us. No file figure has replaced it yet.
Range
2 h to 3 business days, as you said
Why we collect it. This says which columns, how many cases and which calendar a time rests on, so you can judge how far to trust it. When. It appears once a time has been measured from your file.
Loops and rework
No return from this step is recorded.
Why we collect it. A step that sends work back is rework, the single most useful thing to find on a map. When. Your coach marks a return when you describe one; a column that marks redo lets us count how many cases went round.
What we are not sure of
Whether the file would agree: this is your estimate, not a measurement.
Why we collect it. Saying what we are not sure of keeps the board honest and tells the coach what to ask next. When. We note it as it comes up while you walk through your process.
Possible causes noted
Not collected yet
Why we collect it. Possible causes are things you or your coach suspect make this step slow or go wrong, and the Dig tests them against your file. When. They are pinned in the Dig once your file is read.
Focus
Not collected yet
Why we collect it. A focus marks the step you have chosen to look at more deeply, so the Dig and the fix start there. When. We pin it when you choose where to dig.
8The customer confirms it is fixed1 business day
Colour the cases by
yes 255no 105no 154yes 101no 297yes 63No heating 121Leak 103Appliance fault 70Electrical fault 66chance, drawn mutedQuayside 98Eastgate 96Northfield 91Millbrook 75chance, drawn mutedTeam A 127Team B 121Team C 112chance, drawn muted
Run these cases
Choose
A factor, then one or several of its options. The board above replays only those cases, each option in its own colour.
Grid
Two factors make a grid: every cell shows how many cases it holds and their typical time. Click a cell to run it; click several to race them on the same board.
Shading
A cell is shaded by how its typical time sits against what the customer needs. A cell with fewer than 5 cases is greyed: too few to read.
Too many cases
When a choice holds more than the board can draw, it replays a representative sample (every outlier included); the counts below are always of all the cases chosen.
Factor
The number, split by Parts needed
Cause
Parts needed
Groups
yes (255), no (105)
Chance reading
The gaps are bigger than chance gives.
Same axis
Every line below runs on one axis, so the groups can be compared.
Each dot
One case, placed by how long it took.
Thick part
The middle half of the cases.
Tick
The median, the typical case.
Ringed dots
Cases far out from the rest.
Red line
The promise.
This split
Parts needed separates the cases by more than chance would.
yes 255 cases · typical 11.2 business days
no 105 cases · typical 5.5 business days
What it must reach. If cases where “Parts needed” is yes took as long as the rest, the typical for all cases would move from 9.2 business days to about 5.5 business days.
The number, split by Parts ordered before cut-off
Cause
Parts ordered before cut-off
Groups
no (154), yes (101)
Chance reading
The gaps are bigger than chance gives.
Same axis
Every line below runs on one axis, so the groups can be compared.
Each dot
One case, placed by how long it took.
Thick part
The middle half of the cases.
Tick
The median, the typical case.
Ringed dots
Cases far out from the rest.
Red line
The promise.
This split
Parts ordered before cut-off separates the cases by more than chance would.
no 154 cases · typical 12.5 business days
yes 101 cases · typical 8.5 business days
What it must reach. If cases where “Parts ordered before cut-off” is no took as long as the rest at step 5 (5.8 business days down to about 1.9 business days), the typical for all cases would move from 9.2 business days to about 8 business days.
The number, split by Repeat visit
Cause
Repeat visit
Groups
no (297), yes (63)
Chance reading
The gaps are bigger than chance gives.
Same axis
Every line below runs on one axis, so the groups can be compared.
Each dot
One case, placed by how long it took.
Thick part
The middle half of the cases.
Tick
The median, the typical case.
Ringed dots
Cases far out from the rest.
Red line
The promise.
This split
Repeat visit separates the cases by more than chance would.
The gaps are about what chance alone gives in a file this size.
Same axis
Every line below runs on one axis, so the groups can be compared.
Each dot
One case, placed by how long it took.
Thick part
The middle half of the cases.
Tick
The median, the typical case.
Ringed dots
Cases far out from the rest.
Red line
The promise.
This split
The gaps between Fault type groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Fault type matters.
No heating 121 cases · typical 10.6 business days
Leak 103 cases · typical 8.1 business days
Appliance fault 70 cases · typical 9.4 business days
Electrical fault 66 cases · typical 8.6 business days
The gaps are about what chance alone gives in a file this size.
Same axis
Every line below runs on one axis, so the groups can be compared.
Each dot
One case, placed by how long it took.
Thick part
The middle half of the cases.
Tick
The median, the typical case.
Ringed dots
Cases far out from the rest.
Red line
The promise.
This split
The gaps between Branch groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Branch matters.
Quayside 98 cases · typical 9.8 business days
Eastgate 96 cases · typical 10.5 business days
Northfield 91 cases · typical 8.6 business days
Millbrook 75 cases · typical 8.9 business days
The number, split by Engineer team
Cause
Engineer team
Groups
Team A (127), Team B (121), Team C (112)
Chance reading
The gaps are about what chance alone gives in a file this size.
Same axis
Every line below runs on one axis, so the groups can be compared.
Each dot
One case, placed by how long it took.
Thick part
The middle half of the cases.
Tick
The median, the typical case.
Ringed dots
Cases far out from the rest.
Red line
The promise.
This split
The gaps between Engineer team groups are about what chance alone would produce in a file this size, so they are drawn muted: nothing here says Engineer team matters.
Team A 127 cases · typical 8.7 business days
Team B 121 cases · typical 9.5 business days
Team C 112 cases · typical 9.3 business days
Parts needed
This is the clearest difference the file shows. Each bar is the typical time (the middle case) for that group.
The file shows the difference, not the reason — your coach will help you check why.
This finding is on: Days to fix by parts needed.
yes255 rows
11.2 working hours
no105 rows
5.5 working hours
Rows with parts needed took about 6 working hours longer.
The board below is the same real cases with your changes applied.
To change a step
Turn a card on the lower board and set what changes there.
Today
Start to finishtypical 9.2 business days · most 6.3–12.2 business days
Columns
from “Reported” to “Fixed”
Cases counted
360
Calendar
(business days: 8-hour days, 5-day weeks)
How worked out
Typical is the middle case of those counted; “most” is the middle half of them, with the fastest and slowest tails left out.
1
A customer reports a fault
30 min typical
10 min1.5 h
about 1% of the typical time
1A customer reports a fault30 min
2
The fault is triaged and a visit booked
1 business day typical
2 h3 business days
about 11% of the typical time
2The fault is triaged and a visit booked1 business day
3
The engineer visits and diagnoses
2 business days typical
1 business day5 business days
about 22% of the typical time
3The engineer visits and diagnoses2 business days
4
The parts are ordered from the regional depot
1 business day typical
2 h2 business days
about 11% of the typical time
4The parts are ordered from the regional depot1 business day
5
The parts arrive
3 business days typical
1 business day10 business days
about 33% of the typical time
5The parts arrive3 business days
6
The repair is made
1 business day typical
2 h3 business days
about 11% of the typical time
6The repair is made1 business day
7
The repair is checked
1 h typical
20 min3 h
↺ goes back to step 3
about 1% of the typical time
7The repair is checked1 h
8
The customer confirms it is fixed
1 business day typical
2 h3 business days
about 11% of the typical time
8The customer confirms it is fixed1 business day
Start from an idea on your shortlist
a strong fit with what you have recorded
a fit worth taking seriously
a fit worth taking seriously
may still fit
may still fit
may still fit
With your changes
Start to finishtypical 8.2 business days · most 6.3–9.2 business days
Columns
from “Reported” to “Fixed”
Cases counted
360
Calendar
(business days: 8-hour days, 5-day weeks)
How worked out
Typical is the middle case of those counted; “most” is the middle half of them, with the fastest and slowest tails left out.
1
A customer reports a fault
30 min typical
10 min1.5 h
about 1% of the typical time
1
A customer reports a fault
Settings for this step
Why we ask. Every setting in a change (how much it helps, how many will use it) should say whether it comes from your file, from fixes made elsewhere or from your own estimate. When. Your coach shows the source beside each setting and asks you to confirm or correct the ones that are only a guess.
hours
today 30 min
%
no figure for this
%
until you say, 70% is assumed
hours
a warning only
1A customer reports a fault30 min
2
The fault is triaged and a visit booked
1 business day typical
2 h3 business days
about 12% of the typical time
2
The fault is triaged and a visit booked
Settings for this step
Why we ask. Every setting in a change (how much it helps, how many will use it) should say whether it comes from your file, from fixes made elsewhere or from your own estimate. When. Your coach shows the source beside each setting and asks you to confirm or correct the ones that are only a guess.
hours
today 1 business day
%
no figure for this
%
until you say, 70% is assumed
hours
a warning only
2The fault is triaged and a visit booked1 business day
3
The engineer visits and diagnoses
2 business days typical
1 business day5 business days
about 23% of the typical time
3
The engineer visits and diagnoses
Settings for this step
Why we ask. Every setting in a change (how much it helps, how many will use it) should say whether it comes from your file, from fixes made elsewhere or from your own estimate. When. Your coach shows the source beside each setting and asks you to confirm or correct the ones that are only a guess.
hours
today 2 business days
%
no figure for this
%
until you say, 70% is assumed
hours
a warning only
3The engineer visits and diagnoses2 business days
4
The parts are ordered from the regional depot
1 business day typical
2 h2 business days
about 12% of the typical time
4
The parts are ordered from the regional depot
Settings for this step
Why we ask. Every setting in a change (how much it helps, how many will use it) should say whether it comes from your file, from fixes made elsewhere or from your own estimate. When. Your coach shows the source beside each setting and asks you to confirm or correct the ones that are only a guess.
hours
today 1 business day
%
no figure for this
%
until you say, 70% is assumed
hours
a warning only
4The parts are ordered from the regional depot1 business day
5
The parts arrive
2.3 business days typical
1.1 business days3.8 business days
about 28% of the typical time
5
The parts arrive
Settings for this step
Why we ask. Every setting in a change (how much it helps, how many will use it) should say whether it comes from your file, from fixes made elsewhere or from your own estimate. When. Your coach shows the source beside each setting and asks you to confirm or correct the ones that are only a guess.
hours
Comes from
your guess
Graded
Saved as your estimate and checked against what the trial finds.
today 2.3 business days
%
no figure for this
%
Comes from
your guess
Graded
Saved as your estimate and checked against what the trial finds.
until you say, 70% is assumed
hours
a warning only
5The parts arrive2.3 business days
6
The repair is made
1 business day typical
2 h3 business days
about 12% of the typical time
6
The repair is made
Settings for this step
Why we ask. Every setting in a change (how much it helps, how many will use it) should say whether it comes from your file, from fixes made elsewhere or from your own estimate. When. Your coach shows the source beside each setting and asks you to confirm or correct the ones that are only a guess.
hours
today 1 business day
%
no figure for this
%
until you say, 70% is assumed
hours
a warning only
6The repair is made1 business day
7
The repair is checked
1 h typical
20 min3 h
↺ goes back to step 3
about 2% of the typical time
7
The repair is checked
Settings for this step
Why we ask. Every setting in a change (how much it helps, how many will use it) should say whether it comes from your file, from fixes made elsewhere or from your own estimate. When. Your coach shows the source beside each setting and asks you to confirm or correct the ones that are only a guess.
hours
today 1 h
%
no figure for this
%
until you say, 70% is assumed
hours
a warning only
7The repair is checked1 h
8
The customer confirms it is fixed
1 business day typical
2 h3 business days
about 12% of the typical time
8
The customer confirms it is fixed
Settings for this step
Why we ask. Every setting in a change (how much it helps, how many will use it) should say whether it comes from your file, from fixes made elsewhere or from your own estimate. When. Your coach shows the source beside each setting and asks you to confirm or correct the ones that are only a guess.
hours
today 1 business day
%
no figure for this
%
until you say, 70% is assumed
hours
a warning only
8The customer confirms it is fixed1 business day
What it would do
The lowest that still keeps the promise—
No promise is stated, so there is nothing to keep yet.
Your settings8.2 days
Start to finish, the middle case takes 65.667 hours with your settings, against 73.25 hours today.
The most to hope for7.7 days
Start to finish, the middle case would take about 61.55 hours if every case followed the new way at the pace of your quickest tenth, with nothing going back round.
What this rests on
Time held at “The parts arrive”: 8 hours, your guess
Adoption at “The parts arrive”: 65%, your guess
The promise counts as kept when 90% of cases meet it, your guess (change it above)
Kept
Kept since 2026-09-14. eXecute is reading it week by week.
These are the ways a process can be made better that still fit what you have recorded, and the ones we have set aside, each with the reason. Nothing here is a promise of a result. Anything can be reopened.
What still fits
Get ready before the work arrivesa strong fit with what you have recorded
Set up or automate in advance so work is faster when it arrives
The Dig points to this pattern: the work waits for materials, people or information that could have been fetched before it started.
The Dig points to this pattern: steps run serially by convention though no true dependency exists between them.
Do steps at the same timea fit worth taking seriously
Do two or more things at the same time instead of sequentially
The Dig points to this pattern: steps run serially by convention though no true dependency exists between them.
Work in planned batchesa fit worth taking seriously
Switch from constant processing to planned cycles or grouped runs
The Dig points to this pattern: work is held and released in planned cycles where the batch serves setup economics; the window itself creates queues.
The Dig points to this pattern: the work waits for materials, people or information that could have been fetched before it started.
Set aside, and why
The change and the trial
The next review
Monday 16 November
Service operations lead · Every Monday the service lead reads the week's file and the two causes watched
12 Aug · the change and the trial
your words
Engineers carry the commonest parts in the van and order the rest only once the fault is diagnosed, so fewer repairs wait for the depot
the change is made here: Engineers carry the commonest parts in the van and order the rest only once the fault is diagnosed, so fewer repairs wait for the depot
The repair is made
The repair is checked
The customer confirms it is fixed
a scenario · dealt 12 Aug
where on the map
Idea “Parts in the van”. At “The parts arrive”: hold cases at “The parts arrive” for 8 hours (your guess); 65% follow the new way (your guess) · at The parts arrive
The change asked about
Idea “Parts in the van”. At “The parts arrive”: hold cases at “The parts arrive” for 8 hours (your guess); 65% follow the new way (your guess) (in your words)
Based on
not recorded
What it shows
no figure
The donors
not recorded
This one was dealt by an older engine (unversioned); asking the same question again deals it on the current one and keeps this one.
interim · direction to watch · covers the agreed period
7 business days· weeks 1 to 4 · covers the agreed period · entered 14 Sept · weeks 1 to 4 after the change
What the result says
Median business days for faults closed in the week over 4 weeks: 7 business days against a starting figure of 9.3 business days (the file) since 14 August 2026.
Execution not yet noted.
Comparison: the four full weeks before. It can show: whether the figure after the change is different from the figure before it. It cannot show: that the change caused it: anything else that changed over the same weeks (volume, staffing, the season) is in the result too.
What this trial can support: that the figure moved as reported over the agreed period, under the comparison designed. What it cannot: that the change caused the movement on its own. The comparison's own limits apply: anything else that changed over the same weeks (volume, staffing, the season) is in the result too. Execution not yet noted leaves the part the change did not reach open.
You decided: Keep it· 14 Sept
Kept on the record
Result 7.0 business days against 9.3 business days; no expectation recorded. · no expectation recorded
Follow-up: Service operations lead keeps “Every Monday the service lead reads the week's file and the two causes watched”; looked at again Monday 16 November; if it slips: Look first at whether parts orders are going in before the depot's cut-off; keep an eye on Parts orders in before the depot cut-off, Repeat visits.
EARLY WARNINGThe number is steady, but Parts orders in before the depot cut-off has moved outside its usual range. Look at it before the number follows.Driven by: the cause “Parts orders in before the depot cut-off”
The number
Steady · Within the usual wobble, inside the goal you set
The last 8 weeks have stayed within the usual wobble around 6.95 business days; nothing needs a reaction. 2% of the latest 4 weeks went past the promise (8 business days), inside the 20% you said is good enough.
Leave it alone. Reacting to the usual wobble makes the process worse, not better.
The causes you watch
Parts orders in before the depot cut-off
Latest week
61
Kept range
77 to 80 (from the first 4 weeks)
Weeks read
8
How it is seen
the share of parts orders placed before the depot's cut-off, in %
The latest week (61) is outside its kept range (77 to 80).
Something changed kept range 77 to 80
Repeat visits
Latest week
11
Kept range
10 to 12 (from the first 4 weeks)
Weeks read
8
How it is seen
the share of repairs that needed a second visit, in %
The latest week (11) is inside its kept range (10 to 12): usual wobble, do nothing.
Usual wobble, do nothing kept range 10 to 12
The number has not moved, so no new Dig is needed.
Start to finishtypical 9.2 business days · most 6.3–12.2 business days
Columns
from “Reported” to “Fixed”
Cases counted
360
Calendar
(business days: 8-hour days, 5-day weeks)
How worked out
Typical is the middle case of those counted; “most” is the middle half of them, with the fastest and slowest tails left out.
1
A customer reports a fault
30 min typical
10 min1.5 h
about 1% of the typical time
1A customer reports a fault30 min
2
The fault is triaged and a visit booked
1 business day typical
2 h3 business days
about 11% of the typical time
2The fault is triaged and a visit booked1 business day
3
The engineer visits and diagnoses
2 business days typical
1 business day5 business days
about 22% of the typical time
3The engineer visits and diagnoses2 business days
4
The parts are ordered from the regional depot
1 business day typical
2 h2 business days
about 11% of the typical time
4The parts are ordered from the regional depot1 business day
5
The parts arrive
3 business days typical
1 business day10 business days
about 33% of the typical time
5The parts arrive3 business days
6
The repair is made
1 business day typical
2 h3 business days
about 11% of the typical time
6The repair is made1 business day
7
The repair is checked
1 h typical
20 min3 h
↺ goes back to step 3
about 1% of the typical time
7The repair is checked1 h
8
The customer confirms it is fixed
1 business day typical
2 h3 business days
about 11% of the typical time
8The customer confirms it is fixed1 business day
The log
empty
What happened that the figures cannot say by themselves, what was different when the weather changed, what was done about it, and the decisions you took. Nothing here is rewritten: a correction is a new entry that says which one it replaces.
Nothing is written in the log yet.
The plan we are keeping
draft from the record · 2 gaps
Drawn from what is on the record, nothing typed twice. Every line says where it comes from. “You wrote” is yours: the coach may add beside it and never over it.
What changed
StepThe parts arrive · Regional depot · from your map
The changeEngineers carry the commonest parts in the van and order the rest only once the fault is diagnosed, so fewer repairs wait for the depot · you wrote
InstructionEvery Monday the service lead reads the week's file and the two causes watched · existing plan; origin not recorded
Whyshare not measured
Who holds it
OwnerService operations lead · existing plan; origin not recorded
Backupnot yet said
ReviewMonday 16 November · existing plan; origin not recorded
The two looks+3 months look 14 Nov 2026 · +12 months look 14 Aug 2027 · counted from your decision to keep, 14 SeptA reminder is not built yet; these are the days to look at the numbers yourself.
When coaching endsnot yet said
What we watch
The measureTime to fix a fault · A customer reports a fault → The customer confirms it is fixed · business days · from your ruling, 11 Aug
Where it is readcolumn “Days to fix” of your file · from your ruling, 11 Aug
Also watchedParts orders in before the depot cut-off · seen by the share of parts orders placed before the depot's cut-off, in % · share not measured · from the trial
Also watchedRepeat visits · seen by the share of repairs that needed a second visit, in % · share not measured · from the trial
What is good enoughno more than 1 in 5 faults past 8 business days · read as: no more than 20% past the promise · existing plan; origin not recorded
How often a new file comesevery week · existing plan; origin not recorded
If it slips
What we doLook first at whether parts orders are going in before the depot's cut-off · existing plan; origin not recorded
Pick one thing that could go wrong. Your plan, and what you have learned along the way, is walked through it: who would notice, who would act, how they would know. Where the plan says nothing, the table says so. Nothing is made up.
Attach the next extract of the same data. It is read the same way as the first, checked against what you are already watching, and nothing is added until you say so.
What we hold: 4 weeks from before the change, kept as history; 8 weeks since, read from your files; the newest is the week of 5 Oct 2026.
The result recorded for your change, its follow-up and the run chart are shown with the trial above. Go to the recorded result
The map and the file · 4
10 Aug · measure
A calculation
What you have told us, grouped by what each statement meant
“The time that matters is from the fault being reported to the customer confirming it is fixed”
the measure: Days to fix
typed by you in the notebook
What the file points at · 4
11 Aug · the dig
example:harbour-faults.csv
The Dig
11 Aug · the dig
example:harbour-faults.csv · 360 of 360 cases
The whole: every case of Days to fix, before any split
Half your cases are at or below 9.2. The highest tenth are 14 or more.
The smallest move a trial could see, at about 72 cases a week: 1 over 6 weeks, 1 over 12 weeks, 1 over 26 weeks.
11 Aug · the dig
example:harbour-faults.csv · 360 of 360 cases
What goes with Days to fix
By Parts ordered before cut-off, no (154 rows) typically runs at 12.5 working hours, compared with 8.5 working hours for the other 101 rows.
This is the clearest difference in this file. The file does not say why.
A look: the groups barely overlap — worth establishing what this column is before reading it as a cause.
no154 rows · middle half 11.5 working hours to 13.9 working hours
12.5 working hours
yes101 rows · middle half 8 working hours to 9.2 working hours
8.5 working hours
Parts ordered before cut-offa look: the groups barely overlap — worth establishing what this column is before reading it as a cause
39.9% of the spread
Parts neededa look: the groups barely overlap — worth establishing what this column is before reading it as a cause
56.8% of the spread
Repeat visitno vs the rest
7.5% of the spread
Fault typeNo heating vs the rest
8.9% of the spread
BranchEastgate vs the rest
5.1% of the spread
Engineer teamTeam A vs the rest
1% of the spread
Each share is a first reading of this file. To compare a different factor, use “Compare groups” above.
11 Aug · the dig · the column comparison
example:harbour-faults.csv · 360 of 360 cases
The column comparison: what goes with Days to fix
Which factors go with Days to fix, and is your file big enough to show each one?
By Parts needed, yes typically runs at 11.2 working hours, compared with 5.5 working hours for no (255 and 105 cases). This is a difference worth investigating; the file does not say why.
Parts neededthe groups barely overlap — worth establishing what this column is before reading it as a cause
56.8%
Parts ordered before cut-offthe groups barely overlap — worth establishing what this column is before reading it as a cause
39.9%
Fault typeNo heating vs the rest
8.9%
Repeat visitno vs the rest
7.5%
BranchEastgate vs the rest
5.1%
Engineer teamTeam A vs the rest
1%
The dashed line is 14.7%, the largest share of the spread that shuffled labels reached for any one of the 6 factors: one reference for the whole file, not a verdict on a bar. Each factor’s own shuffles are under How we checked this. Each share is a first reading of this file.
The factor Parts needed accounts for 56.8% of the spread; matched shuffled labels on the same cases reached up to 12.8% (across all 6 factors the largest share any shuffle reached is 14.7%, a different reference).
The factors together 2 factors taken together (Parts ordered before cut-off, Repeat visit) account for 53.9% of the spread once matched shuffled labels on the same groups are taken off (57% raw, 3.1% by chance alone).
What is left 44.3% of the spread is not accounted for by anything in this file, with 1 factor taken together: 43.2% before the chance line for those groups together (1.1%), which is a different line from the 14.7% line each single factor is read against.
Exploratory readings of this file, not causes.
What the file shows together is not yet a cause: you rule on which to take forward.
An example
When you are ready, start with your own process: the coach works alongside you.