Crowdsourcing is like herding cats. Everyone wants to go in their own direction – and seldom is it yours. Of course “crowdsourcing” is best added to a project that is already structurally sound w/ core stakeholders … we don’t always have that luxury. Thanks to Max Aetheling – for that bit of insight.
In my May 8 post, “Collaboration 2.0 … from ideas to action,” I discussed the chasm that exists between most collaborative thought efforts and the implementation of the results of these efforts. What’s needed is an “implementation template” to service as a guide to put these ideas and thoughts into play. Well after a few days of thought (sorry, just my own), I’ve come up with a rough out of this “template.” Here we go.
Before the actual collaboration begins – the stage needs to be set. It’s the job of the collaboration Founders to set the project direction before the rest of the collaborators, or Alliance, is brought on.
- Define the general premise of what the collaboration is trying to accomplish. This could be an idea, a solution to a problem, or even a general societal benefit.
- Breakdown the collaboration into components – or Milestones.
- Determine who you want on your team – your collaboration Alliance. Cast a wide net. You never know where talent will come from.
- Set up Yammer groups (or equivelent) for each individual Milestone. All members of the Alliance will be members of each groups. They can jump from “sandbox” (Milestone) to “sandbox” or stay primarily in one – whatever their preference.
- Set a “ship it” date, a deadline. Take advantage of emotional momentum (like the Middle East rebellions). After the deadline – project implementation starts.
- Create a narrative goal of what each Milestone should strive for. Tell a story. Don’t fall back on lists – make it real.
- Conduct an active ideas forum. The flow is the responsibility of the Founders. Moderate the activity and keep the goals always in focus. Use a proactive approach for inactive or lagging members.
- Once each Milestone narrative is set, then the Alliance is to breakdown implementation needs, timetable and determine who will occupy leadership, or Driver positions for each Milestone.
During the project formation the following issues need be addressed.
- Total resources needed – things, talent (not money)
- What resources needed do we currently have – and how compensated
- What additional resources needed do we not have – how compensated
- How will the additional resources be obtained and by who