« Competition for Academic Libraries (Hint: It's not Google) | Main | Building Branded Environments: examples from television »

January 31, 2007


Ryan Deschamps

I remember trying to get people to buy into email waybackwhen believe it or not.

Eventually, we needed to force people to access it. As in "this is your job folks. no excuses if you miss out on something important because you didn't check your email."

It's a hard balance between encouraging the freedom of collaboration and requiring people to do this as their job, but this is a situation where it appears people have offered a verbal "yes" to the project. If that's the case, they should be called on to participate: as in, "I didn't pay for this thing as a personal toy. It is a device that I believe will improve the way we serve the students."

If people don't participate, you don't only lose the $5/month, you lose all of the potential productivity and service quality that ought to have been gained by implementing the tech.

If you got the buy in from the upper-ups for this project, perhaps you can get some help from them too.

You could also set some mini wiki projects in an action plan (get tasks, names and dates!). That might help get things started as well.

In the end, if people didn't want to participate, they should have said so when you did the demo.


Here is a brainstorm about what could help, the link is about pattern languages for adoption:

weblog post

Best, Mark

The comments to this entry are closed.

My Photo
Blog powered by Typepad
Member since 05/2006