METHODOLOGY STAGE 01

SCAN — Process Discovery & Opportunity Assessment

Help process owners and operations leaders choose which workflows deserve further assessment, using evidence about effort, exceptions and service needs.

Value to the engagement

A shortlist worth assessing

Who this helps

Process owners, operations leads and automation leads

SCAN: from starting evidence to a useful output
  1. BringProcess evidence

    Volumes, handling time, exceptions and interviews

  2. Work throughAssess the opportunity

    Map the work and compare candidate priorities

  3. Leave withA focused shortlist

    Owners, baseline assumptions and next questions

Why this stage matters

SCAN turns a broad request for automation into a defined set of candidate workflows. We map what people actually do, which systems they use and where work waits or needs correction.

The result is an opportunity assessment, with uncertainty recorded. A process may need simplification, better inputs or clearer ownership before technology is useful.

Who uses the output, and how

Operations lead
Compare candidate processes against effort, queue delays, quality and service priorities.
Process owner
Make handoffs, exceptions and missing information visible before committing team time.
Automation lead
Take a focused, evidenced shortlist into feasibility assessment.

How we establish the opportunity

  • Understand the work: Interview the people handling the process and map its trigger, end point, handoffs and normal and exception paths.
  • Build a usable baseline: Review available transaction counts, handling time, queue age and error records. Separate measured values from estimates and identify gaps.
  • Compare candidates: Consider potential capacity, quality and service value alongside stability, access constraints and business priorities. Assign a process owner to each candidate.

A shortlist is not build approval

SCAN identifies where to investigate. Technical feasibility, business-case assumptions and control requirements are tested during GATE.

Keep discovery connected to operations

The same intake can be reused as priorities change or production reveals new opportunities. Refresh candidate evidence and ownership before adding more work to the delivery backlog.

What you leave with

The assessment gives the business and automation team a common basis for selecting the next workflow:

Deliverables and acceptance criteria are confirmed in the engagement scope.

  • Prioritized opportunity backlog: Candidate workflows with owners, scope, reasons for priority and a recommended next assessment.
  • Process baseline and evidence register: Current effort, exceptions and service measures, with sources, assumptions and missing data made explicit.
  • Current workflow and constraint map: Key handoffs, system dependencies and known risks to investigate before design.
Illustrative application

Manufacturing invoice disputes

Starting situation: Several queues are proposed for automation, but their volumes and reasons for rework are unclear.

Useful output: Operations receives a shortlist with invoice and dispute boundaries, available baseline evidence and the questions to resolve before selecting a candidate.

An example of how the stage can be used, not a client result or a promised outcome.

Which candidates should move to GATE?

Take the prioritized processes and evidence gaps into feasibility assessment. Candidates can also be held or simplified first.

Explore GATE