← All articles

Operations

Before You Call Repeated Work a Pattern, Check the Evidence

A task that looks familiar may still be a different attempt. Compare evidence, outcomes, and context before treating repetition as a workflow pattern.

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

Start with distinct attempts

Seeing similar steps more than once is a reason to investigate, not proof of a standard workflow. First identify separate attempts at the same business outcome. Check that each attempt has its own captured batch and that the evidence belongs to the work you are comparing.

Then compare the attempts side by side. Look for steps that recur, steps that vary, and places where the available evidence stops. A shared outcome can involve different paths; a shared sequence can lead to different outcomes.

Check what the evidence actually supports

For each apparent common step, ask what was recorded and where it came from. A citation can help you trace a claim to its source. It proves provenance, not that the interpretation is correct or that the record tells the whole story.

Keep three things separate: recorded evidence, your interpretation of it, and any planning assumption. For example, a record may show that a particular form appeared in two attempts. Calling that form a required step is an interpretation that needs more checking.

Test for meaningful differences

Before describing a recurring pattern, look for differences that could change the process: the request type, starting conditions, exceptions, approvals, or final result. If those details are missing, mark the pattern as tentative rather than filling gaps with assumptions.

Use the comparison to describe what is common and what is not. A useful finding may be that two attempts share an early handoff but diverge later. That is more actionable than flattening both into one supposedly universal sequence.

Treat app and site sequences as discovery signals

A sequence of apps or sites can suggest where to look for a repeated workflow, but it does not establish the purpose of each visit or the business step it represents. Keep those sequences separate from evidence about the work outcome until you can connect them with relevant records.

When the evidence is incomplete, state what remains unknown and decide what would resolve it: another distinct attempt, a source record, or clarification from the people responsible for the process. The goal is a careful account of how work appears to happen, not a judgment about individuals or a claim that the record is complete.