How to Baseline Cycle Time Before Automation

Teams buy automation when drowning in tickets. Without a baseline, vendors claim success for work you already did.

Foundation5 process engineering baselines before tools — the Subsplash 5x pattern and the process mapping pillar.

What to measure

Median and p90 cycle time for one critical flow; percent rework; volume per FTE; customer-visible error rate. Pull thirty days of system timestamps plus a shadow sample — systems lie when side channels exist.

How to capture without a six-month program

Pick one flow (lead-to-cash, case-to-resolution, quote-to-invoice). Shadow three transactions. Annotate waits and loops. Agree definitions with ops and finance in one workshop.

Using the baseline

Removal and redesign targets must beat baseline at thirty and ninety days. Automation coverage is secondary to cycle time and rework. Tie to remove approvals before you automate.

Related reading

Meeting-to-CRM after process mapping. Contact.

Facilitation tips that keep maps honest

Shadow real transactions before the workshop. Bring a draft swimlane, not a blank board. Separate policy from habit in two columns. End with owners and open questions.

Baseline cycle time and rework before changing anything — otherwise vendors claim success for volume you already had. Subsplash scaled 5x with the same headcount by fixing flow first.

When you are ready to apply this on your stack, schedule a consultation with Foundation5 — we stay accountable to named business outcomes, not tool checklists.