Skip to content

Follow one customer workflow from discovery to delivery.

Follow fictional Northstar Supply through discovery, product decisions, requirements and handover. Every source, decision and requirement is open to inspect.

Discuss a pilot

Fictional customer data. Open the evidence. No sign-up.

Evidence Decisions Scope Handover
01

Trace each decision

Inspect source evidence, conflicting rules and authored customer decisions together.

02

Inspect the scope

See included work, open questions and the pending change request.

03

Follow the handover

Connect requirements, acceptance cases, operating instructions and the measurement plan.

Illustrative example - fictional customer data

Northstar Supply · The worked example

One workflow.
Every decision connected.

A fictional purchase-approval deployment. Follow a disputed threshold from source evidence to a reviewed target, delivery requirements and operating ownership.

No live AI or changes to product records. Identity access and escalation ownership remain open.

Original sources POL-01 and WB-01 lead to authored decision D-01, requirement R-01, and operating instruction O-02. The customer decision is distinct from the supplied sources.

Keep the evidence attached at every handoff.One inspectable fictional thread
01

Place the vendor’s product in the customer’s operation.

The customer is adopting a software vendor’s platform. Its delivery team proposes request intake, approval routing and an assistant that prepares recommendations. These are design choices for product and customer review, not completed configuration or a live agent.

Customer operationNorthstar Supply

Purchase requests, approval rules and urgent exceptions

Reviewed workflow & rules
Vendor implementation

Your SaaS platform

Request intakeApproval recordRouting
Agent prepares

Check the request.
Recommend the route.

Inspect agent boundaries
People decide

Approve the purchase.
Handle exceptions.

Inspect the rules
Operating handover
Customer team runs the workflow

Procedure · operating owner · escalation route

Inspect the handover

Proposed use of a vendor’s product, subject to capability and implementation review. Access and escalation remain open.

02

Understand the operation around the product.

Workflow is one part of the customer context. Review the people, handoffs, existing technology, data movement and controls as well. Unknowns remain visible rather than being filled in as facts.

Workflow

Purchase requests and urgent exceptions

REC-01POL-01Confirm the other paths

People & organization

Requester, purchasing manager and finance roles

POL-01REC-01Reporting lines and named owners to confirm

Handoffs

Purchasing-manager notification and proposed approval routing

REC-01Escalation remains open under Q-05

Existing technology

The approval workbook is supplied

WB-01ERP, messaging and identity systems to confirm

Data flows

Order ID, amount and urgent status are required

WB-01REC-01Field ownership and integration mapping to confirm

Rules & controls

Policy and workbook disagree at USD 10,000

POL-01WB-01D-01 defines the target; originals stay unchanged

This register distinguishes supplied evidence from what still needs discovery. It is not a completed organization, architecture or data-flow model.

03

Keep Product, customer requests and development connected.

CR-01 asks to extend the brief into production integration. The vendor must decide whether this is configuration, a customer-specific extension or a broader product change before committing development effort.

Evidence informs the design
Product management

Capabilities & priorities

Fit, gaps, requirements and roadmap decisions.

Explore Product Management
Customer workflow

Current → target state

People, systems, agents and operating responsibilities.

Inspect the target design
CR-01
Request: add production integration

Proposed scope change · decision pending

Inspect
Rapid development

Spec → build → test → review

Your engineering workflow or Build Factory Beta

Explore the build demo
Operate & learn

Owner → use → feedback

Operating handover and observed customer needs.

Feed learning into Product

Customer learning informs the next product decision.

CR-01 is unapproved. No build or deployment has run. Build Factory requires configured runners, repository access and review.

Customer request · CR-01

Add production integration for the approval route.

The request extends the agreed brief. Production integration remains excluded until scope, architecture, access and effort are reviewed.

Product decision
Review standard configuration, customer-specific extension or a reusable product change. No option is approved in this example.
Development input
A cited specification, affected requirements, boundary cases and dependencies. A build starts only after the appropriate review.
Return to Product
Capture the request and later deployment feedback with the customer context intact. Decide what belongs on the product roadmap.
04

Start with what the customer supplied.

These prepared excerpts are the evidence for the fictional scenario. They are not presented as a verified product capture.

POL-01

Purchase approval policy

Prepared policy excerpt · version 1.0

Purchase orders above USD 10,000 require finance approval. All other purchase orders require purchasing-manager approval.

This original policy excerpt does not define an urgent-order exception. Its wording remains unchanged after the example review.

WB-01

Purchase approvals workbook

Prepared workbook fixture · version 1.0

northstar_purchase_approvals.xlsx

WB-01Approvals · version 1.0
A2 · Order ID
PO-1048
B2 · Amount USD
10000
C2 · Formula
=IF(B2>=10000,"Finance review","Purchasing manager review")
C2 · Illustrative saved resultFinance review

