← All articles

Process discovery

Start Process Discovery With a Task Outcome, Not an App

App activity shows where work may have happened. An evidence-linked task attempt connects a business outcome to the steps and records that can explain how it happened.

Text-free Shadow evidence-map composition in ink black, warm cream, mustard gold, and muted sage.

An app visit is a clue, not a process

A sequence of sites or apps can suggest where to investigate, but it does not say what business work was being done or whether it reached an outcome. The same app can support many tasks; one task can span several apps.

Treat app and site sequences as discovery signals. They can point to possible handoffs or tools to examine, but they are not a substitute for evidence tied to a specific business outcome.

Define the unit by the outcome

For process discovery, start with a task attempt: the work associated with an intended outcome, reconstructed from captured evidence. For example, follow an order change from the request to the recorded disposition, rather than counting visits to an inbox or order system.

Be precise about the word “completed.” Evidence may support that an outcome was recorded, but it cannot establish more than the records show. If the evidence is incomplete or ambiguous, describe the attempt that can be traced—not a verified end-to-end completion.

Compare distinct attempts to find recurring patterns

One attempt gives useful context; distinct attempts can reveal what recurs. Compare how different attempts reach similar outcomes: which steps appear repeatedly, where handoffs occur, and where the available records leave gaps.

Keep the comparison grounded in the evidence. A repeated sequence may be a candidate workflow pattern, not proof that every case follows it. Differences between attempts matter too: they can signal exceptions, alternative routes, or simply missing evidence.

Keep evidence, interpretation, and plans separate

Record what the captured material shows, then label interpretations as interpretations. Keep proposed process changes or assumptions about what should happen in the future separate again. This makes it easier for operations leaders to review the reasoning and challenge it when needed.

A citation shows where a claim came from; it does not make the claim certain. Use that distinction to discuss process design, not to score people or infer productivity, working time, or savings.