Skip to content
By use case · AI adoption tracking

Track AI adoption across teams

Connect assigned access and observed use to repeat workflows and completed work, so you can see where adoption stalls.

Talk to Oximy
The records behind the decision

See where adoption stalls.

A seat list describes access, not adoption.

Where does the rollout stop between a seat and finished work?

Four weeks, one team
Records behind the four weeks
Seat listSeat list400 seats
Identity sign-ins260 people
Tool activity140 repeating
Work itemsWork items90 matched
OximyOximy groups four weeks of activity by the workflow it returned to.
Activity by workflow400 seats assigned
Week 1Week 2Week 3Week 4
Maintenance fixesNamed workflow0Repeat
Architecture questionsUnresolved context0Isolated
Assigned accessNo observed workflow0Idle
How to read the evidence

Different gaps need different actions.

Keep each adoption stage separate.

From access to useful workFour stages
Access assigned
Activity observed
Repeat workflow
Completed work
Adoption is the stage that reaches work90 of 400

What counts as repeat use?

Keep the four stages separate: access assigned, activity observed, a workflow that repeats, and completed work linked to it. A single percentage hides which of the four the rollout stopped at.

Work matchOne workflow, four weeks
50 of 140Repeat, no work matched
Check the business record before judging the workflow.

Does a missing work match mean AI was unused?

No. Usage and completion can sit in different systems, or a source may be outside the agreed scope, so keep missing evidence distinct from observed non-use.

Where three teams stopOne quarter
Customer support30 of 120 repeat weeklyEnable
Sales9 of 180 repeat weeklyExpand
Finance12 of 60 ever signed inReallocate

Does every team stall in the same place?

One team runs a weekly workflow with most of its seats idle; another opens the tool and returns to no task at all. The next change should address the stalled stage rather than ask everyone to use AI more.

Next step