← All articles

Operations

Let Collection Gaps Narrow the Workflow Story

When evidence is incomplete, describe what was captured, what it suggests, and what still needs validation—rather than turning missing steps into assumed process.

Text-free Shadow evidence-map composition with connected paper fragments and pathways in ink black, warm cream, mustard gold, and muted sage

A gap is part of the evidence

A workflow description is shaped not only by what a collection captures, but also by what it does not capture. A batch may show a request being reviewed and a record being updated without showing the handoff between them. That missing segment should remain visible in the description.

The practical rule is simple: do not use a gap as permission to write the most familiar version of the process. State the observed boundary, then explain what may connect it. This keeps the workflow useful without presenting an unrecorded step as fact.

  • Recorded evidence: “The request appears in the captured material, followed later by an updated record.”
  • Interpretation: “This may indicate a review or handoff between the two states.”
  • Planning assumption: “Confirm whether a person, queue, or system action connects them.”

Describe attempts, not an idealized process

A captured batch is best treated as evidence of a particular attempt at an outcome. One attempt may contain a visible exception, a skipped-looking step, or a different route from another attempt. Combining those attempts into one smooth sequence can hide the conditions under which the work changed.

Compare distinct attempts before naming a recurring workflow pattern. If the same transition appears across several evidence-linked attempts, it can support a stronger description of the pattern. If it appears only once, describe it as a local observation rather than a standard step.

  • Keep each attempt traceable to its captured evidence.
  • Separate repeated transitions from one-off details.
  • Use qualified language when the sample does not show whether a variation is normal, exceptional, or caused by a collection gap.

Keep app and site sequences in their place

A sequence of applications or sites can help identify where to investigate, but it does not by itself establish the business action taking place. The same application may support several workflows, and a workflow may move through tools that are not captured in the sequence.

Treat these sequences as discovery signals. Use them to ask better questions about a handoff, record change, or review point. Do not use them to fill an unobserved business step or to claim that a person completed a particular action.

  • Use an app or site sequence to locate a candidate area for review.
  • Look for corroborating evidence in the captured batch before describing a business transition.
  • Keep the tool path separate from the workflow narrative when the connection is uncertain.

Make uncertainty actionable

A useful workflow description does not need to eliminate every unknown. It needs to show which unknowns affect the next decision. Mark the missing evidence, explain why it matters, and define the smallest validation step that could distinguish between plausible explanations.

This also makes planning more disciplined. A proposed change can be based on an explicit assumption, while the recorded account remains unchanged. As new batches are captured, compare them with earlier attempts and update the pattern only when the evidence supports it.

  • Name the missing boundary: for example, intake to review, review to approval, or approval to update.
  • Record competing interpretations when more than one fits the evidence.
  • Treat citations as provenance for the material used, not as proof that an interpretation is certain.
  • Use a validation plan to test the gap rather than silently rewriting it.