The work is faster. Why is the business still waiting?
Before adding another tool, follow one piece of work from the first request to a useful result.
Published . Updated .
A practical website edition developed from The Fast Worker, Slow Organisation by Sourabh Agarwal, ScaleOn Growth, first published .
Measure the journey before measuring the tool.
A faster draft is useful, but it answers only one question: how long did that task take? The buyer experiences the journey from request to a usable answer. That journey includes work, queues, review, corrections and the final commitment.
The Fast Worker, Slow Organisation explores this distinction. This companion guide gives you a small diagnostic you can use with existing records. It does not repeat the original article’s research claims or estimate a company-wide productivity gain.
Start with one recurring journey such as enquiry to usable quote. Define its start and finish before collecting times. “Draft complete”, “quote sent” and “buyer received a correct quote” are different finish points. Choose the one that answers your operating question and keep it consistent.
Separate four measures.
Elapsed time is the time from the agreed start to the agreed finish. Initial working time is active work that advances the item, including necessary review. Waiting time is time when the item is not being actively worked on. Rework is active time spent correcting or repeating earlier work.
Record rework separately from initial working time so it is visible and counted once. For a simple serial journey, elapsed time can be split into these non-overlapping intervals. In work that happens in parallel, elapsed time and total staff effort are different measures. Do not add overlapping people’s time and call it the buyer’s elapsed time.
Outcome quality sits alongside time, not inside the timing total. Did the answer meet the agreed requirement? Were its scope and commitments correct? Was it usable without another correction? A shorter journey that creates an unsafe or undeliverable promise is not an improvement.
A four-hour quote journey, shown honestly.
The timeline below is fictional and deliberately simple. It illustrates the calculation, not a ScaleOn engagement, a benchmark or an achieved result. Assume one quote moves through serial work between 09:00 and 13:00 on the same day.
During review, the team finds a scope omission. Correcting it takes fifteen minutes. That is rework. The review itself is initial working time because checking scope is part of the agreed process. The example does not prove that review is unnecessary.
At 13:00 the buyer receives the corrected quote. Its scope has been checked and an unverified delivery promise removed. That is the illustrative finish condition. It is not proof of buyer acceptance, revenue or commercial success.
| Interval | What happens | Classification and minutes |
|---|---|---|
| 09:00 to 09:30 | Enquiry waits for a named person to pick it up. | Waiting: 30 |
| 09:30 to 10:00 | The quote is prepared. | Initial work: 30 |
| 10:00 to 11:30 | Quote waits for the agreed review. | Waiting: 90 |
| 11:30 to 12:00 | Scope and commitments are reviewed. | Initial work: 30 |
| 12:00 to 12:15 | A missing scope item is corrected. | Rework: 15 |
| 12:15 to 12:30 | The correction and final quote are checked. | Initial work: 15 |
| 12:30 to 13:00 | The ready quote waits to be sent. | Waiting: 30 |
- Interval
- 09:00 to 09:30
- What happens
- Enquiry waits for a named person to pick it up.
- Classification and minutes
- Waiting: 30
- Interval
- 09:30 to 10:00
- What happens
- The quote is prepared.
- Classification and minutes
- Initial work: 30
- Interval
- 10:00 to 11:30
- What happens
- Quote waits for the agreed review.
- Classification and minutes
- Waiting: 90
- Interval
- 11:30 to 12:00
- What happens
- Scope and commitments are reviewed.
- Classification and minutes
- Initial work: 30
- Interval
- 12:00 to 12:15
- What happens
- A missing scope item is corrected.
- Classification and minutes
- Rework: 15
- Interval
- 12:15 to 12:30
- What happens
- The correction and final quote are checked.
- Classification and minutes
- Initial work: 15
- Interval
- 12:30 to 13:00
- What happens
- The ready quote waits to be sent.
- Classification and minutes
- Waiting: 30
Elapsed time: 240 minutes = initial work 75 + waiting 150 + rework 15. These are invented example values, not observed performance or a target.
Use the largest interval as a question, not a verdict.
In the example, the ninety-minute review queue deserves attention. It does not automatically deserve removal. Find out whether the reviewer was unavailable, the request was invisible, the quote lacked information or the agreed review time was appropriate.
The thirty-minute wait after the quote was ready raises a different question: who was responsible for sending it? Faster drafting would not resolve that responsibility gap. Removing review could meanwhile allow an incorrect commitment to reach the buyer.
Ask the people involved what the record cannot show. A timestamp tells you when something happened. It may not tell you why. Where a timestamp is missing, mark the interval unknown. Do not turn recollection into minute-level accuracy.
Keep a worksheet small enough to repeat.
Use a few comparable items to test whether the same constraint recurs. Include an ordinary item and one that needed correction. This is a diagnostic sample, not statistically representative research.
Record the agreed start and finish, the non-overlapping intervals, the handover owner and whether the result met the requirement. Keep evidence references in the authorised business system. Avoid copying customer or employee information into a new worksheet unless the question requires it.
Do not compare unlike journeys without explanation. A quote requiring specialist approval may properly take longer than a routine repeat order. The point is to understand the cause of delay and error, not to rank people by a single duration.
| Measure | Record | Question it supports |
|---|---|---|
| Elapsed time | Start event, finish event and timestamps | How long did the recipient wait for the agreed result? |
| Initial work | Active intervals, including necessary review | Where did useful work take place? |
| Waiting | Inactive intervals and known reasons | Which queue, missing information or unclear owner needs attention? |
| Rework | Correction intervals and the reason for each | What caused work to be repeated? |
| Outcome quality | Requirement met, correction needed or still unknown | Was the result usable and the commitment appropriate? |
| Next test | One change, owner and review point | What can we learn without changing the whole process? |
- Measure
- Elapsed time
- Record
- Start event, finish event and timestamps
- Question it supports
- How long did the recipient wait for the agreed result?
- Measure
- Initial work
- Record
- Active intervals, including necessary review
- Question it supports
- Where did useful work take place?
- Measure
- Waiting
- Record
- Inactive intervals and known reasons
- Question it supports
- Which queue, missing information or unclear owner needs attention?
- Measure
- Rework
- Record
- Correction intervals and the reason for each
- Question it supports
- What caused work to be repeated?
- Measure
- Outcome quality
- Record
- Requirement met, correction needed or still unknown
- Question it supports
- Was the result usable and the commitment appropriate?
- Measure
- Next test
- Record
- One change, owner and review point
- Question it supports
- What can we learn without changing the whole process?
Use consistent definitions. For parallel work, record elapsed time and staff effort separately rather than forcing them into this serial calculation.
Change one constraint and check the whole result.
A proportionate test might clarify who sends a ready quote, improve the information supplied for review or agree a review rhythm. Choose the change supported by the observed problem. Do not add software before you know what it needs to repair.
At the agreed review, compare elapsed time, waiting, rework and outcome quality using the same definitions. Record exceptions and changes in case difficulty. A quicker result with more corrections deserves another look.
ScaleOn connects Sales, People, Operations and Digital around that whole journey. The commercial question is whether the next person receives a usable result and knows what to do, while necessary judgement and controls remain intact.