← All articles

Workflow analysis

Describe the Workflow You Can See—Not the Gaps You Have to Guess

When evidence is incomplete, narrow the workflow description instead of filling in missing steps. Separate what was recorded from what you infer and what still needs checking.

Text-free Shadow evidence-map composition with connected document and task shapes, open gaps, and branching paths in ink black, warm cream, mustard gold, and muted sage.

A gap is a limit on the claim

A workflow description can sound complete even when the captured evidence is not. A handoff may be missing, a batch may begin after work has started, or the recorded sequence may end before the outcome is visible. In those cases, describe the part the evidence supports. Do not turn a missing step into an assumed one.

For example, if a captured attempt shows a request being reviewed and later shows a result being sent, it supports those observed events. Unless the evidence connects them, it does not establish every action between review and sending.

Keep observation, interpretation, and planning separate

Use three distinct layers when writing about a workflow. First, state the recorded evidence and link it to its source. Next, offer an interpretation, clearly labeled as such. Finally, identify planning assumptions or questions that need confirmation.

A citation shows where a statement came from; it does not prove that the interpretation is complete or certain. Phrasing such as “the captured batch shows” or “this may indicate” makes the boundary visible and gives readers a way to check the claim.

  • Recorded: what the evidence directly shows.
  • Interpretation: a plausible explanation of the recorded events.
  • Planning assumption: a condition to test before changing the workflow.

Compare attempts without smoothing over differences

Shadow reconstructs evidence-linked attempts at business outcomes from captured batches. Comparing distinct attempts can reveal recurring workflow patterns, but variation matters too. If one attempt includes an approval and another does not, report that difference rather than presenting approval as a universal step.

Describe a recurring pattern at the level the evidence supports: for example, “In these attempts, requests were reviewed before results were sent.” Avoid turning a pattern in the captured attempts into a claim about every case or the whole operation.

Treat app and site sequences as discovery signals

An app or site sequence can suggest where to look for more evidence, but it is not, by itself, a complete account of business work. A sequence may reflect navigation without showing the purpose, decision, handoff, or outcome associated with it.

Keep these sequences separate from evidence-linked attempts. Use them to formulate questions—such as whether a particular step belongs in the process description—not as proof that the step happened in every attempt.

Write the next version with its limits visible

A useful workflow description says what is known, names what is missing, and identifies what would resolve the uncertainty. This gives operations leaders a practical basis for review without disguising gaps as established process.

Before using a description to plan a change, check whether the captured attempts cover the cases that matter. If they do not, mark the open question and gather or review additional evidence. A narrower, qualified description is more useful than a smooth story that the record cannot support.