This is still the fifth of the five decisions, Visibility. You’ve set up the record of what happened. This lesson covers the other question visibility can help to answer: Is the rollout meeting its objective? Your analytics (the dashboard, Analytics chat, and the Analytics API covered in Lesson 10) report what members actually do with Claude, and you read those numbers against your rollout objective to see whether adoption is spreading or stalling in a few groups.
Breadth and depth measure adoption: whether Claude usage is taking hold and how much members rely on it. They are leading indicators you act on that tell you Claude is being used, not what that use produced. To see what the usage is delivering, pair these signals with the outcomes of the work itself. A high count can be one enthusiastic team, and a low one can be a team that was never properly enabled. Read these as diagnostics rather than proofs — a low number tells you where to look, not what you’ll find.
The common signals, and how to read them
The dashboard shows more numbers than any one lesson could list, so this lesson focuses on the signals you’ll meet most often and ways to consider interpreting them. Each signal here is one of two kinds: breadth or depth. When a number is low, ask which kind it is, then look where that kind of problem lives.
| Signal | What it tells you | When it’s low, look at |
|---|---|---|
| Active members, by group (breadth) | Whether adoption is spread across your groups or concentrated in one | Access and awareness: does that group have Claude, and has it been properly enabled? |
| Members returning week over week (breadth) | Whether members come back or try Claude once and stop | Onboarding and expectations: what did the first session promise? |
| Chats per active member (depth) | How much each active member relies on Claude | Fit: do this group’s surfaces and connectors match their workflows? |
| Skills and/or projects in use (depth) | Whether work is compounding into workflows others reuse | Your governance posture: is it letting transformative work spread? |
| Connector use (depth) | Which of your tools matter and how much Claude acts inside them | Your connector scope from Lesson 7: does it allow connectors to create value in members’ workflows? |
For the group-by-group view this lesson relies on, use the group breakdowns from Lesson 10 (the Analytics API by group, or the spend CSV joined to your group mapping). None of these numbers are a target to manage; they’re diagnostics. The month you turn a diagnostic into a quota, members optimize for the number instead of the work.
The interactive widget below is a way to think a number through: it hands you a dashboard shape and traces it to every cause that could produce it — usually more than one — to see what it can tell you, and what it can’t.
Pluto’s adoption read
Pluto’s pace goal: every unit returning weekly by quarter’s end, read monthly on active members by group. Four weeks in, Pluto’s dashboard shows most groups active and climbing, but Ops flat at about ten percent of its members active. Flat Ops is a breadth signal, so Pluto looks at access and awareness rather than assuming the rollout failed, and asks the Ops lead. The cause is simple: most of Ops is field staff who haven’t had their team enablement session yet because of competing priorities. They either don’t know Claude exists or haven’t been trained to use it. The fix is usually enablement, not a settings change: a replay of the company workshop or a targeted session. Same count, and the interpretation would have been the opposite for a team that once had access and stopped coming back.
Set up resources
The signals in this lesson live in three distinct locations; these articles cover reading each.
- View usage analytics for Team and Enterprise plans(opens in new tab): the adoption and usage read the admin dashboard gives you.
- Analytics APIs (Claude Platform Docs)(opens in new tab): pulling the same signals into your own reporting.
- Claude Enterprise consumption guide(opens in new tab): Analytics chat, and how to read the numbers behind the signals.
Lesson activity
In Lesson 1 you wrote your rollout objective, which included what success looks like and any constraints. You may not be able to measure adoption yet if your members haven’t been given access to Claude, but this is the moment to decide what you’ll measure.
- Set the pace goal that will tell you, month by month, whether you’re on the way there: which groups should be active by when, and what breadth and depth would count as on track versus behind.
- Make the pace goal concrete against a signal you’ll actually be able to read. “Every granted group returning weekly within eight weeks” is a pace; “good adoption soon” is a wish.
- Choose one group you’d most expect to lag, and decide now what a flat number there would prompt you to do first.
- Finalize these checkpoints with your stakeholders rather than alone, since unit leaders own what their teams can absorb, and treat this as the draft you bring them.
- Once members are in and the dashboard has signal, come back and read it against this goal.
→ Record this in the work-along companion, section Lesson 12.
Downloads
What’s next
The next module, Your rollout, pulls your five decisions together on one map: your five answers in a single table beside Pluto’s, the way one decision cascades into the others, and the four settings worth confirming in one place before you go live.