Ever wonder why there seems to be such a big gap between non-profits and technology? It’s a popular topic with ADB (big fans and believers in the wonders of great design and tech for nonprofits that we are), but Ayça Akin at Core 77 recently took a more personal look into the phenomenon and suggests that “differences in how designers, technologists, and nonprofits see each other (and themselves) is at the heart of the problem.” Akin held interviews with over thirty “designers, geeks, nonprofits, (and hybrids between the three), in order to identify the source of these communication breakdowns” and highlights the answers in the article Good For Nothing? Why Nonprofits, Designers, and Techies Can’t Talk to Each Other.

Some of the most interesting perspectives from the designer:

Nonprofits are too busy moving from crisis to crisis, unable to invest in the learning curve needed to learn how to use available tools; tailor-made solutions involve more troubleshooting than non-profits can afford; volunteers are unable to offer long term help needed; and there’s a feeling that some of these groups are impoverished except for passion.

There is a general feeling that most nonprofit employees are rich in knowledge and passion for their group’s mission, but not much else. It’s interesting that there is a stigma attached to being on the technical side of things, and a feeling that if you aren’t working directly on programs, you aren’t “in the trenches,” and are likely “less of an expert on the issues.” (Here it’s worth mentioning that language can particularly befuddle: For nonprofits, “program” means initiative; for architects it means layout; for software engineers, coding. There really can be different languages on the table here.) This kind of prejudice is obviously detrimental to progress, but recognizing this kind of territoriality is essential to understanding the various stakeholders.

From the Techies:

Nonprofits are high maintenance, wanting maintenance all the time when developers want less long-term commitment and diversity in clients; many nonprofits don’t understand what the realization of their ideas requires in terms of tech and implementation; techies don’t always want to be saving the world; and there’s often confusion about scope and value

Many techies remark that when approached by a nonprofit with a particular need, it’s rarely clear to them what that need exactly is. From the other perspective, when a volunteer approaches a nonprofit, they often encounter resistance because the nonprofit “can’t recognize when you’re offering them something useful.” This represents a gap both in project definition and perceived value—absolute basics in any work engagement. Is there any wonder difficulties arise?

And finally, nonprofits:

Growth is a luxury and, amazingly, many nonprofits seem focused on maintaining rather than growing; There’s no time to think or explore new ideas (for lack of resources and focus on keeping afloat); and finally, technology is a big, scary monster.

Most nonprofits are confused about technology—what it really is, what its potentials are, and what their own capabilities might be in managing it. Nonprofits are often unable to understand the different language that “techy people” speak, and this leaves them vulnerable to not getting what they want, paying too much for what they get, and not being able to maintain tech-dependent tools on their own. Fear is an overriding factor here, and helping non-savvy groups understand design and technology systems is the best way to turn them into sustainable partners.

Of course, there have been successful projects like Neighborhood Networks and Many Eyes that are empowering communities and Open Planning Project TechSoup, CivicSpace, and Drupal that are addressing the lag of tech for non-profit issues by offering open web tools. But while some of the problems above are generalizations, there’s no doubt they’re common and highlighting them encourages a good long gander at how the disparate groups (self reflection included) operate to pinpoint problems and misconceptions for the fixin’. Know thy enemy. Maybe the answer is an intermediary b/w tech and design volunteers and the non-profits they’re working with–something like a consulting company or creative manager. Or maybe it’s just about getting more alternative funding for non-profits to hire the designers and programmers they need. Any readers out there working on design for non-profits? I’m sure your thoughts and insight would be appreciated (and we know you’re good at problem solving) so get thinking. It’ll just make it easier on everyone.

via: Core 77