Good work, late follow-ups: requests lose their owner between the first reply and the last word.
An example project, made up to show the work, with made-up cases to replay. It shows Find (the Path) only: it has no file, so the Dig was not run on it, and Improve and eXecute have nothing to show; nothing here is yours.
The cases you can replay are made up for the example. Each moves through the steps at a pace drawn from the typical time on its card.
- 1
A request lands in the shared inbox
4 h typical
30 min8 habout 2% of the typical time
1A request lands in the shared inbox
Step nameA request lands in the shared inboxWhy 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 itStudio inboxWhy 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 whereA client email or web formWhy 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 whereto Whoever is free: The request, as writtenWhy 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 workNot collected yetWhy 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 yetWhy 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 4 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
- 30 min to 8 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 reworkNo 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 ofWhether 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 notedNot collected yetWhy 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.
FocusNot collected yetWhy 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.
- 2
Someone replies to say it was seen
8 h typical
1 h16 habout 5% of the typical time
2Someone replies to say it was seen
Step nameSomeone replies to say it was seenWhy 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 itWhoever is freeWhy 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 whereThe request, as writtenWhy 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 whereto The client: A short acknowledgementWhy 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 workHas to happenRead 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 yetWhy 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 8 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
- 1 h to 16 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 reworkNo 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 ofWhether 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 notedNot collected yetWhy 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.
FocusNot collected yetWhy 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.
- 3
The work is agreed and scoped
16 h typical
8 h1.3 daysabout 10% of the typical time
3The work is agreed and scoped
Step nameThe work is agreed and scopedWhy 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 itStudio leadWhy 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 whereThe acknowledged requestWhy 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 whereto The designer: A scoped jobWhy 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 workNot collected yetWhy 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 yetWhy 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 16 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
- 8 h to 1.3 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 reworkNo 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 ofWhether 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 notedNot collected yetWhy 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.
FocusNot collected yetWhy 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.
- 4
The job is designed and finished
1.3 days typical
16 h2.7 daysabout 20% of the typical time
4The job is designed and finished
Step nameThe job is designed and finishedWhy 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 itDesignerWhy 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 whereA scoped jobWhy 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 whereto The client: The finished workWhy 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 workWorth paying forRead 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 yetWhy 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.3 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
- 16 h to 2.7 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 reworkNo 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 ofWhether 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 notedNot collected yetWhy 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.
FocusNot collected yetWhy 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.
- 5
The client is sent the result
8 h typical
2 h16 habout 5% of the typical time
5The client is sent the result
Step nameThe client is sent the resultWhy 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 itDesignerWhy 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 whereNot collected yetWhy 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 whereto The client: The finished work, with a noteWhy 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 workNot collected yetWhy 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 yetWhy 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 8 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
- 2 h to 16 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 reworkNo 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 ofWhether 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 notedNot collected yetWhy 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.
FocusNot collected yetWhy 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.
- 6
A follow-up is meant to be sent
2.3 days typical
16 h5 daysabout 34% of the typical time
6A follow-up is meant to be sent
Step nameA follow-up is meant to be sentWhy 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 itNot collected yetWhy 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 whereNothing: nobody is named for thisWhy 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 whereNot collected yetWhy 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 workNot worth paying for · waitingRead 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 yetWhy 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.3 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
- 16 h to 5 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 reworkNo 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 ofWhether 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 notedNo one is named as the owner of the follow-up; It is remembered only when the client writes againWhy 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.
FocusNot collected yetWhy 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.
- 7
The client replies, or goes quiet
1.7 days typical
8 h4 daysabout 24% of the typical time
7The client replies, or goes quiet
Step nameThe client replies, or goes quietWhy 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 itThe clientWhy 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 whereNot collected yetWhy 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 whereNot collected yetWhy 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 workNot collected yetWhy 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 yetWhy 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.7 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
- 8 h to 4 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 reworkNo 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 ofWhether 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 notedNot collected yetWhy 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.
FocusNot collected yetWhy 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.
fix.lab · A hunch is something to test
The Dig
This example has no file of cases, so the Dig has nothing to compare. In your own project, bring a file and the Dig shows which causes separate the slow cases from the quick ones.
fix.lab · Fix the work, then automate it
Improve
- Today
- The board above is the process as it runs now.
- With your changes
- 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
- 1
A request lands in the shared inbox
4 h typical
30 min8 habout 2% of the typical time
- 2
Someone replies to say it was seen
8 h typical
1 h16 habout 5% of the typical time
- 3
The work is agreed and scoped
16 h typical
8 h1.3 daysabout 10% of the typical time
- 4
The job is designed and finished
1.3 days typical
16 h2.7 daysabout 20% of the typical time
- 5
The client is sent the result
8 h typical
2 h16 habout 5% of the typical time
- 6
A follow-up is meant to be sent
2.3 days typical
16 h5 daysabout 34% of the typical time
- 7
The client replies, or goes quiet
1.7 days typical
8 h4 daysabout 24% of the typical time
With your changes
- 1
A request lands in the shared inbox
4 h typical
30 min8 habout 2% of the typical time
1A request lands in the shared inbox
Settings for this stepWhy 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.
hourstoday 4 h%no figure for this%until you say, 70% is assumedhoursa warning only - 2
Someone replies to say it was seen
8 h typical
1 h16 habout 5% of the typical time
2Someone replies to say it was seen
Settings for this stepWhy 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.
hourstoday 8 h%no figure for this%until you say, 70% is assumedhoursa warning only - 3
The work is agreed and scoped
16 h typical
8 h1.3 daysabout 10% of the typical time
3The work is agreed and scoped
Settings for this stepWhy 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.
hourstoday 16 h%no figure for this%until you say, 70% is assumedhoursa warning only - 4
The job is designed and finished
1.3 days typical
16 h2.7 daysabout 20% of the typical time
4The job is designed and finished
Settings for this stepWhy 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.
hourstoday 1.3 days%no figure for this%until you say, 70% is assumedhoursa warning only - 5
The client is sent the result
8 h typical
2 h16 habout 5% of the typical time
5The client is sent the result
Settings for this stepWhy 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.
hourstoday 8 h%no figure for this%until you say, 70% is assumedhoursa warning only - 6
A follow-up is meant to be sent
2.3 days typical
16 h5 daysabout 34% of the typical time
6A follow-up is meant to be sent
Settings for this stepWhy 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.
hourstoday 2.3 days%no figure for this%until you say, 70% is assumedhoursa warning only - 7
The client replies, or goes quiet
1.7 days typical
8 h4 daysabout 24% of the typical time
7The client replies, or goes quiet
Settings for this stepWhy 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.
hourstoday 1.7 days%no figure for this%until you say, 70% is assumedhoursa warning only
What it would do
- The lowest that still keeps the promise—
No promise is stated, so there is nothing to keep yet.
- Your settings—
Choose a setting on the back of a card to see what it would do to the same cases.
- The most to hope for—
Start to finish, the middle case would take about a time we cannot say if every case followed the new way at the pace of your quickest tenth, with nothing going back round.
What this rests on
- The promise counts as kept when 90% of cases meet it, your guess (change it above)
This example has no chosen change, so Improve has nothing to try. In your own project, a change chosen from the Dig’s shortlist is tried here.
fix.lab · One number you can trust
eXecute
This example has no kept change, so there is nothing to keep working. In your own project, each week’s file is read here once a change is kept.