This formula refers to B2 in the same workbook version. Open the complete WB-01 excerpt.

The formula, input and illustrative saved result belong to the same fixture version. This website does not edit the workbook or recalculate an Excel file.

REC-01

Purchase walkthrough transcript

Authored transcript excerpt

For an urgent request, I mark it urgent and message the purchasing manager. I am not sure whether finance must approve it before release when the amount is high.

Authored for this fictional example. No recording or timestamp is implied. The speaker’s uncertainty does not establish permission to bypass approval.

The difference at exactly USD 10,000

A prepared comparison of the supplied rules, before customer review.

USD 9,999

POL-01 · > 10000
Purchasing manager review
WB-01 · >= 10000
Purchasing manager review

The two supplied rules select the same route for this amount.

USD 10,000

POL-01 · > 10000
Purchasing manager review
WB-01 · >= 10000
Finance review

Different routes. Q-01 requires a customer decision.

USD 10,001

POL-01 · > 10000
Finance review
WB-01 · >= 10000
Finance review

The two supplied rules select the same route for this amount.

Changing this example amount compares the two rules. It does not edit WB-01; its saved B2 remains 10000.

05

Separate observed work from the proposed target.

The walkthrough describes marking an urgent request and messaging the purchasing manager. It does not confirm the authority to release a high-value order.

Current evidence · REC-01

Request marked urgent → purchasing manager notified → finance approval before release is unclear.

Read the authored walkthrough

Proposed target workflow

REQUESTOrder ID · amount · urgent status

Ordinary route

  1. Check the amount
  2. Below USD 10,000 → purchasing manager
  3. At or above USD 10,000 → finance
  4. A person records the approval decision

Urgent branch

  1. Mark urgent
  2. Notify purchasing manager
  3. Keep the amount-based approval route
Urgency does not bypass approval.

Proposed target after D-01 and D-02. The original walkthrough remains uncertain about finance approval.

Open question

Q-05 · Who receives an escalation, and through which route?

Owner: Customer process owner

Draft interpretation

“Finance reviews orders above USD 10,000; an urgent request messages the purchasing manager.”

POL-01REC-01

This draft does not settle the boundary or permission to release an urgent order.

Authored customer correction
“Use finance review at or above USD 10,000. Urgent requests still need the required approval; notifying the purchasing manager is an additional step.”

Customer process owner · fictional review

D-01 · threshold · D-02 · urgency

This prepared review changes the proposed target behavior. The policy and walkthrough remain unchanged as supplied evidence.

06

Give every uncertainty an owner.

Q-01–Q-03 have authored resolutions in this example. Q-04 and Q-05 remain open prerequisites for live operation.

Q-01Reviewed in example

Which route applies at exactly USD 10,000?

The policy says above; the workbook says at or above. A customer decision is needed to define the target rule.

Owner: Customer process owner

POL-01WB-01

Follow the authored decision D-01

Q-02Reviewed in example

Does urgency change the required approver?

The walkthrough identifies a purchasing-manager notification but leaves approval before release uncertain. The policy supplies no urgent exception.

Owner: Customer process owner

REC-01POL-01

Follow the authored decision D-02

Q-03Reviewed in example

What should happen when the amount is missing?

A valid amount is necessary to apply the target rule. Missing-amount behavior is a proposed design decision, not an observation from the supplied sources.

Owner: Customer process owner

WB-01

Follow the authored decision D-03

Q-04Open question

Which identities and access rights will support the workflow?

Confirm the identity source, reviewer membership, permissions and access with the technical delivery lead. This prerequisite remains unresolved.

Owner: Customer process owner

Q-05Open question

Who receives an escalation, and through which route?

Escalation route: To be agreed. The owner of this decision is not assumed to be the eventual escalation recipient.

Owner: Customer process owner

07

Inspect the example customer review.

A human decision defines the proposed target. Original evidence stays available, including the disagreement at exactly USD 10,000.

See the example reviewAuthored fictional decision
Draft interpretation

“Finance reviews orders above USD 10,000; an urgent request messages the purchasing manager.”

POL-01REC-01

This draft does not settle the boundary or permission to release an urgent order.

Authored customer correction
“Use finance review at or above USD 10,000. Urgent requests still need the required approval; notifying the purchasing manager is an additional step.”

Customer process owner · fictional review

D-01 · threshold · D-02 · urgency

This prepared review changes the proposed target behavior. The policy and walkthrough remain unchanged as supplied evidence.

D-01Reviewed in example

Include the threshold

For the proposed target workflow, purchase orders at or above USD 10,000 require finance approval. Lower amounts require purchasing-manager approval.

Authored customer review decision. POL-01 retains its original “above” wording; the target follows the inclusive boundary visible in WB-01.

Reviewer: Customer process owner · fictional role

Q-01 → R-01

D-02Proposed design

