Clone Solutions
Template

Success Metrics & Baseline

Defines the Year-1 success metrics and captures a measured baseline per workflow, so results are reported as numbers against a before.

What this is for

Without a baseline there is no ROI, only anecdotes. This template does two jobs. Part A sets the Year-1 success metrics the steering committee will hold the engagement to. Part B captures a measured baseline for each workflow before its Clone goes live, then tracks actuals against it. The 90-Day Results Report, the 6-Month Business Review and the Year-1 Impact Report all draw from this one source.

When to use it

Part A in Weeks 3–4, alongside the ranked roadmap. Part B in the Discover week of each department rollout, before the pilot starts. Update actuals monthly.

Who's involved

  • Executive sponsor and steering committee: set Year-1 targets.
  • Business owner: confirms metrics and accepts the baseline.
  • Process owner and team: provide data or take part in time sampling.
  • IT or data team: extract system data where available.
  • Project Clone: collects, calculates and reports.

How to fill it in

  1. Agree Year-1 metrics (Part A). Keep to six to eight. Every one needs a definition and a data source.
  2. For each workflow going live, choose three to five metrics from the menu in Part B: at least one for effort, one for speed or quality, and one for adoption.
  3. Capture the baseline from system data where possible. Where not, time-sample: have the team log a representative set of items over 2–5 days.
  4. Record the data source and the sample size next to every number.
  5. Have the business owner accept the baseline in writing before the pilot starts. A baseline accepted after the results are known is not trusted.
  6. Record actuals monthly, using the same definition and method.

The template

Part A: Year-1 success metrics

#MetricDefinitionTarget by Month 12Data sourceOwnerReported
1Departments liveDepartments with at least one Clone in production use and a tracked baseline6–8PortalSolutions PartnerMonthly
2Productivity or cost gain per departmentHours given back or cost avoided vs. baseline, per live departmentAgreed per departmentPart BBusiness ownersMonthly
3Workflows at Execute with approval or higher% of live workflows at autonomy level 3+e.g. 50%Governance CharterInfoSec leadMonthly
4Governance incidentsIncidents above agreed severity0Risk RegisterInfoSec leadWeekly
5Champion coverage% of live departments with an active champion100%Champion rosterChange LeadMonthly
6Weekly active usersPeople who used a Clone in the past 7 days, as % of licensed usersAgreedPlatform usageChampionsWeekly
7Center of Excellence in placeCoE charter approved and meetingBy Month 9CoE charterExecutive sponsorQuarterly
8Organization-specific

Part B: Workflow baseline and tracking

Workflow details

FieldEntry
Workflow
Department / business owner
Linked problem statement and opportunityPS-_ / OP-_
Clone
Baseline periodfrom – to
MethodSystem data / Time sample / Both
Sample size

Metric menu

TypeMetricTypical definition
EffortHandling time per itemMinutes of human effort from start to done
EffortHours per week on the workflowTotal team hours
SpeedCycle timeElapsed time from trigger to completion
SpeedBacklogItems waiting at a point in time
QualityError or rework rate% of items corrected after completion
QualityFirst-contact resolution% resolved without a second touch
ServiceSLA attainment% completed within the agreed time
FinancialCost of failureFees, write-offs, credits caused by errors or delays
AdoptionClone usage rate% of eligible items where the Clone was used
AdoptionOverride rate% of Clone outputs changed or rejected by a person
ExperienceTeam or customer satisfactionShort pulse survey score

Baseline and actuals

MetricDefinitionBaselineSource / sampleTargetMonth 1Month 2Month 3Month 6Month 12
Handling time per invoiceMinutes of AP effort from email to matched record18 minTime sample, 3 specialists, 240 invoices, 4 days< 7 min
Matched within 2 business days% of invoices matched within 2 days of receipt61%ERP timestamps, 30 days90%
Late-payment feesFees per monthFrom AP ledgerERP, 6 monthsDown 75%
Clone usage rate% of invoices processed with the Clone0%Platform90%

Value calculation (for results reports)

ItemFormulaValue
Hours given back per month(Baseline minutes − Actual minutes) × Volume ÷ 60
FTE equivalentHours given back ÷ [standard monthly hours]
Quality gainBaseline error rate − Actual error rate
Cost of failure avoidedBaseline cost of failure − Actual

Report hours given back as capacity redeployed to higher-value work. Note what the team did with the time.

Baseline acceptance checklist

  • Every metric has a written definition
  • Data source and sample size recorded
  • Sample covers a normal period (not month-end only, not a holiday week)
  • Business owner accepted before pilot start
  • Measurement method for actuals is the same as for the baseline

Good looks like

  • Accepted before the pilot. A baseline agreed after results are known will be questioned.
  • Few metrics, well defined. Three to five per workflow, each with one definition everyone uses.
  • System data where possible, time samples where not, and both labeled.
  • Adoption measured alongside impact. Great results from 10% usage are a pilot, not a rollout.
  • Common mistake: measuring hours saved but not what changed. Pair the efficiency number with a quality or service number.

How Clone helps

The Project Clone sets up time-sampling forms, pulls system data through approved connections, calculates baselines and monthly actuals, and feeds the numbers into steering packs and results reports. The Solutions Architect Clone suggests metrics from the problem statement. In the portal, Part A is the Year-1 Success Metrics deliverable in Foundation and Part B is the Baseline Metrics deliverable for each department; actuals appear on the adoption and results views.

Sign-off

RoleNameDateDecision
Executive sponsor (Part A)Year-1 metrics approved
Business owner (Part B, per workflow)Baseline accepted