|
But Tim couldn't leave well enough alone. He came up with three ways to get Radio into MIT:
Centralized push. Have Sloan’s IT services folks set up a Radio Community Server and put Radio on every first year MBA’s laptop.
In the classroom. Have a few professors start using Radio as a knowledge sharing mechanism and put part of the class participation grade for their students in how well they use their weblogs.
From the grassroots. Have a few bleeding edge folks get their sleeves up and evangelize it.
How can we generalize this? Tim's three stages are natural levels of escalation.
A. User referrals.
"How did you do that?" "Oh, yeah. My Radio. Wanna see?"
Grassroots, subversive, and memetically savvy. Seed early adopters with the tool. Listen carefully for their hot buttons. Probe for their serious problems and experiment with how the tool makes things better.
Then plan your pilots.
B. Pilot projects.
Prove your solution works,
Learn the best ways to use it in this environment.
Discover which features and practices:
Generate the most perceived value,
Provoked the strongest positive emotional response
Stack the deck in favor of an early win. For example, Tim's picks for fertile pilot soil:
There are some classes, including the introduction to IT class, a few of the marketing classes, and a class being taught on virtual communities, with which Radio is a natural fit. You might get the professors on board pretty quickly, with the students doing exercises in Radio for a semester.
I'd also look for classes, and workplaces, where:
people work together in project teams,
freshness of external information (competitor and customer behavior) is important,
klogs can help overcome team member churning.
C. Standard deployment.
Software rollouts are well understood. Bullet proof deployment and use for newbies. Stimulate learning curve behavior, minimize life cycle costs.
I'm adding this to my Radio Klogging Kit for Managers. [klogs]
8:46:02 AM Google It! 
|
