Piloting you!

I had a lot of conversation today about pilot initiatives within a
larger institution. it seems as though in each project that I take
part in, there is reason enough to get a small group of (semi)
dedicated people together who will try something out and report back
on their success. Whether that is moodle, gmail, google sites, dimdim,
or ning; it seems as though there is never enough at stake to require
all users to jump on board initially. While this is good in a lot of
ways: less kicking and screaming, learning from mistakes with small
group is better, and less chance of falling flat on your face with
everyone watching. But, it is bad in many as well: no ensuring that
the pilot will go further, no urgency in rolling out to everyone, and
all pilots are basically representations of the person who creates
them.
 
This last point is what I would like to focus this post on. What I am
finding as I do more pilot initiatives is that I am trying to model
the pilot on my own practice and workflow. I am taking what I feel is
valuable and important and I am saying that others should feel the
same way. At the end of the day, I am piloting a larger and more
unwieldy version of me.
 
While it is flattering that others would want to help beta test me, I
am not totally sure how smart it is. I am not a typical user of almost
anything. I want to break things open and push them to do what I
envision, not what they were intended for. While I may have a good eye
for what others may need, I need people who aren’t using tools in such
ways to help design the pilots too.
 
I guess what I am trying to say is that I cannot pilot myself if I
want the pilot to actually do what it is supposed to: test whether or
not something will work for everyone. But, how do I ask those who are
less willing to try new things to become a part of a pilot. How do I
ensure that all voices are heard so that when things do go live, the
backlash from these users isn’t fierce enough to shut it down?
 
Easy question, right?

Posted via email from olco5’s posterous