Impact tracker · example
What AI is giving back to Example Co
Baseline a workflow, measure it again once people work the new way, and the hours add up here. Every number says whether it's the team's estimate or timed.
You're looking at example data for a made-up company. With Membership, the impact tracker runs on your own workflows, sessions and numbers.
- Hours back a week
- 15.8 Team estimate
- Workflows adopted
- 2 of 4
- People working the new way
- 21
- Training sessions
- 4
from 41.1 hours a week at baseline
1 workflow piloting
across piloting and adopted workflows
52 attendees · rated 4.4/5 useful
Hours back a week, by workflow
Each point is a measurement. Zero is the baseline.
Board pack
One page for your sponsor each month: the headline, what changed, sessions, and what you need from them.
See an example board packTeam scorecard
- Maturity score
- 18.4 / 36
- Maturity level
- Experimenting
- Change since last survey
- +3.1
- People who answered
- 41
Champions
- Active champions
- 7 of 8
- Sessions run by champions
- 9
- People reached
- 64
- Wins logged
- 5
- •Month-end commentary drafted in two hours, not a day (Priya, Finance)
- •Shared prompt for refund replies (Tom, Support)
Workflows
| Workflow | Status | Baseline | Now | People using | Hours back / week | Source |
|---|---|---|---|---|---|---|
|
Monthly client report Account management · 6 people · 0.25× a week each |
Adopted | 180 min | 75 min | 6 | 2.6 | Timed |
|
Meeting notes and actions Delivery · 14 people · 4× a week each |
Adopted | 20 min | 7 min | 12 | 10.4 | Team estimate |
|
First-draft proposals Sales · 5 people · 1× a week each |
Piloting | 150 min | 95 min | 3 | 2.8 | Team estimate |
|
Policy questions inbox HR · 3 people · 12× a week each |
Baselined | 9 min | – | – | 0 | Team estimate |
How the numbers are worked out
Hours back a week = (baseline minutes − current minutes) × times a week each person does it × people using it ÷ 60.
"Current minutes" and "people using" come from the latest measurement. Dropped workflows count for nothing; a workflow that got slower shows a negative number rather than being hidden.
Numbers are labelled team estimate unless the measurement was timed. Estimates are fine (say so when you report them); timing a handful of real instances is better for the ones leadership cares about.