Measuring adoption, workflow abandonment, and cost
A paired measurement model for GTM systems that shows whether people use the workflow, where they abandon it, and what each successful business outcome costs.
On this page
A workflow can be used often and still produce little value. Measure usage beside the outcome and the cost of getting there.
Define the events
| Event | Example |
|---|---|
| Eligible | Record meets the workflow contract |
| Started | Owner opens or accepts the work |
| Abandoned | No next event by the stated deadline |
| Completed | Business completion evidence exists |
| Costed | Provider, compute, or human review cost is recorded |
Do not call a record adopted because the system enrolled it. Adoption requires the owner action that makes the workflow useful.
Paired scorecard
Eligible: 120
Started: 92
Completed: 71
Abandoned: 18
Still open: 31
Total measured cost: defined in the metric dictionary
Cost per completed outcome: cost / 71Keep open and abandoned separate. An open record has not had its full window.
Find the abandonment point
Group abandonment by step, owner, source, workflow version, and reason. If people stop after an approval preview, the preview may be too slow or unclear. If they stop after assignment, the handoff payload or SLA may be wrong. Fix the step, then watch the same cohort.
Cost boundary
State whether cost includes vendor usage, internal review time, implementation, or fixed platform fees. Use the same boundary across versions. Cost is a useful decision measure only when a successful outcome is defined.
Measure meaningful use
Opening a tool or creating a record is not necessarily adoption. Define the smallest event that shows the intended work was completed, and connect it to a stable user, subject, workflow version, and outcome. Separate eligible users from licensed users and distinguish first use, repeated use, and sustained use over a named period.
Build a funnel from eligibility through start, key steps, completion, accepted outcome, and repeat use. Show counts and rates, plus time between steps. Preserve explicit exits such as not applicable, rejected, superseded, and failed; treating every non-completion as abandonment points the team toward the wrong fix.
Compare value with the full cost
Report cost per eligible item, attempt, completed workflow, and accepted business outcome. Separate fixed implementation cost, platform cost, variable vendor or model usage, and estimated human review time. Compare versions and segments only with the same cost boundary. A cheaper run that creates more cleanup is not cheaper in operation.
Related: GTM metric dictionary template, Leading and lagging indicators, and GTM operating review template.
Related guides
FAQ
- How do I measure workflow adoption?
- Define the eligible population, the first meaningful use event, the completion event, and abandonment. Report counts and rates by owner or team, with open and suppressed records visible.
- How do I calculate cost per successful outcome?
- Add the costs inside the defined measurement window, including provider usage and operational review, then divide by successful business outcomes. Show the population, exclusions, and whether fixed costs are included.
Get the next guide
New guides and the occasional note on GTM tooling. Don't worry, I won't drop you into a three-month nurture.