Revised with new information as of June 1, 2005


 
Introducing New Technology Successfully into an Agency
and
Why Your Organization Needs a Technology Plan

 
Change is stressful. Good or bad, it adds tension to any office. Throw the word "computer" or "upgrade" or "Internet" into this equation, and stress can skyrocket. Plus, mission-based organizations (nonprofits, non-governmental organizations or NGOs, public sector organizations, civil society organizations, etc.) are often facing intense, even do-or-die deadlines -- so the stress of dealing with computers can sometimes seem too much.

Introducing or adding computers to a mission-based organization, or upgrading software or hardware such an organization uses, will change the way staff at the organization access and manage information -- for the better, you hope. But without realistic expectations and a thoughtful strategy, a new system can create as many problems as it is supposed to solve.

 
Contents:

 

 
Your Agency Needs a Technology Plan

No matter what an agency's mission is, no matter what size an agency's staff or budget, no matter who an agency serves -- your agency needs a computer and Internet technology plan. Just as you should do a critical analysis and form a strategic plan for your fundraising plans, your staffing needs and your program activities, you need to evaluate your technology needs and create strategies to meet those needs. How your organization will access and use technology will effect just about every function of your agency, in fact.

If you choose not to create a technology plan, you will find yourself in a constant state of reactive crisis management.

So there!

At the Philanthropy News Network's "Nonprofits and Technology" conference in Seattle in January 1999, the executive director of CompuMentor told attendees that technology plans are more than just hardware and software wish lists. They can help nonprofits:

He cited a 70/30 rule for technology funding used by many large companies and organizations: For every $1 budgeted for technology, 30 cents would be used for hardware and software purchases, with the remaining 70 cents used for training and support.

 
Reasons to Computerize or Upgrade a System

Augustine "Tino" Paz, Network Development Specialist at Orlando's Community Services Network, made this insightful observation on CUSSNET (Computer Use in Social Services Network Internet discussion group):

David Arons of Tufts University added during this discussion: The first step in introducing a computer technology or upgrading/changing a computer system in your agency is exploring the "whys." In the excellent Guide to Automating I & R Systems: Automating Information and Referral Systems for the Non-Profit Community (published by CompuMentor, BUT NO LONGER AVAILABLE), several reasons to automate are cited: Clinton Jones of South Africa cited this formula on the CUSSNET group for introducing or changing technology during a discussion on "Planned Change vs. Rapid Development"

Included in his post was an example of this forumla in action.

Return to Table of Contents

 
Disadvantages and Risks

Any kind of change or upgrade can at first seem more work than it's worth. That in itself can make introducing computers or upgrading technology seem not worth the effort. Also, there's

Return to Table of Contents
 
Staff Buy-In

Staff and volunteers may tell you they have been doing just fine without computers or the Internet (and maybe they have!), so why computerize systems and data? They may tell you that whatever version of software they use meets their needs and it took an enormous time to learn and upgrading will cause more trouble than it's worth. Or, they may have unrealistic ideas about the technology -- that computers, a new software package or the Internet will instantly and effortlessly raise more money for the agency, or improve staff and board communications, for instance.

Many agencies invest considerable resources in computer hardware, software and staff training for computerized systems that then end up being under-utilized and failing to live up to their vast potential, because the staff had unrealistic expectations for the technology, or they never bought in to the idea of the technology in the first place.

The key to worker acceptance seems to hinge on the following factors:

  1. User-friendliness of the new system.
  2. Clearly identifying the benefits of the new system to those who will use it.
  3. Training and hands-on practice with the specific application.
  4. Clear commitment by management to support staff during their learning curve.
  5. Clear and communicated commitment by management to support the introduction of the new system.
  6. Timely hardware/application support.
  7. Clear expectations by management that staff are expected to use the new system.

Most who have commented on this subject via various Internet discussion groups feel that forcing technology on someone outright doesn't work. It's not efficient, creates even greater tension around the use of the technology, and takes even longer for the system to work. Instead, the successful integration of a new technology into an agency requires good and ongoing communication, long-term commitment by the entire staff, monitoring, support, intervention and patience.

One person on CUSSNET (Computer Use in Social Services Network Internet discussion group) noted that, at the time of his post (July 1997), California was installing a state-wide information system called Child Welfare Services/Case Management System (CMS/CWS). The system is comprehensive and covers everything from caseload listings, client history, placement and payment processes, contact narratives, management of court documents, service plans, state-wide search capability, etc. His story on the introduction of this system offers many lessons for anyone introducing a new technology, no matter what system it is computerizing:

Another participant on CUSSNET had this real-life example to offer, which also offers good advice regarding the introduction of any new technology: Another real-life example, this time from a reader on CYBERVPM (a discussion group for volunteer managers):

Still another CYBERVPM participant said:

Also see Being Fluent with Information Technology, an excellent document that will help you measure your success in getting your nonprofit staff up-to-speed regarding using technology.

Return to Table of Contents
 
Time for a Technology Moratorium?

This was a post to UP FOR GRABS, and it provoked a lot of discussion and disagreement. I agreed with it -- because, often, nonprofit and public sector agencies, particularly schools, will receive "upgrades" in the form of donated hardware and software, and the organization does not have the infrastructure, expertise or resources to utilize this donation. It ends up not working, or, at least, not meeting expectations of the donor, and the organization gets "blamed." Or, the school pours money and resources into equipment, but not into training and support and infrastructure -- and the results are the same:

 
Return to Table of Contents
 
Other Resources

Two Excellent Case Studies
In Effective Tech Use by Nonprofits

 
If any of the aforementioned sources no longer work, type in the original URL to archive.org, and you should be able to retrieve the original information.

These resources can help your staff with computer and Internet hardware and software issues (and for any links that no longer work, type in the original URL to archive.org, and you should be able to retrieve the original information):

For any links above that no longer work, type in the original URL to archive.org, and you should be able to retrieve the original information.

Information about CUSSNET and CYBERVPM, as well as other Internet discussion groups relating to nonprofits and technology, are listed here on this web site.

border

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:
          Jayne Cravens & Coyote Communications, a consulting service and online resource for mission-based organizations, www.coyotecommunications.com

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

border

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

The art work and material on this site was created and is copyrighted 1996-2007
by Jayne Cravens and Coyote Communications, all rights reserved
(unless noted otherwise, or the art is a link to another web site).