Find how work really happens.
Process discovery is the work of finding out how a process actually runs — not documenting the official procedure. This guide covers the evidence sources, the hidden handovers and exceptions, weak evidence and assumptions, a practical discovery sequence, and where discovery reaches its limits.
What is business process discovery?
Documentation records what you know. Discovery finds what you don't.
Asking an owner to “just draw it” assumes the process is already in their head, complete. For work that's distributed across people and exceptions, that produces the idealised version. Guided discovery asks one question at a time and builds the map from the answers — far closer to the truth.
Assumes you already know the process well enough to draw it — so you map the official version, not the real one.
Where does work most often get stuck or land back on your desk?
Asks one question at a time and builds the map from your answers — closer to how work actually happens.
Four sources of truth
Strong discovery ties every claim back to something specific. Four sources do most of the work:
Interviews
What people say, in their own words — the owner and the team who do the work. The richest source, and the one that surfaces the workarounds.
Systems
The tools work runs through — the accounting package, the job sheet, the shared inbox — which reveal where work lives and where it crosses.
Artefacts
The real objects of work: spreadsheets, WhatsApp threads, quote templates, job packs. They show the process as it's actually operated.
Team validation
Confirming the emerging map with the people who run it — which catches the difference between what one person believes and what really happens.
A good discovery is honest about what it doesn't know.
Not every claim is equally certain. The discipline is to name confidence and assumptions openly — so weak evidence becomes a follow-up question, not a fact quietly baked into the map.
- ✓Every claim carries the evidence it came from
- ✓Confidence is stated; assumptions are named, not hidden
- ✓Weak evidence triggers a question, not a guess
- ✕No fabricated certainty to make the map look finished
- ✕No hidden handover or exception left unmarked
- ✕No “that'll do” — unconfirmed steps stay flagged for review
How to actually do it
Start from the business, not the process
Capture what the business does, who's involved and what hurts most — so discovery follows the real pain, not a template.
Walk one real job end to end
From first contact to money in the bank, in the owner's words — including the messy bits. One real story reveals more than a form.
Surface the handovers and exceptions
Ask specifically where work moves between people and what happens when it's not standard. That's where the losses hide.
Attach evidence and confidence
Tie each step to a quote or artefact, and mark how sure you are. Weak spots become the next questions.
Validate with the team
Confirm the map with the people who run it — the step that turns one person's belief into a shared, trusted picture.
The limits are worth stating: discovery reflects what people can recall and are willing to share, and it captures a moment in time. That's why validation and treating the map as living matter — discovery is a strong start, not a one-off certainty.
Common questions
- What is business process discovery?
- Process discovery is the work of finding out how a process actually runs — surfacing the real steps, people, systems, handovers and exceptions — rather than writing down the procedure as it's supposed to work. Discovery precedes documentation: you can only document accurately what you've genuinely discovered.
- How is discovery different from documentation?
- Documentation records a process you already understand. Discovery uncovers one you don't — including the workarounds, the informal escalations, and the steps that only live in someone's head. Documenting without discovering first usually captures the official fiction, not the reality.
- What counts as evidence in process discovery?
- Evidence includes what people say in interviews, the systems and artefacts work passes through (spreadsheets, job sheets, emails), and — crucially — validation from the people who actually do the work. Strong discovery ties every claim back to a specific source.
- Why is asking an owner to “just draw it” a problem?
- Because for a process that grew organically, the owner often can't fully articulate it from memory — it's distributed across people and exceptions. A blank canvas produces the idealised version. Guided discovery asks one question at a time and builds the map from the answers, which is far closer to the truth.
- What are the limits of process discovery?
- Discovery reflects what people can recall and are willing to share, so it can miss things until validation surfaces them, and it captures a moment in time. That's why validation with the team and treating the map as living matter — discovery is a strong start, not a one-off certainty.
Discover your real process. One question at a time.
Veda Flow runs the discovery for you — guided, evidenced, validated. Your first map skeleton forms in minutes, no card required during early access.