This paper examines organizational change through a case study of a nonprofit community action agency transitioning from an outdated DOS-based grant and fund management system to a modern Windows-compatible platform. Drawing on interviews with the agency's CFO and frameworks from Kotter, Deming, and Senge, the paper identifies key stakeholders, assesses their readiness for change, and evaluates the leadership approach guiding the transition. The analysis highlights critical gaps in vision, team alignment, and top management commitment, while emphasizing that successful technology change requires disciplined process management, cross-departmental cooperation, and a shared organizational vision rather than a desire simply to get the project over with.
Change can come in many forms — from the reassignment of duties and roles within an organization to the challenge of a corporate takeover. Among the most daunting changes that affect people and organizations on many levels, however, is the transition away from a legacy computer system that a company and its staff have relied on for years. While companies can operate on the same systems for extended periods, eventually change comes to all systems as new technology becomes incompatible with older legacy products. Resistance to these changes is high, and a genuine addiction to the "way we've always done it" mentality can develop.
This case study examines a non-profit community action organization and its need to update an outdated DOS-based grant and fund management software system to a Windows-compatible platform. The case illustrates how deeply ingrained habits, leadership gaps, and resistance to change can complicate even a well-intentioned technology upgrade.
The organization at the center of this case study is a private, not-for-profit charitable organization that began in 1964 as a grassroots effort to improve the lives of low-income children, families, and individuals in its local community. Incorporated as a 501(c)3 in 1966, it is one of over 1,000 Community Action Agencies (CAAs) in the United States, Puerto Rico, and U.S. Territories. Each year, a consumer mix of over 6,500 households and individuals come to the organization for assistance. The agency administers over 16 programs annually, tailored to the needs of an ever-changing community, and operates 15 sites in the area — ten of which are Head Start and other after-school programs operating out of donated space at local schools.
The organization's mission is to partner with low-income households and individuals as they develop to their full potential. Its departments include Head Start, Energy Services, Family Resources, and Housing Services. The Administration Department consists of an Executive Director, a Human Resource Director, and a Chief Financial Officer (CFO). The CFO oversees a finance department composed of a Fiscal Coordinator, a Payroll/Benefits Specialist, and a Senior Bookkeeper.
The finance department is the primary stakeholder in the change and upgrade to a new financial management software system. The Fiscal Coordinator is a relatively new staff member of two years with an information systems background and is responsible for leading the change process. The Payroll/Benefits Specialist has been with the agency for five years. The Senior Bookkeeper has been with the agency for 20 years and has worked exclusively on the legacy software for 14 of those years. A change consultant was asked to evaluate the situation and interviewed the CFO about the transition process.
1. Who do you see as the stakeholders for this change?
The Senior Bookkeeper and Payroll Specialist.
2. What are the short- and long-term goals of this project?
Short-term: to be able to access records from past and current years, to make the changeover as smooth as possible, and to remain on track with all usual financial duties such as payroll and vouchering for grants. Long-term: greater flexibility in analyzing and inputting data into the system, and less time trying to pull together disparate data for presentations.
3. What will keep this change project on track?
Putting key players in the right places. The Fiscal Coordinator will serve as the project leader for the finance department, and the other staff members will need to be trained and kept informed of all activities prior to the actual changeover.
4. Have you analyzed the positive and negative viewpoints of each stakeholder?
After reviewing the situation, most of the people involved in the change appear fairly positive about it — except for the Senior Bookkeeper, who does not adapt well to change or to computers in general. This transition will also significantly affect her established way of doing things.
5. Do you see any pitfalls on the horizon?
The primary concern is any change in personnel during the initial stages of the changeover, as well as any disruption to the normal flow of agency operations.
6. What strengths will you use to pull this project together?
Creating a functioning team with a supervisory leader who has both the managerial skills and the technical knowledge to guide the process.
7. Do you feel that the management team has been positive about the change?
Yes — in fact, they have been wondering what has taken so long to move forward with it.
8. Do you envision staff changes during or after this process, and are contingency plans in place?
Yes, it is believed that the Senior Bookkeeper will leave. At this moment, no contingency plan is in place to address that scenario.
9. Are you looking forward to this change process?
Yes and no. Yes, because updating the software is necessary. No, because the current system does work adequately, and it will be a significant upheaval to change everything.
10. Are you more interested in the outcome than in the actual process?
Absolutely. The desire is to get through it and wait about three months for everything to return to normal.
"CFO's limited vision undermines effective change leadership"
"Deming's 14 points applied to agency-wide cooperation"
"Broader stakeholder inclusion needed for lasting change"
Always verify citation format against your institution’s current style guide requirements.