# 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

| # | Metric | Definition | Target by Month 12 | Data source | Owner | Reported |
|---|---|---|---|---|---|---|
| 1 | Departments live | Departments with at least one Clone in production use and a tracked baseline | _6–8_ | Portal | Solutions Partner | Monthly |
| 2 | Productivity or cost gain per department | Hours given back or cost avoided vs. baseline, per live department | _Agreed per department_ | Part B | Business owners | Monthly |
| 3 | Workflows at Execute with approval or higher | % of live workflows at autonomy level 3+ | _e.g. 50%_ | Governance Charter | InfoSec lead | Monthly |
| 4 | Governance incidents | Incidents above agreed severity | _0_ | Risk Register | InfoSec lead | Weekly |
| 5 | Champion coverage | % of live departments with an active champion | _100%_ | Champion roster | Change Lead | Monthly |
| 6 | Weekly active users | People who used a Clone in the past 7 days, as % of licensed users | _Agreed_ | Platform usage | Champions | Weekly |
| 7 | Center of Excellence in place | CoE charter approved and meeting | _By Month 9_ | CoE charter | Executive sponsor | Quarterly |
| 8 | _Organization-specific_ | | | | | |

### Part B: Workflow baseline and tracking

**Workflow details**

| Field | Entry |
|---|---|
| Workflow | |
| Department / business owner | |
| Linked problem statement and opportunity | PS-___ / OP-___ |
| Clone | |
| Baseline period | _from – to_ |
| Method | System data / Time sample / Both |
| Sample size | |

**Metric menu**

| Type | Metric | Typical definition |
|---|---|---|
| Effort | Handling time per item | Minutes of human effort from start to done |
| Effort | Hours per week on the workflow | Total team hours |
| Speed | Cycle time | Elapsed time from trigger to completion |
| Speed | Backlog | Items waiting at a point in time |
| Quality | Error or rework rate | % of items corrected after completion |
| Quality | First-contact resolution | % resolved without a second touch |
| Service | SLA attainment | % completed within the agreed time |
| Financial | Cost of failure | Fees, write-offs, credits caused by errors or delays |
| Adoption | Clone usage rate | % of eligible items where the Clone was used |
| Adoption | Override rate | % of Clone outputs changed or rejected by a person |
| Experience | Team or customer satisfaction | Short pulse survey score |

**Baseline and actuals**

| Metric | Definition | Baseline | Source / sample | Target | Month 1 | Month 2 | Month 3 | Month 6 | Month 12 |
|---|---|---|---|---|---|---|---|---|---|
| | | | | | | | | | |
| _Handling time per invoice_ | _Minutes of AP effort from email to matched record_ | _18 min_ | _Time sample, 3 specialists, 240 invoices, 4 days_ | _< 7 min_ | | | | | |
| _Matched within 2 business days_ | _% of invoices matched within 2 days of receipt_ | _61%_ | _ERP timestamps, 30 days_ | _90%_ | | | | | |
| _Late-payment fees_ | _Fees per month_ | _From AP ledger_ | _ERP, 6 months_ | _Down 75%_ | | | | | |
| _Clone usage rate_ | _% of invoices processed with the Clone_ | _0%_ | _Platform_ | _90%_ | | | | | |

### Value calculation (for results reports)

| Item | Formula | Value |
|---|---|---|
| Hours given back per month | (Baseline minutes − Actual minutes) × Volume ÷ 60 | |
| FTE equivalent | Hours given back ÷ [standard monthly hours] | |
| Quality gain | Baseline error rate − Actual error rate | |
| Cost of failure avoided | Baseline 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

| Role | Name | Date | Decision |
|---|---|---|---|
| Executive sponsor (Part A) | | | Year-1 metrics approved |
| Business owner (Part B, per workflow) | | | Baseline accepted |

## Related

- [Problem Statement Worksheet](/playbook/templates/problem-statement-worksheet)
- [Pilot Scorecard](/playbook/templates/pilot-scorecard)
- [90-Day Results Report](/playbook/templates/ninety-day-results-report)
- [Year-1 Impact Report](/playbook/templates/year1-impact-report)
- [Clone Solutions: Results](https://clone.org/solutions/results)

---
From the Clone Solutions Playbook: https://solutions.clone.org/playbook/templates/success-metrics-baseline
