I’ve been reading and thinking a bit about “collective impact” lately. (Here’s the seminal article introducing the buzzword.) It’s a solid, mostly-common-sense framework for thinking about collaborative/coalition efforts. There are five elements that define a “collective impact” approach:
- Common agenda. If you don’t have a shared vision for change, you can’t really expect to collaborate effectively.
- Mutually reinforcing activities. Successful collaborators need to coordinate their activities, play to their strengths, and know their role in the larger effort.
- Continuous communication. If you don’t communicate regularly you can’t hope to build enough trust and shared language to collaborate effectively.
At this point, you’re probably thinking, “Jon, why are you wasting my time with such obvious folderol?” Most coalition efforts I’ve seen fulfill these first three conditions pretty well. Hang in there, it’s the next two that are the most interesting:
- Shared measurement systems. Hmm, now we’re getting somewhere. Collective impact suggests that collaborative efforts need agree on a shared set of indicators of success and the systems for monitoring and reporting on those indicators. Without shared indicators, collaborators have no way to really know if they are succeeding or failing, and no feedback systems that allow them to “course correct” as needed.
- A backbone support organization. Proponents of collective impact assert that successful collaboration efforts need to have a strong, staffed organization at their center, in order to run the collaborative process with sufficient intensity and focus to drive it forward in the face of distractions. It’s not clear to me whether they think a strong “lead coalition partner” fulfills this condition or not. (I suspect not.)
It’s these last two points where most collaborations falter, and probably not concidental that they require sustained, long-term resource commitments. How do collaborations you’re involved with stack up?