Skip to content

Field guide 09 · Evidence & discovery · 3 min read

Capture a workflow with a clear purpose.

Record enough context to understand the work while controlling what enters the evidence pack.

What you’ll leave with

A bounded recording or walkthrough with useful steps, context and a review before sharing.

ProcessScout / TransformReal product · fictional data
Walkthroughs, documents and spreadsheets kept together as sources (ProcessScout Transform, fictional data)
Walkthroughs, documents and spreadsheets kept together as sources · fictional data

A recording can make an ordinary workflow much easier to explain. It can also capture more than the reviewer needs: unrelated tabs, notifications, customer details or credentials. Plan the capture around the question you are investigating. A short, purposeful walkthrough is often more useful than a long recording with no clear boundary.

01

Prepare a representative example.

Choose the task and the start and finish you want to demonstrate. Use a test or demonstration account with suitable example data when that can represent the work accurately. If real records are needed, follow your organization’s rules for access, recording, storage and sharing before you begin.

Close unrelated windows and tabs, reduce unexpected notifications and check what is visible on screen. Avoid exposing passwords, tokens or other secrets. Decide how you will handle a step that needs sensitive information: pause, use a prepared example or document the rule separately.

02

Explain the decisions around the clicks.

A sequence of clicks does not fully explain a process. State what starts the task, what information you need, how you decide the next action and what makes the work complete. Name the role performing the task and the role that receives its output.

Mention the checks that are easy to miss on screen. An operator may recognize an exception from experience, compare a value with another source or decide when to ask for approval. Capture that context without presenting one person’s practice as the agreed organization-wide rule.

  1. 01Prepare a safe exampleA demonstration record, the sites you allow and unrelated tabs closed.
  2. 02Narrate the decisionsWhat starts the task, what you check and why work goes back.
  3. 03Review before sharingWatch it through, remove what isn’t needed and name an owner.
Illustration · three moments that keep a capture useful
03

Capture the normal path and a useful exception.

Begin with a normal case so the reviewer can understand the basic route. Then choose an exception that changes the flow: missing information, an approval threshold or an unavailable system. Keep the recordings separate if that makes the sequence easier to follow.

Label what the example represents and what it leaves out. A demonstration is evidence of a particular walkthrough, not proof of how frequently an exception occurs. Use records or a defined sample to estimate frequency, and keep that analysis separate from the captured procedure.

04

Review the evidence before sharing it.

Watch the recording or inspect the captured steps before distributing them. Remove or replace material that is unnecessary for the purpose, using the tools and process your organization permits. Check captions, step labels and generated explanations for accuracy, particularly around decisions and exceptions.

Give the evidence a descriptive name, owner, date and scope. Link it to the finding, map or procedure it supports. Agree who can access it and when it should be reviewed or retired. A useful recording stays connected to the work instead of becoming another unowned file.

A recorded browser walkthrough with every piece of screen content obscured
Example walkthrough · screen content obscured before sharing

Fictional working example

A five-minute walkthrough with a precise question

Northstar wants to understand why a handoff returns to Sales. An operator records a demonstration case from request opening to the readiness decision, explains the missing scope rule and shows the return reason. The recording uses fictional client details. A separate case extract will establish how often returns happen. The walkthrough explains the mechanism; the records support the frequency claim.

Purpose
Explain the readiness decision
Capture
One normal case and one missing-scope case
Review
Accuracy, unnecessary data and access

Bring this to the review

A practical checklist.

  • The capture has a defined purpose and boundary.
  • The example and recording permissions are appropriate.
  • Unrelated information and secrets are kept out.
  • Decision rules and exceptions are explained.
  • The recording is reviewed and assigned an owner before sharing.

In ProcessScout

The ProcessScout recorder provides a focused entry point for documenting work. The free plan includes 25 recordings of up to 15 minutes. For supported files that need anonymization before use, the separate redaction tool runs locally in the browser; always inspect its output before relying on it.

Product view

ProcessScout interactive demo · Fictional Northstar data