Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and method
Define adoption through completed tasks rather than logins alone. Choose an action that represents value for each role and explain who had an opportunity to perform it. Someone who only reads should not be assessed like an order approver. Avoid turning product measurement into unnecessary individual surveillance.
Illustrative example
Illustrative example: twenty people open a tool, but only eight have assigned requests. Six complete their task without help. The report shows 6/8 for that journey alongside errors and unfinished requests. Dividing by twenty would confuse general access with a genuine opportunity to use the relevant workflow.
Acceptance check
Observe a test session for each role and compare recorded events with the actual task. Count retries within the same journey where appropriate. Accept measurement if it helps locate friction and improve training or interface design, without rewarding repeated clicks that fail to produce a useful outcome.
Key takeaways
- Measure tasks and opportunities to use the tool; logins alone do not demonstrate meaningful adoption.