When to use it
At pilot launch, when use stalls or when a new user group joins.
Fields to complete
| Field | Your notes |
|---|---|
| Eligible tasks and total count | Add known information, your judgment or an open question. |
| Access, attempts, completion and repeat use | Add known information, your judgment or an open question. |
| Reasons for non-use, abandonment or refusal | Add known information, your judgment or an open question. |
| Benefits and added work for each role | Add known information, your judgment or an open question. |
| Evidence of barriers and proposed changes | Add known information, your judgment or an open question. |
| Training, support and escalation contacts | Add known information, your judgment or an open question. |
| How feedback changes the product and workflow | Add known information, your judgment or an open question. |
| Results that justify expansion, revision or stopping | Add known information, your judgment or an open question. |
Example entry
For overnight non-use, check access and available takeover support first. Run an overnight support test and count eligible tasks completed, rather than logins alone.
From the fictional Beichen case. This shows one way to write an entry; your analysis may lead to a different choice.Check your work
State which result would show the change did not help, and have operations confirm support is feasible.