I spend a fair amount of time presenting our cloud vision and technology to our customers. In thes conversations, we often end up talking about transformation and the people and process angle of this transformation. Sometimes I feel my role is that of a Cloud Pyschiatrist, and not a technologist.
Often he conversations turns towards managing the fear of change, the anger that other people don't get it, the exasperation with customers that demand impossible service levels, don't pay and yet are not smart to know they need help.
And the myriad of policy changes needed: Is a patch a change and does it need to go to the CAB? (yes,no). Why is that user running his CPU at 100%? Is that other user even looking at box, because it's running at 3%? Will we run out of capacity if provide self-service?
What about security? What about security? Is it insecure?
And so goes another day at the Cloud Psychiatrist's office. Change is hard. That cheese ain't going to move itself. So a healthy dialog about change is required. And that's something, we can help with.
And remember, anxiety about change is normal. Be a cheese mover, not a cheese chaser. Because that cheese ain't gonna move itself
After seeing a number of these promising beginnings turn into stalled launches, my friend concluded that some kind of organizational anxiety was preventing them from taking concrete steps. He believes a "defogging" service designed to help IT organizations clearly understand their options would help them move forward with confidence.
His experience mirrors my firm's. At speaking engagements, I interact with people who are intellectually convinced that aggressively moving toward cloud computing is necessary, but seem hesitant and even confused about what to do