Key terms explained
A process canvas is an overview of the work you want to improve. Scope means where that work starts and ends. The process owner is the person responsible and authorised to make decisions about the process.
Start with a specific outcome
Describe what should be achieved and for whom. Recording an order differs from answering a customer question. Identify the problem you want to reduce: rekeying, waiting, unclear status or corrections. Use a process name that the people involved recognise.
Choose a beginning and an end
Record what starts the task and when it is genuinely complete. Identify the main handovers between those points. Note where someone searches for or copies information. You do not need a full process model; a traceable description of an ordinary case is a useful start.
Identify systems and information
List the applications and the data moving between steps. Describe categories rather than real customer records. Leave out passwords and access codes. Identify the authoritative source and the person who can resolve uncertainty about the content.
Distinguish observation from estimation
Record volumes and handling time with a period and source. Label estimates as estimates. Waiting for approval is not the same as active handling time. An open question is more useful than a precise-looking number without evidence.
Include an unusual case
Describe what happens when information is missing, a request arrives twice or processing provides no confirmation. Identify who takes over and what they need. The aim is to expose where judgement or additional agreements are required.
Finish with an open question
Name the person responsible for the process and the outcome that matters to them. Then choose a question to discuss, such as where time is lost or which handover deserves investigation first. The canvas does not have to be complete before that conversation can happen.
Start with a fictional process example
Open an example, review it and confirm before it replaces your canvas. Save your current answers first if you want to keep them. Adapt roles, systems and agreements with the process owner; the example is not an approved design.
Orders from email
From a fictional email to a confirmed test order. Includes a missing unit, repetition and an unknown outcome.
Download editable example file · Read the practice article · Trial log
Invoice processing
From a fictional invoice to a confirmed test posting. Approval and payment remain separate decisions.
Download editable example file · Read the practice article · Trial log
AI draft replies
Fictional product questions with source review and human takeover. Sending and commercial promises remain outside the trial.
Download editable example · Test source and instruction · AI reading guide
MFT chain trial: arrival, processing and recovery
Fictional chain K-01 with stage-specific evidence, partial processing and authorised recovery. A tabletop exercise, no live file transfer.
Editable example · Cases and instruction · MFT reading guide
Without JavaScript you can download the example files and use the paper canvas below. To edit an example here, enable JavaScript and use Open saved worksheet. Examples contain no real customer details.
From canvas to pilot preparation
The transfer uses boundaries for scope, roles for reviewers, systems and data categories as data context, exceptions for cases, and the desired outcome plus measurement context as a starting point for acceptance and measurement. It copies descriptions and next actions, never a canvas readiness status.
Access, stopping, recovery and operations remain unknown. Permission and concrete acceptance criteria still need review. No automatic storage or information in a web address is used.
Process, purpose and desired outcome
Beginning, end and main steps
Systems, data categories and authoritative source
Volume and active handling time: period, measured or estimated
Exceptions and current handling
Process owner, participants and open question
Record only necessary process information. Leave out personal data, passwords and confidential customer details.
What would you like to clarify?
Describe the process step or open question. We can explore a practical next step together.
Discuss your process