Adoption improved during launch, then declined. What should we do?
Unsustained behavior changeCheck whether support, ownership, incentives, and process quality continued after launch attention ended. Look at actual task completion and renewed workarounds, not only logins. Assign ongoing improvement ownership and correct the reasons people stopped using the intended process.
What to do now
- Compare current behavior with launch outcomes
- Investigate recurring barriers and workarounds
- Assign ongoing improvement and support owners
- Review sustained use over an agreed period
When to escalate
The intended benefits are no longer being realized.
The business process owner and change sponsor
Example
Monthly process reviews catch a growing approval delay before users return to email requests.
Mistake to avoid
Treating the launch campaign as the end of organizational change.
Prevent a repeat
Measure successful use of the intended workflow and resolve recurring barriers instead of relying only on attendance or logins.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Resources
Assign role-specific readiness and feedback actions, keep reviewed job aids with the project, and record accepted operating responsibilities. See the platform
Related cases
- The organization rewards the old behavior while asking for a new one. What should change?Misaligned incentives
- We launched the system, but staff still use spreadsheets. Why?Unresolved adoption barriers
- Users request a change during training. Should we implement it immediately?Late adoption feedback
- A metric improved after we changed its definition. Can we claim success?Broken metric comparability