Saturday, 14 September 2013

10 steps to make cloud technology initiative successful

1. Any technology is as good as user adoption

Team readiness and organization culture is critical when defining technology initiative

2. Create bandwidth to drive change

Energy required to drive and sustain a change is significant. Management commitment is critical. Identify the brightest team member to drive and manage technology development until adoption

3. Re-engineer the processes before selecting technology

Processes automation should drive your technology assessment 

4. Involvement brings accountability

Create user groups to participate in the process of development, share responsibility and participation brings joy and reduce risk of failure 

5. Execute proof of concept (POC) but with a well defined strategy

Cloud solution can be easy to register and even easier to opt out, but drive pilots with stronger approach. POC is more critical than the final roll-out. Innovate quickly and drop-off even quicker if it fails. Choose a technology which has lower risk of experiment

6. Set-up baseline for success

Define success factors (business aspects) upfront along with project success factors and always gauge progress with these baselines 

7. Speed of success

Choose expert or service provider to drive your technology roll-out to crash time, reduce risk and improve effectiveness. Choose a partner who has the knowledge, industry best practices and who can connect with your business and fit your business culture is critical. 

8. Roll-out of technology

Share value to users, create gamification and incentive programs to motivate users, stronger awareness / hand-holding programs, structured adoption and business reviews and listen to users feedback are important 

9. Strong well define review to create / push positive change 

This is the most critical step to make your cloud initiative a success. Reviewing quality / quantity of data and system utilization is critical. Review the data and trends not the system. Until stability (for about 4 weeks) involve a system admin during review. System admin can support if there are system gaps so that system gaps does not come in the way of an effective review process. Define 30, 60 and 90 days roll-out plan. Train and re-train at frequent intervals, conduct internal certification programs, identify internal early stage adopters and publish their internal CRM success (used cases) for creating right energy among other user groups.

10. Business is dynamic and so as your technology

Sustaining any initiative is key to success of any initiative. Constantly strengthen technology as the business evolves.

Simple technology is a good formula for greater success. 

No comments:

Post a Comment