← All articles

Operations

Describe the Workflow You Can Evidence, Not the One You Assume

Collection gaps should narrow a workflow description, not disappear inside a confident summary. Separate what was captured from what it may mean and what still needs to be checked.

Text-free Shadow evidence-map composition with ink black paths, warm cream background, mustard gold markers, and muted sage blocks

A gap changes the claim

A workflow description is only as strong as the evidence behind it. If a collection captures an intake form, a review page, and a final record—but not the handoff between them—describe those observed steps without presenting the handoff as established fact.

This does not make the analysis less useful. It makes the boundary clear. Operations leaders can see which parts of the process are evidenced, which connections are inferred, and where another collection would resolve an important question.

  • Recorded evidence: the pages, files, or actions present in the captured batch.
  • Interpretation: a reasonable explanation of how those items may relate.
  • Planning assumption: a proposed step or dependency that still needs confirmation.

Use batches to reconstruct attempts

A captured batch can show an attempt at a business outcome: preparing a request, checking supporting information, or updating a record. Reconstruct the sequence only as far as the batch supports it. If the beginning or end is missing, mark the attempt as partial rather than filling the gap with a standard operating procedure.

This approach also keeps separate attempts distinct. Two batches may concern the same kind of request while following different paths. Comparing them can reveal recurring workflow patterns—such as a repeated review before an update—without claiming that every case follows that pattern.

Keep discovery signals in their place

App and site sequences can help identify where work may have been explored or routed. They are discovery signals, not a complete account of the business process. A sequence of visits may indicate that someone looked for information, but it does not establish why they did so, whether the information was used, or whether the task was completed.

Treat citations the same way. A citation proves where an observation came from. It does not prove the interpretation attached to that observation. Link claims to their source, then state the remaining uncertainty plainly.

Write the next review around the gap

The most useful workflow description ends with a focused question. For example: “The batch shows a request moving from intake to review, but the approval handoff was not captured.” That wording gives the next reviewer a concrete issue to investigate instead of inviting a broad search for anything that might be missing.

Planning can then stay proportional to the evidence. If the gap affects an important decision, collect or review the missing handoff. If it does not, record the limitation and proceed without turning an unverified step into a fact.

  • Name the missing segment.
  • Explain why it matters to the workflow description.
  • State what would confirm or revise the interpretation.
  • Keep the proposed next step separate from the recorded history.