Name the trigger, end state, current bottleneck, and what stays outside scope.
02 / Owner and decision rights
Name the operating owner, access approver, reviewer, and release authority.
03 / Baseline and unknowns
Define the unit of work, period, records, comparison method, and missing evidence.
04 / Systems and dependencies
List source documents, authoritative systems, permissions, integrations, and people.
05 / Proposed change and acceptance
Define the change and the quality, review, adoption, and total-cost criteria needed before testing.
06 / Exceptions and fallback
State what is held, who resolves it, and how staff continue if the system fails.
07 / Next decision and evidence
Request a bounded decision. Name the evidence, owner, and conditions for the next stage.
Fictional completed example
Supplier invoice review at Example Co.
An illustrative planning exercise, not a Meru client engagement, measured outcome, or deployment recommendation. Example Co. and its circumstances are invented.
01 / Workflow and boundary
Example Co., a fictional distributor: from a supplier invoice received in the shared inbox to a reviewed accounts-payable entry. Staff currently reconcile invoice lines with purchase orders and receiving records. Payment authorization and supplier master changes remain outside scope.
02 / Owner and decision rights
The operations manager owns the workflow. IT approves access and integration. An accounts-payable reviewer checks each prepared entry; the finance lead accepts financial controls and any later release proposal.
03 / Baseline and unknowns
No baseline has been measured yet. Before testing, the owner will agree a representative period and record received invoices, completed entries, review and rework time, and exceptions. Invoice mix and review effort must remain visible in comparisons. No savings estimate is approved.
04 / Systems and dependencies
Inputs: invoice, purchase order, receiving record, and supplier master. The accounting system remains authoritative. Inbox access, document retention, API permissions, and source completeness need confirmation before a build is approved.
05 / Proposed change and acceptance
Prepare a source-linked entry for a reviewer, matching supplier, order, quantity, and amount to the records. Every proposed value must have a traceable source. Test missing records, mismatches, duplicates, and ordinary work. The owners must set justified pass criteria and a cost ceiling before evaluation; they are not yet agreed.
06 / Exceptions and fallback
Hold discrepancies and missing originals. Check the records already received before requesting information again. Ask for genuinely missing or stale information. Never guess a quantity, approve a payment, or create a second entry on retry. Staff retain the existing manual process.
07 / Next decision and evidence
Request authorization for bounded discovery only, not production. The next review needs an approved access plan, baseline definition, representative evaluation records, and cost and acceptance criteria. Proceed, narrow, or defer based on that evidence.