
How does a small mission-based organization (nonprofit, non-governmental organization/NGO, public sector organization, civil society organization, etc.), with very limited resources and, often, a staff doing a LOT more than their job description defines, support its computer and Internet systems? Who solves problems? Who evaluates the system and suggests when or when not to upgrade? Who identifies training needs of the staff?
Who should be in this role? Ask the staff for their input -- often, there is someone on your staff doing this unofficially already. It could be the Development Director, it could be the Receptionist ,it could be a Teacher -- the person should already have an interest in this area and already at least dabbling in technology, either at home or at the organization.
Should you look for a paid part-time person, or could a volunteer fill the role of computer and Internet support person? Either route will get you the expertise you need -- but both routes probably won't get you the TIME you need. Volunteers are WONDERFUL, and I highly recommend them as great resources of help for your comptuer and Internet support needs. But do note that volunteers have many other priorities -- their paid work, for one. In an emergency, you may have to wait for the volunteers' other priorities to be taken care of before he or she can get to you.
The Virtual Volunteering Project has an excellent resource on how to recruit volunteers for computer technical assitance roles.
Here are tips on Finding a Computer/Network Consultant.
Tim Mills-Groninger, chair of the Technology Resource Consortium (TRC), Associate Executive Director Information Technology Resource Center (ITRC) npo.net in Chicago, and one of the wisest posters on the soc.org.nonprofit newsgroup says:
CRPs should be their own team within the agency, and have time to meet, learn, and do their support functions. When things are messy at CRP can work 1/2 time on support functions, when things are under control it more like two hours per week.
Next up the support ladder is the Computer Coordinator, often 1/2 time if there are around 20 computers in the office, full-time if there are more than fifty. This person takes the support problems the CRPs can't answer, does hardware configurations, troubleshoots the network (you_should_ have a network by now), manages vendor relationships, files all the lisencing paperwork, and basically does the infrastructure plumbing.
Next is outsourced technical support. No Computer Coodinator will have seen every problem - there just won't be the diversity of trouble in your shop until you pass a hunred or more PCs. Technical support providers see these problems all of the time and can offer solutions much faster than having your own staff futz around looking for the chance fix.
If there are extensive database applications you may want to think about have a DataBase Administrator or DBA. DBAs have the tricky job of coordinating the business uses of the database and all the "behind the scenes configuration and tuning"
Many of the TRC members can help you organize staffing and find qualified vendor in your community.
Also see these tips on Finding a Computer/Network Consultant.

Disclaimer: No guarantee of accuracy or suitability is made by the poster/distributor. This material is provided as is, with no expressed or implied warranty.
All Coyote Communications materials are works-in-progress. If you would like to add something to these materials, please contact me with your suggestion; if your contribution is used, you will be credited (unless you don't want to be). Please include your name, email address, web address (if applicable), the name of the company you represent (if any), and any other information you would like to share.
Permission is granted to copy and/or distribute a limited amount of material from this web site without charge to recipients if the information is kept intact and without alteration, and is credited to:

Please notify me if you intend to use these materials or to quote me.

my consulting services | about Jayne Cravens | return to home page |
contact me | linking to or from these pages