A Rapid Insight Workshop is one session. By the end of it we need to understand a business well enough to say what to fix first and what it is worth. That only works because we are looking for specific things, and most of them are not on the agenda.
Here is what we are actually doing in the first couple of hours.
Getting the real process, not the official one
Every business has two versions of how work happens. The official one is in the induction pack. The real one has the workarounds in it.
So we do not ask how the process works. We ask someone to walk us through the last one they did, the actual job, with the actual dates. Specifics defeat the tidy version. That is where you hear the sentence we are always listening for: "and then I just export it and fix it in Excel."
Every one of those is a gap between two systems, and somebody is being paid to be the bridge.
Watching where the room disagrees
We want a few different roles present, and not only the leadership team, because the most useful moments are the disagreements.
Someone says approvals take a day. Someone else says three. Both are describing something true and the difference is usually a queue nobody has visibility of. Or two people give different definitions of a completed job, which means every report counting completed jobs has been answering two questions at once.
These moments are not conflict, they are the diagnosis. When the room agrees on everything, we are usually being shown the official process and we push harder.
Following the exceptions
Ask about the standard case and you learn the happy path. The happy path is rarely where the money goes.
So we ask what happens when a customer wants something slightly different, when a job gets cancelled after dispatch, when the numbers do not reconcile at month end. Exceptions are where the manual effort concentrates, and they are also the reason previous software failed, because it was built for the standard case and the standard case was sixty per cent of the work.
Finding who the business runs on
In most businesses there are one or two people who hold something critical in their heads. The pricing logic that was never written down. The knack for which supplier to call. The spreadsheet only they can maintain.
We find those people early, for two reasons. They know more about the operation than any document, and they are your single biggest risk. If one person going on leave slows the business down, that is worth fixing regardless of anything else we recommend.
Separating what hurts from what costs
The last thing, and the one that changes the outcome most. What annoys people and what costs money are different lists, and the annoying thing is always louder.
The clunky interface everyone complains about might cost a few minutes a day. The quoting process nobody mentions, because it has always been like that, might be losing real margin on every job. We chase both, then rank on cost and effort, not on volume of complaint.
Why it is one session
Because a long discovery phase changes what you learn. Give people three weeks and they prepare, tidy up and present the official process. One focused session with the right people in the room gets you the real thing, and the roadmap that comes out of it is built on how the business actually runs.
Not everything gets answered in a day. The point is not to specify the solution, it is to know which problem is worth solving and roughly what it is worth. That is enough to make the next decision properly.
