Last week Andrew McAfee wrote a blog post entitled Drop the Pilot wherein he discusses the challenges associated with piloting Enterprise 2.0 tools, and then arrives at the conclusion that we should abandon pilots altogether for such implementations and go as broad as possible right away. As much as I hate to, I respectfully disagree.
Call me a cynic, but when I hear suggestions which go against my gut and break some very fundamental principles, such as the need to proactively manage change as well as risk, I tend to stand back and watch others jump off the bridge to see what happens before i even think about stepping to the edge. As technologists, we are innovating at a rapid pace and paradigms are constantly shifting around us, but we need to be cautious about
I do agree that E2.0 projects pose unique challenges, one of which is that their effectiveness is often [but not always] tied proportionally to the number of users in the ‘system’ (e.g. with microblogs…try launching one with only 100 diverse people in your test group and see well it takes off. Hint: it won’t). I also agree that it’s been universally accepted that “pilot” = “small”, and that this characterization, by definition, hinders the chances of success for an E2.0 pilot. But the ‘aha’ here should not be that we should start throwing caution to the wind and launching new tools across our organizations.