Clone Solutions
Template

Systems & Workflow Map

A department-by-department map of workflows, systems, handoffs and data, showing exactly where work stalls and where Clones can add capacity.

What this is for

The diagnostic needs a shared picture of how work actually moves: which systems it touches, where people rekey data, where it waits for an approval, and where it breaks. This map is that picture. It turns problem statements into concrete workflows, exposes the systems and data each Clone would need, and gives the scoring rubric the facts it needs for feasibility and data readiness.

When to use it

During the Weeks 2–3 diagnostic for priority departments, and again in the Discover week of each department rollout. Refresh it when a major system changes.

Who's involved

  • Business owner: confirms the map is accurate.
  • Two or three people who do the work: walk through the real steps.
  • IT lead or system admins: confirm systems, integrations and data locations.
  • Implementation Engineer and Solutions Architect Clone: interview, map and draft.

How to fill it in

  1. Start from the department's confirmed problem statements. Map those workflows first.
  2. Interview the people who do the work, not just their manager. Ask them to share their screen and walk through one real item.
  3. Record each step: who does it, in which system, how long it takes, and what can go wrong.
  4. Mark every handoff (person to person, system to system) and every wait.
  5. List the data each step needs and where it lives.
  6. Tag each step with a Clone fit signal (below). Do not design the solution yet.
  7. Review the map with the business owner and IT lead. Fix errors, then confirm.

The template

Department summary

FieldAnswer
Department
Business owner
Team size and roles
Interviewees
Problem statements coveredPS-___
Date mapped

System inventory (department view)

SystemUsed forUsersIntegrations todayAPI / connector availableData classificationAdmin owner
ERPPOs, receipts, invoice postingAP team, buyersNightly sync to data warehouseYesConfidentialIT applications

Workflow map

One table per workflow. Clone fit signals: R = repetitive, K = knowledge lookup, X = cross-system rekeying, J = judgment needed, A = approval gate, H = must stay human.

StepActorSystemActionInputOutputTime per itemWait before next stepFailure modesFit signals
1
1AP specialistShared inboxOpen supplier invoice email, download PDFEmailPDF2 min0–2 days in inboxMissed emails, duplicatesR
2AP specialistERPFind PO and goods receiptPO number on invoiceMatched PO6 minNonePO missing or wrong on invoiceK, X
3AP specialistERPThree-way match, key invoicePDF, PO, receiptInvoice record8 minNonePrice or quantity varianceX, J
4AP supervisorERPApprove variances over toleranceVariance flagApproval2 min1–3 daysSupervisor backlogA, H

Handoffs and waits

FromToMechanism (email, ticket, chat, system queue)Average waitWhat gets lost
AP specialistBuyerEmail asking for missing PO2.5 daysContext; follow-ups

Data and knowledge sources

Knowledge or data neededWhere it livesOwnerQuality (Good / Patchy / Poor)Sensitive?Notes
Vendor tolerance rulesPolicy PDF in file shareControllerPatchy: two versionsInternalNeeds one approved version before loading

Observations

  • Biggest time sink: step and minutes
  • Biggest wait: handoff and days
  • Biggest risk point: step and why
  • Quick fixes that don't need AI: e.g. a required PO field on the supplier portal
  • Candidate Clone opportunities: list, each linked to a problem statement

Good looks like

  • Mapped from a real item, watched on screen, not from the process document.
  • Waits are measured. Most cycle time hides in handoffs, not in the work itself.
  • Data quality is honest. "Patchy" now saves a failed pilot later.
  • Human steps are named, with the reason they stay human.
  • Non-AI fixes are captured. Clone-first, not Clone-only: some answers are a form field or an n8n flow.
  • Common mistake: mapping the whole department at once. Map the workflows behind the top problem statements first.

How Clone helps

The Solutions Architect Clone joins or reviews the interviews, drafts the workflow tables, flags missing timings and builds the system inventory from the pre-read. The Implementation Engineer validates feasibility and connector availability. In the portal, the map is the Systems & Workflow Map deliverable under Opportunity & Roadmap; each candidate opportunity is pushed to the Opportunity Inventory for scoring.

Sign-off

RoleNameDateDecision
Business ownerAccurate / Needs changes
IT leadSystems confirmed