Urgency does not bypass approval

An urgent request notifies the purchasing manager, while the amount still determines the required approval route. Urgency does not authorize release or bypass approval.

Authored customer review decision for the target workflow. REC-01 leaves this behavior uncertain; it is not inferred as current practice.

Reviewer: Customer process owner · fictional role

Q-02 → R-02

D-03Proposed design

Clarify an incomplete request

When the purchase amount is missing, request clarification from the requester. Do not prepare an approval recommendation until a valid amount is supplied.

Authored customer review decision for the target workflow. The source fixture does not establish missing-amount behavior.

Reviewer: Customer process owner · fictional role

Q-03 → R-03

08

Carry the decisions into implementation requirements.

Select a requirement to inspect its source, decision reference and expected behavior. These business requirements still need technical discovery and implementation checks.

R-01Route a complete purchase requestInspect
Reviewed in example

At or above USD 10,000 → Finance review. Below USD 10,000 → Purchasing manager review.

Source references
POL-01WB-01
Customer review
D-01 · authored decision resolving Q-01
Operating instruction
O-02
A-01USD 9,999 · ordinary

Purchasing manager review

R-01 · Expected behavior
A-02USD 10,000 · ordinary

Finance review

R-01 · Expected behavior
A-03USD 10,001 · ordinary

Finance review

R-01 · Expected behavior

These are expected behaviors for the fictional target. No model or implementation tests have been executed.

Implementation and access checks remain with the delivery team; see Q-04 and Q-05.

R-02Keep urgent requests in the approval routeInspect
Proposed design

Notify the purchasing manager when a request is urgent. Apply R-01 to choose the required approver; urgency does not bypass approval or authorize release.

Source references
REC-01POL-01
Customer review
D-02 · authored decision resolving Q-02
Operating instruction
O-03
Expected behavior · not executed

Notify purchasing manager; finance approval still required. No bypass or release.

Implementation and access checks remain with the delivery team; see Q-04 and Q-05.

R-03Request a missing amountInspect
Proposed design

If the amount is missing, request clarification. Do not prepare an approval recommendation until a valid amount is supplied.

Source references
WB-01
Customer review
D-03 · authored decision resolving Q-03
Operating instruction
O-01
Expected behavior · not executed

Request clarification; do not prepare an approval recommendation.

Implementation and access checks remain with the delivery team; see Q-04 and Q-05.

09

Make the expected behavior concrete.

The rows below are acceptance examples for the fictional target, not evidence that an implementation or model has passed a test.

A-01USD 9,999 · ordinary

Purchasing manager review

R-01 · Expected behavior
A-02USD 10,000 · ordinary

Finance review

R-01 · Expected behavior
A-03USD 10,001 · ordinary

Finance review

R-01 · Expected behavior
A-04USD 10,000 · urgent

Notify purchasing manager; finance approval still required. No bypass or release.

R-02 · Expected behavior
A-05Amount missing · ordinary or urgent

Request clarification; do not prepare an approval recommendation.

R-03 · Expected behavior

These are expected behaviors for the fictional target. No model or implementation tests have been executed.

10

Keep the engagement boundary explicit.

The example prepares a purchase-routing brief. Commercial estimates and delivery commitments remain the strategist’s responsibility.

Included
  • One purchase-approval workflow
  • Reviewed routing rules and open decisions
  • Acceptance examples and operating instructions
  • A measurement plan and responsibility handover
Excluded
  • Payment execution
  • ERP replacement
  • Production integration
Open question

Q-04 · Which identities and access rights will support the workflow?

Owner: Customer process owner

Delivery dependencies

  • Architecture and implementation checks — technical delivery lead
  • Q-04 · identity and access — customer process owner, with technical delivery lead
  • Q-05 · escalation route — customer process owner
11

Use the same rule in the operating instructions.

Prepared instructions for customer review. The original policy still says “above”; D-01 deliberately defines a different target boundary.

  1. O-01

    Check the request

    Check the order ID, amount in USD and urgent status. If the amount is missing, ask the requester to supply it. Do not prepare an approval recommendation until a valid amount is available.

    Requester / operating owner · R-03
  2. O-02

    Prepare the required approval route

    For an amount at or above USD 10,000, route to finance review. For an amount below USD 10,000, route to purchasing-manager review. The designated person makes and records the approval decision.

    Operating owner · R-01
  3. O-03

    Handle an urgent request

    Mark the request urgent and notify the purchasing manager. Keep the amount-based approval route from O-02. Do not release or bypass approval because the request is urgent.

    Operating owner / purchasing manager · R-02
  4. O-04

    Resolve prerequisites before live operation

    Q-04: confirm identities and access. Q-05: Escalation route: To be agreed. Agree the escalation recipient and route before this procedure is used in live operation.

    Customer process owner, with technical delivery lead
