← All articles

Operations

Compare the documented process with the evidence of how work unfolded

A procedure describes the intended route. Captured evidence can show how particular attempts unfolded. Compare them carefully, and treat recurring differences as questions to investigate—not proof that every case works the same way.

Text-free Shadow evidence-map composition in ink black, warm cream, mustard gold, and muted sage, with linked evidence points and branching paths.

Start with the procedure as a claim

Read the documented process as a description of the intended route: its steps, handoffs, decisions, and expected outcomes. Note what the procedure says should happen, and where it leaves room for judgment or variation.

Keep that description separate from captured evidence. A procedure is not proof that a step happened; a record of an attempt is not proof that the written procedure is wrong.

Compare complete attempts, not isolated moments

Review evidence-linked attempts from captured batches. For each attempt, trace the available sequence toward its business outcome, then compare it with the documented steps. Mark where the evidence supports a step, where it suggests a different route, and where the record is incomplete.

Use distinct attempts as separate comparisons. One unusual route may reflect a particular case or missing evidence. Similar differences across several attempts can reveal a recurring workflow pattern worth examining, but they do not establish that every case follows that pattern.

  • Separate documented steps from observed evidence and from your interpretation.
  • Record gaps and uncertain links instead of filling them with assumptions.

Treat differences as questions to check

A difference between the procedure and a captured attempt is a useful prompt: Is the written process out of date? Does the work vary by case? Is a handoff or decision missing from the documentation? Could the evidence be incomplete?

Keep the answer open until it has been checked with appropriate context. A citation establishes where a piece of evidence came from; it does not make the evidence complete or prove why a step occurred.

Keep discovery signals in their own lane

App and site sequences can help suggest where to look for a workflow or a missing documented step. Treat them as discovery signals, not as proof that a business step was completed or that a particular path represents the whole process.

When sharing a comparison, label recorded evidence, interpretation, and planning assumptions separately. Use the findings to decide what to verify or document next—not to claim certainty beyond the evidence.