Signal: Usage Is Not Value
Prompt counts are useful, but they need an outcome sitting beside them. Before deciding on prompt usage dashboards, consider also measuring the why.
Usage Is Not Value
AI usage is easy to count, AI value in the work still needs to show up at some point to reflect the usage.
Usage is not value.
What showed up
A dashboard shows prompts, users, sessions and adoption rates, while those numbers can be useful, if nobody can explain what improved, what changed or what stopped, the dashboard is mostly reporting activity.
Why it matters
A lot of AI programmes start with usage because usage is visible. This is not wrong but it is just incomplete. If the goal is better work, then the value question has to sit beside the usage number from the beginning.
The pattern
The pattern is metric convenience. The easiest number becomes the headline because it is available first. The harder number, outcome, waits behind people, process, finance and reality, that creates a gap where activity can be mistaken for progress.
Where this shows up in everyday work
- A team reports 10,000 prompts but cannot name the task that got meaningfully better.
- An AI assistant has high adoption, but rework, review time and meeting volume do not fall.
- Leaders see usage growth and assume the business case is working before Finance has recognised any benefit.
- Employees try multiple prompts because the tool is available, but nobody knows whether the repeated attempts saved time overall.
What to watch before it becomes another programme
- Put an outcome next to every usage metric.
- Track whether AI reduces rework, cycle time, errors, escalation or manual handoffs.
- Watch for leaderboards that reward volume instead of better work.
- Do not call a pilot successful only because people tried it.
- Ask what would make the usage number matter to someone outside the AI rollout team.
The Satire
The adoption rate is high, the usefulness rate may still be pending.
Related Vieews paths
Signals pull the thread. Guides help check it. Playbooks hold the heavier structure when needed.
Chaos
The Blue Blob and the Prompt Counter
The discovery scene that started this thread.
Guide
Usage-to-Outcome Map
Use the practical check when you need the next simple move.
Playbook
AI Workload Waste Ledger
Use the heavier structure when the topic needs more depth.
Useful context
This Signal connects to the broader AI Workload Waste thread: use is not bad, but use needs evidence. Otherwise the organisation may be measuring motion while the work stays the same.
These are Vieews, not bibles, use as basic lenses, not prediction, investment advice, legal advice, or a replacement for doing your own investigation. If a line makes the spreadsheet uncomfortable, excellent, ask one more question, tug on that thread (don't get fired!).