Escalation route: To be agreed — Q-05

Decision owner: Customer process owner. Q-04 · identity and access also remains open. Live operation is not ready on the strength of this brief alone.

12

Pass the responsibility with the evidence.

Every role below is fictional. A prepared brief does not establish production readiness.

01

Delivery lead

Prepare the brief, preserve source references and carry open questions into implementation.

Receives
Supplied policy, workbook and authored walkthrough
Passes on
Workflow, scope, requirements and acceptance examples
02

Customer process owner

Confirm business behavior and acceptance; resolve Q-04 and Q-05 with the relevant specialists.

Receives
Rules, conflicts and proposed decisions
Passes on
Reviewed target behavior and explicitly open prerequisites
03

Technical delivery lead

Confirm architecture, identity/access and implementation checks. Run implementation tests before a readiness decision.

Receives
R-01–R-03 and unresolved technical prerequisites
Passes on
Implementation evidence and remaining delivery risks
04

Operating owner

Maintain the procedure and follow the agreed approval route after operational readiness is established.

Receives
Operating instructions and approved access arrangements
Passes on
Maintained procedure and operational feedback

Fictional role labels. Reviewed rule: R-01 · at or above USD 10,000 goes to finance.

Open question

Q-04 · Which identities and access rights will support the workflow?

Owner: Customer process owner

Readiness at this handoff

Business rule
Reviewed in exampleInspect R-01
Operating guide
Prepared for customer review
Identity and access
Open questionQ-04 · pending
Escalation route
Q-05 · To be agreed
Implementation tests
Not run
Go-live decision
Not complete
13

Agree how usefulness will be measured.

Customer operating results and engineering effort are separate measures. Neither has an observed result in this example.

M-01 · Customer operating outcome

Elapsed business time from a complete purchase request to a recorded approval decision

Baseline
To collect
Target
To agree
Latest actual
Not measured

Measurement owner: Customer process owner

Define the business-hours calendar, event data source and measurement window before collecting a baseline.

Review cadence and measurement window: To agree

Business-hours calendar, data source and measurement window: To agree.

M-02 · Delivery-team effort

Staff hours spent preparing, checking, revising and reviewing the brief

Baseline
To collect
Target
To agree
Latest actual
Not measured

Measurement owner: Vendor delivery lead

Record total staff effort through review for a comparable workflow. Keep this vendor-effort measure separate from the customer’s operating outcome.

Review period: To agree during pilot scoping

14

Define a proposed assistant’s limits.

This is a design input for the vendor’s AI implementation. The website does not operate an agent, enforce permissions or execute an evaluation.

Proposed design
Required inputs

Order ID · valid amount in USD · urgent status · reviewed routing rule

Assistant may prepare
  • Check supplied fields for completeness
  • Request clarification for a missing amount
  • Prepare a routing recommendation using R-01
  • Flag urgency and notify the purchasing manager
A person must decide
  • Confirm the business rule and permissions
  • Make and record the approval decision
  • Resolve unclear policy and escalation
  • Authorize any release in the implemented workflow

Proposed design for the customer implementation. Urgency never authorizes bypass. Identity and access (Q-04) and escalation (Q-05) remain open.

R-02 · D-02

Urgent order

Notify the purchasing manager. The amount-based approval still applies; urgency cannot authorize bypass or release.

Inspect urgent-request behavior
R-03 · D-03

Missing amount

Ask the requester for clarification. Do not prepare an approval recommendation until a valid amount is supplied.

Inspect incomplete-request behavior
Q-01

Unclear or conflicting policy

Keep the disagreement visible and ask the customer process owner to decide. A proposed assistant must not invent a resolution.

Inspect the question register
Next step for the implementation team

Resolve Q-04 and Q-05, then execute model evaluation, integration tests and operational checks against the agreed requirements. Record actual results separately from these expected behaviors.

15

Follow the complete thread.

One inspectable chain connects supplied evidence, a question, a fictional human decision, a requirement and an operating instruction.

  1. EvidencePOL-01 + WB-01

    “Above” and “at or above” disagree at USD 10,000.

  2. QuestionQ-01

    Which route should the target use at the boundary?

  3. Human decisionD-01

    The fictional customer owner chooses the inclusive threshold.

  4. RequirementR-01

    At or above USD 10,000 → finance review.

  5. Operating instructionO-02

    Prepare the route; a person records the approval decision.

End of the complete authored sample brief. Illustrative example - fictional customer data. The example records no customer outcome or completed deployment.

Bring one workflow from your customer deployments.

Discuss the source material, useful deliverables and measures for a focused evaluation.

Discuss a pilot

Explore your own customer deployment.

Bring one workflow to scope your deployment brief.

Discuss a pilot

Scope, timing, access and terms are agreed before a pilot begins.

Product view

ProcessScout interactive demo · Fictional Northstar data