Making organisations
more productive.

01Observed problem

Some enquiries receive no reply at all, or a reply that arrives too late to matter. The customer hears nothing and takes the work elsewhere.

02Possible underlying bottleneck

Ownership gap: no one is accountable for the first responseThere is no single place that captures every enquiry, and no named person responsible for the first reply. Whoever happens to notice the message answers it. When nobody notices, the enquiry leaves no trace that it ever existed.

03Downstream effects

• Sales works on the leads someone remembered to pass on, not the leads that actually arrived.
• Management reporting understates real demand, because a missed enquiry is never recorded as a lost one.
• Response quality varies by channel and by who is on duty, so the customer experience is unpredictable.

04Evidence to investigate

• Every channel an enquiry can arrive through, and the real volume on each, compared with the leads actually recorded.
• Who checks each channel, how often, and what happens when they are busy or away.
• The time from arrival to first response, and how many enquiries receive no response at all.

05Potential intervention

Capture, owner and first responseA single capture point for every enquiry, with a named owner and a defined first-response step. This is the path the Lead Recovery System addresses. Its exact scope depends on the channels in use and what those channels allow.

An illustrative hypothesis, not a diagnosis. Establishing whether the suspected cause is real requires an engagement and investigation of your actual workflow.

01Observed problem

Quotes and enquiries are followed up sometimes, usually when one person remembers. The customer who was interested but not ready is rarely contacted again.

02Possible underlying bottleneck

Process failure: follow-up depends on memory, not a due dateFollow-up lives in individual habits rather than in a shared next action with a date and an owner. There is no single list of what is owed to which customer, so nothing can be chased when it slips.

03Downstream effects

• Revenue depends on which staff member happens to be handling the lead that week.
• Management cannot tell how much work is genuinely in the pipeline, only how much was remembered.
• Customers who were close to buying are never given the second contact that would have closed them.

04Evidence to investigate

• How follow-up dates and owners are recorded today, if at all, and where that record lives.
• The proportion of open quotes that have no scheduled next action.
• Whether follow-up behaviour differs by person, by channel or by type of request.

05Potential intervention

Follow-up queue with owners and due datesA follow-up queue where every open lead carries a named owner and a due next action, and where silence becomes visible rather than invisible. This may be a process change, an internal tool or an automation, depending on what the investigation shows.

An illustrative hypothesis, not a diagnosis. Establishing whether the suspected cause is real requires an engagement and investigation of your actual workflow.

01Observed problem

Staff copy the same details between tools, re-type records and chase routine updates by hand. Administration expands to fill the time available.

02Possible underlying bottleneck

Information gap: the same data is entered in more than one placeInformation is entered into several tools because those tools do not share it. The repetition is a symptom of duplication in the system, not of poor effort from the team.

03Downstream effects

• Time spent re-typing is time not spent on delivery, which caps how much work the team can take on.
• Every copy is an opportunity for an error, and errors are found later, by the customer.
• Volume grows faster than headcount, because each new job carries the same manual steps.

04Evidence to investigate

• Which records are entered more than once, and into precisely which tools.
• How long a routine job takes from start to finish, counted in steps rather than in impressions.
• Where errors are discovered, and how much work goes into correcting them.

05Potential intervention

Remove the duplication, not the effortA single shared record, an integration between the tools that support it, or a simple automation for the steps that never vary. Where a tool cannot be connected, that becomes a fact to weigh rather than something to hide.

An illustrative hypothesis, not a diagnosis. Establishing whether the suspected cause is real requires an engagement and investigation of your actual workflow.

01Observed problem

Work stalls between people or teams. A request sits because each side assumes the other has picked it up.

02Possible underlying bottleneck

Ownership gap: responsibility transfers by conversation, not by assignmentOwnership is implicit. When a job changes hands, the new owner is agreed in conversation rather than recorded as an assigned step, so the next action is neither clear nor traceable.

03Downstream effects

• Jobs sit idle while each party reasonably believes the other is handling them.
• Customers chase for updates the business did not know it owed.
• Delivery timelines reported to management drift away from what is actually happening.

04Evidence to investigate

• Where requests sit longest between stages, and who was nominally responsible at that point.
• How ownership changes hands, and whether that transfer is recorded anywhere at all.
• How often customers chase the business, and what they are chasing.

05Potential intervention

Explicit handoff with a named ownerA defined handoff step for each stage, carrying a named owner and the next action, so responsibility is assigned rather than assumed. The exact form follows from where the work actually stalls.

An illustrative hypothesis, not a diagnosis. Establishing whether the suspected cause is real requires an engagement and investigation of your actual workflow.

01Observed problem

Numbers reach management late, or are assembled by hand after the period has already closed.

02Possible underlying bottleneck

Process failure: the report is reconstructed, not observedReporting is rebuilt from source records at the end of a period, because no shared record is updated as the work happens. The report describes the past accurately and the present not at all.

03Downstream effects

• Decisions are made on information that is already out of date when it is read.
• Problems surface only after the month in which they occurred, when they are harder to fix.
• The team spends time producing the report instead of acting on it.

04Evidence to investigate

• How the current report is assembled, by whom, and from exactly which sources.
• How long after the period ends the numbers actually become available.
• Which decisions the report is supposed to inform, and whether it arrives in time to inform them.

05Potential intervention

Record as work happens, report as a viewUpdate the shared record as work happens, so the report becomes a view of current work rather than a reconstruction of past work. This usually reduces to an earlier change in the system, not a new dashboard.

An illustrative hypothesis, not a diagnosis. Establishing whether the suspected cause is real requires an engagement and investigation of your actual workflow.

01Observed problem

The tools do not talk to each other. The same customer exists in several places, in different states, and the truth is assembled in someone’s head.

02Possible underlying bottleneck

Information gap: there is no single source of truthEach tool holds a partial view of the business, and the join between those views happens mentally rather than in the system. Any report or decision inherits that uncertainty.

03Downstream effects

• Different people act on different versions of the same situation, and both are confident.
• Producing a report means reconciling sources by hand before any analysis can begin.
• Every new tool adds another island instead of closing the gap it was bought to close.

04Evidence to investigate

• Which systems hold customer or job records, and what each one actually knows about them.
• Where the same entity appears differently across tools, and which version the team treats as true.
• Which integrations exist today, as opposed to which ones are assumed to exist.

05Potential intervention

One source of truth, then connect or replaceDecide which system is the source of truth, then connect the others to it, or replace the tools that cannot be connected. This is an architecture decision made from evidence, and it protects every later build.

An illustrative hypothesis, not a diagnosis. Establishing whether the suspected cause is real requires an engagement and investigation of your actual workflow.