The Wayback Machine - https://web.archive.org/web/19970208052241/http://www.compumentor.org:80/cm/mentors/handbook/handbook3.html
CompuMentor Mentor Handbook

Mentor Handbook- Chapter Three
Working with Nonprofits


Nonprofit organizations are usually long on heart but short on funds. Staff members are often idealistic but overworked, and may have a high turnover rate. While npos have many of the same computer needs as businesses (word processing, databases, accounting), they also have special needs such as the management of volunteers, tracking of donors, frequent mailings and fund accounting. Here are a few points to keep in mind:

Nonprofits Are Typically 'Cause' Motivated.

This means they are usually organized around a social issue, such as homelessness or health. The staff and volunteers are doing this work because they are committed to 'the cause'. They don't expect (or sometimes don't want) to become computer experts. Have patience in dealing with people who aren't quite as technical as you may be. Learn what you can about THEIR work and put things in a context they can understand.

If you are aware of where your project stands relative to the npo's mission (and usually, budget situation), you will better understand why the npo may be slow or unable to assign dollars and people to support you. While the computer help you're giving may increase an npo's effectiveness in providing services, it is usually NOT their end-product, which might be placing homeless families or providing hospice care or increasing literacy. Try not to get too frustrated if things go slowly.

Get a feel for the npo's 'culture': regular activities, decision process, rules. Meet everyone affected by your project. Define your role, and establish your working area.

Most Nonprofits Depend on Volunteers and Have High Turnover.

Some of the procedures you help set up may be performed by volunteers who are motivated but lack technical know-how and may leave in a few months. It's essential that you design your solution with this in mind - for example, by producing robust, simple procedures and code to withstand lots of new users; building modules with easy hand-offs; paying special attention to writing necessary documentation; and incorporating foolproof back-up methods.

Because npos function in an environment of limited resources and high turnover, it's extremely important to explain to one or more key staff members what you've done - and why - so there is someone who knows your documentation and can provide continuity for newcomers. Otherwise, in this environment, there is a good likelihood that your work will be used incorrectly - or not at all!

Most Nonprofits Have Very Limited Resources.

They may not be able to simply purchase needed software and equipment; their focus is on necessities, not the latest technology. And what they are able to purchase is usually on a piecemeal basis - fully dependent on the timing and the types of available gifts and funding rather than an integrated information technology and management plan.

Much of the hardware you will see is donated, often pre-owned. You might believe strongly that better hardware or software could be cost-effective over time and that you would be doing them a real favor by pushing the npo to invest. But that investment just might not be possible and you will have to work with what there is. So if new technology is needed, create a basic proposal and be prepared to cut it, spread it over a longer time, or find ways to help fund it. Expect the limited resources to challenge your creativity!

Nonprofits Operate with a Board of Directors.

You may recommend a computer or software purchase and be told that it 'has to be run by the board' and the next meeting is a month or two away. Be patient, particularly with small groups, since board approval is often required for significant purchases or procedural changes. While you're waiting, prepare the case to support your recommendation and help the right person get ready to present it to the board.