While cloud computing is a hot topic today, how should users approach this nebulous resource? The most important step is to recognize the key dynamic of cloud computing is shifting demographics. A good way to get a sense of what is happening in your organization is to:
- Conduct a meeting about your organization’s posture on cloud computing with your most senior managers – preferably those over 40.
- Conduct a meeting about your organization’s posture on cloud computing with your least senior managers – preferably those under 30.
Make sure lawyers over 40 and under 30 are present for both meetings. Then try to reconcile the two. The older group will show conservatism and a huge concern for security. The younger group will demonstrate increasing comfort with Web 2.0 tools and business models and want to actively embrace them.
While cloud computing holds great promise, for many traditional applications it’s too young. Cloud computing requires new stuff including hardware, file systems, data protection techniques, and security approaches. Note that elastic computing such as Amazon Elastic Compute Cloud (EC2) is actually more interesting but it should only be used for experimental purposes
Nonetheless, by all means, increase awareness and experiment with cloud computing. Explore available services; investigate file systems such as OceanStore. Don’t let information risk management policies cut users off from experimenting with new services. Design processes to allow this to be done safely rather than not done at all.
Ultimately this will support the goal of getting leaner faster. Applications that should be considered early in the phase include remote backup, archiving (notwithstanding the privacy and security concerns), email and social networking activities.
Also take note that it’s hard to remove applications from their storage so they either both have to go into the cloud or they should be avoided until visibility becomes clear.
Action Item: Experiment and remember the old Roman advice -- festina lente (hurry slowly).
Footnotes:
