01 / Section
Start with separate attempts
Seeing similar steps more than once can suggest a recurring workflow. But repetitions in one captured batch are not necessarily independent attempts. Before drawing a conclusion, identify the separate attempts and the business outcome each was meant to reach.
Compare like with like. If the intended outcome or the starting conditions differ, the sequence may not be comparable. Record those differences rather than smoothing them into a single account.
02 / Section
Check what the evidence actually shows
Review the captured evidence supporting each step and outcome. A citation helps you trace a claim back to its source; it does not prove that the interpretation is correct or that the evidence tells the whole story.
Separate recorded evidence from interpretation. For example, a captured page or action may show what appeared in that attempt. Calling it a required step, a cause of an outcome, or a reliable handoff is a further interpretation that needs support.
03 / Section
Look for variation before naming a pattern
Compare the attempts for both common steps and meaningful differences. Note skipped steps, different routes, changed inputs, and outcomes that do not match. A pattern should describe what recurs in the evidence, not erase exceptions that matter.
Keep app and site sequences separate as discovery signals. They can help point to areas worth examining, but a sequence across apps or sites does not by itself establish a business workflow or explain why someone used it.
04 / Section
State the conclusion at the right strength
Use a bounded claim: say which attempts were compared, what steps recurred, and where the evidence is incomplete or mixed. Avoid turning a small set of observations into a universal process description.
Keep planning assumptions visibly separate from findings. If you propose a change or a further check, label it as a next step to test—not as a result already established by the captured evidence.
