Step 1 : Check Awareness
Are they aware of it? if not then communicate and make them aware.
Step 2 : Check Objectives behind Development of the Tool
- Productivity Improvement
- Process Improvement
- Performance Tracking/Visibility
Also check if there are any conflicts such as
- visibility improvement but decline in productivity
- Improved productivity but lesser visibility
Step 3 : Check whether these objectives are met
if objectives are met for the team ?
- if yes, communicate and benchmark with existing
- if partially met, then try to ask for adoption with rest things to be deliveded in pipeline
Step 4 : objective are met but resistance to adoption ?
- either due to usability/ease of use/training needs/learning curve
- due to increased workload. we may need steps to reduce the workload/normalise
- more staff not in our hand
- more case on automation of the tool
- automate cases that are incerasing workload eg. approval and review flows
- reduce monitoring cases from product give notification to time critical thangs
- bulk actions supports
- Or it can be a typical change management case
- workshops/benefits/deadline for forced adoption/ escalation from leaders
- post adoption
- check usage
- verify if all existing tasks process that product was supposed to replace are taking place in product
- how to measure?
- quantitative data eg no of tempaltes created before and after product
- usage summary
- dau / wau / mau as per personas - approvers, reviewers, project or tasks owners
- no of customer bugs discovered - qualitative measure
- regular feature request/ bugs from customer is good measure of adoption