“If you bring the appropriate people together in constructive ways with good information, they will create authentic visions and strategies for addressing the shared concerns of the organization and community.”
In our work at IISC, we occasionally reference David Chrislip’s “collaborative premise” (see above) as a way of orienting people to some of the key components of effective collective and net work. Given our emphasis on effective stakeholder engagement and process design, we generally focus on the first two elements more so than the last around good information, which does not mean we think it doesn’t matter. In fact, recently I’ve been observing some interesting dynamics around the data conversation in various network building and collective impact projects that we support.
Invariably, it seems that there are those who are quite concerned about ensuring that a given collective effort has the “right data” and that people are being “rigorous” in their approach to problem/opportunity analysis and solution generation. While understanding the need to have and use good data, we also think that it’s important to ask the question – Data for what? People often say they want data to ensure that they are not making uninformed and overly subjective judgments. Understandable. Furthermore it is sensible to want to seek out a baseline to be able to measure progress as a change effort moves forward. This said, I see a number of pitfalls in what can sometimes become the drumbeat for data.4 Comments