David Stairs of the Design Altruism Project argues that many collaborations aren’t actually collaborative. In a sobering post, he notes that people want to set up a project to be the hub for collaboration in their field… often without checking who’s doing the same thing, or even using the same name. We’ve observed similar behavior.
Partly it’s about wanting to be at the center of things – and that’s natural. And partly it’s about not realizing just how much work is involved in making an online community. I’m not sure what the solution is. One possibility is the Wikipedia experience: perhaps what happened with Wikipedia is that it was a single project which gained a good reputation, gave a good experience to many contributors, was a clear concept to grasp (a free encyclopedia), and a broad enough scope to be of interest to many, many people.
This hasn’t happened to the same degree in architecture, design or sustainability, though we’ve made good progress on Appropedia – especially as we’ve come from a number of different projects and chosen to collaborate rather than compete.
“…And, you know, it’s all good, an orphanage in Sri Lanka, house inspections in Mississippi post-Katrina, a community center in Kenya… But I just got sick of it and had this idea that you should change the name of DWB to Designers With Borders. As in, maybe there should be some boundaries, some active awarenesses that we are unqualified, or unfit, or unable to work borderlessly.”
Not that we need to be changing names – just recognizing our limits. I can’t recall who said it, but it is our weaknesses that make us great, not our strengths, for our weaknesses lead us to work with others and create something greater than ourselves.
Pardon this meditation on failure. There are many encouraging successes to dwell on, support, and learn from, and we’ll continue to do that. A cautious recognition of where things go badly pear-shaped is one side of the coin of success, and we do well to keep both in mind.