Designing Impact

Recently I shared my suggestions about what learning leaders should think about when considering implementation of Web 2.0 features within learning solutions. It was written to learning leaders who have already made the decision to implement features that use cloud computing. To help with context, here’s the definition of cloud computing.

While reading the February 2010 CLO mag (from the cloud mind you), I ran across a great article, “Learning in the Cloud” by Agatha Gilmore about what learning leaders can takeaway from the cloud computing trend. It’s a great read. Mostly written for learning leaders who have not already made the decision to implement features that use cloud computing, she mentions a 2008 survey by IDC that had some intriguing data about perceptions related to the challenges of ascribing to the cloud model. Since we’re in newly minted 2010, I wondered if there was any other survey information about adopting the cloud model. Here’s some most recent surveys for starters: 2009 Survey of Cloud Computing 2009 Cloud Computing Survey Results | F5 Networks
I didn’t find that much. Do you have any share?

Who cares? you might be whispering… as you read this from… the cloud. Before you surf away…er…or float away….allow me to make my point.

Trying to influence more use of Web 2.0 technologies in learning solutions within your company or organization? Have you brought up cost-efficiency in the conversation? Using virtual apps and platforms to reduce costs in delivery, time away from work, and production could yield BIG numbers (beyond the upside of likely increasing retention and motivation of learning using built-in Web 2.0 features).

There are many ready-made apps and platforms that are delivered over the internet by a service providers that include ready-made, scalable Web 2.0 technologies. (ie, hosting, project management infrastructure packages, storage, databases, wikis, Twitter, YouTube, Facebook, Google Apps, just to name a few) Not to mention blended models like cloud app + mobile phone, cloud app + laptop or pseudo private cloud platforms like SharePoint.

Here is some info and perhaps insight that may help build your case.

1–Do a “scare check-in” with learning leaders and give them some perspective.
According to Andrew McAfee’s research mentioned in the article, leaders worry that someone is going to giveaway company secrets, criticize the company, give medical or legal advice that’s going to go public. McAfee searched instances where this actually occurred. None. Apparently it’s a myth.

2–Mitigate security issues by telling everyone the rules of the road.
Ray Cross, within Agatha’s article, mentions the importance of putting standards and policies in place to ensure everyone understands what’s secret and what’s not. I would add taking time for leaders to agree upon what is appropriate and what isn’t as well. I’ve had great success visually defining in-bounds and out-of-bounds guidelines and scenarios via short tutorials so all understand clearly.

3–Make a business and integration roadmap.
Bob Moul, of Boomi (cloud platform) makes some great points:  A–Define how your business will continue to run using the new app, platform, or infrastructure. B–Know how the cloud applications will work together with existing technology.

4–Build your relationship with IT and conduct a pilot.
Mark Filley of Lombardi Software, mentions work with IT to understand what users will face as they begin to use the new app or platform. What security protocols might they need to work around? I would add run a pilot with a group of typical users to see what kinds of issues arise.

5–Train the heck out of ‘em AND have it searchable by need.
Everyone who plans to use the features, apps, or platform needs quick, just-in-time, always-on-demand, confidence building training. Period.  Think small bites (5 min or less) of learning (videos, tutorials, screencasts or recorded webinars) available online searchable by common needs users would have as they learn how to use the app or platform. Poll the pilot group and ask them what their greatest needs were as they learned to use the features, app, or platform.

6–Uncloud your cloud talk.
Cloud apps or features don’t have to be public. That might ease fears about security. Here are some definitions according to the NIST (below) and wikipedia:

Private cloud. The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise.

Community cloud. The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise.

Public cloud. The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud. The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

What would you add?