How To Know If You Need Better Systems

Introduction

What is one thing that most people can agree on? Their favorite football team? Their ideal vacation spot? Their political beliefs (probably not)? None of these. Most people can agree that they don't like change. I'm not a big fan of change whatsoever, either. I lived in the same place my whole life before coming down to Florida for college, and it's still an adjustment. I like my routines and the way that I do them and don't like switching it up for any reason.

The same is true when it comes to operating an organization. People get so comfortable with the processes and systems they have in place that they never feel the need to innovate, to pursue something new, or to even admit that what they are doing is not efficient. I've seen these problems constantly in the nonprofit world, especially. This is due to mostly long-standing ways of doing business and a refusal to look at any alternatives because the present system has gotten them where they are today. In some cases, there really isn't anything more to be done because at the end of the day, the people need to use the systems effectively to do their jobs well. But in most cases, there is a lack of enthusiasm to change up what is already going for the organization because of the work that needs to be done to ensure it can be implemented effectively.

What we're going to be talking about is how to tell if your organization qualifies as one of these organizations and some subtle, daily practices to identify that usually go unnoticed by team members and leaders.

What I Would Look For First

You may need better systems when routine work keeps taking too long, follow-ups get missed, information lives in disconnected places, or one person has to remember how everything works. I would start with the process causing the most trouble, understand where it breaks down, and then decide whether it needs clearer responsibilities, better use of existing tools, or something new.

Routine Work Taking Longer Than Usual

Doing the same thing every week over and over again may seem like a necessary part of business, but that's not always the case. This is where I see a lot of organizations not improving their systems because what they do right now technically works. Why change anything up if it's worked for years? I hope that we as a society don't actually think like that, because it would be detrimental towards human innovation and we will lose our zeal to improve ourselves and our society as well. Just because it has worked, doesn't mean it shouldn't change.

If someone is doing work that is the same every week, which steps actually need a person's judgment? There are plenty of automatic workflows that can help with basic tasks like routing volunteer requests to the right person, sending out newsletters to contacts in a database, or preparing reports of weekly activities for the board. This is all without the use of AI as well. An organization doesn't need to implement AI and allow it to have complete control of the organization's systems. In fact, I highly recommend against that train of thought. Manual data entry, follow-ups, and routine task updates are good places to look for automation that can give staff more time for work that needs a person.

People and Opportunities Are Getting Missed

There are thousands of different software applications that can be used for following up with people interacting with your organization. Recent data shows, however, that many churches and nonprofit organizations are missing the follow-ups that are vital for maintaining good communication with potential new members and donors. Invite Welcome Connect, a nonprofit dedicated to helping churches build connection, received 743 complete or near-complete survey responses from people associated with Episcopal and mainline Protestant congregations in the United States and Canada. Follow-up and relationship-building received 401 responses as an area needing support. (Invite Welcome Connect, 2026)

This is a significant problem because following up with somebody is often the first step toward building a lasting relationship. Think about a family visiting a church for the first time, filling out a connection card, and expressing interest in becoming members. What happens next? Does somebody receive a notification to follow up with them? Is there a process that ensures their questions get answered? Or does their information sit in a spreadsheet until somebody remembers to check it?

The same can be said about nonprofits working with donors, volunteers, and potential community partners. There are countless opportunities that can be missed simply because nobody was assigned the responsibility of following up. This is where a CRM (Customer Relationship Management) system becomes incredibly valuable. Instead of manually keeping track of every interaction, organizations can automatically create follow-up tasks, notify the appropriate team members, and keep a record of previous conversations. The goal shouldn't be to automate the relationship itself, but to make sure the relationship doesn't get forgotten because of poor organization.

Disconnected Systems and Disorganized Information

This is probably one of the most common problems I come across when discussing technology with nonprofits and churches. There is a big difference between having software and actually having a system. An organization might have software for collecting donations, another platform for managing volunteers, Google Sheets for organizing contacts, and a separate application for handling communications. There isn't necessarily anything wrong with those individual programs, but what happens when none of them communicate with one another?

A 2025 study conducted by IDC for Unit4 found that 39% of the 70 larger nonprofits surveyed considered gathering and reporting financial information cumbersome, while 45% were still using manual processes for policy, legal, and compliance workflows. (Unit4, 2025) These organizations are spending valuable time transferring information between applications instead of actually using that information to improve their operations.

I believe this is one of the biggest misconceptions about improving organizational technology. You don't always need to purchase more software. Sometimes the best thing you can do is connect the software you already have. Having one reliable place to access important information, with systems automatically sharing updates behind the scenes, can eliminate unnecessary work and give leadership a much clearer understanding of what is happening throughout their organization.

Your Organization Relies Too Heavily on Certain Employees

This is another problem that often goes completely unnoticed until something goes wrong. Think about the person in your organization who knows how everything works. They know where the important documents are, how to access every software platform, how to organize events, and who to contact when something needs to get done. That person is probably incredibly valuable to your organization, but what happens if they leave tomorrow?

NTEN conducted an analysis of technology assessments from nearly 1,300 nonprofits and found that organizations without dedicated technology staff averaged risk flags on almost 60% of their assessment responses, compared with 28% for organizations with more than ten technology staff. (NTEN, 2026) While this doesn't mean every nonprofit needs a full-time technology department, it highlights the importance of having adequate support and clearly organized processes.

If the success of your operations depends entirely on one person's knowledge, then you don't really have a sustainable system. You have a dependency. Organizations should be documenting important workflows, assigning responsibilities, and ensuring that information is accessible to the appropriate employees. This doesn't have to be an expensive project. Sometimes something as simple as a shared knowledge base and clearly documented procedures can make an enormous difference.

Is Your Technology Actually Helping Your Mission?

Finally, I think every organization needs to be asking itself whether the technology it currently uses is actually producing the results it was purchased to accomplish. According to Barna's 2026 State of Church Technology research, 94% of surveyed church leaders agreed that technology helps their church fulfill its mission in today's digital culture. (Barna, 2026) However, believing technology is useful and knowing how to use it effectively are two completely different things.

How much time are your employees saving? Are your follow-ups being completed? Can leadership access accurate information without having to ask three different people? Are your volunteers better organized? These are the kinds of questions that determine whether your technology is actually making a difference.

I see a lot of enthusiasm surrounding Artificial Intelligence right now, and I share that enthusiasm. But implementing AI into an organization that doesn't have structured processes or organized information is not going to magically solve its operational problems. Before purchasing another subscription or implementing another automated workflow, organizations should first understand what they are trying to improve and how they are going to measure whether it worked.

A Practical Check for Your Team

Before deciding what to change, pick one recurring process and walk through a recent example with the people who actually do it.

• Write down what starts the work, who owns it, and what counts as finished.
• Follow the information from the first form, email, or conversation to the final record.
• Mark where someone has to copy information, chase an update, or rely on memory.
• Check whether another team member could follow the documented steps when the usual person is away.
• Choose one improvement and a measure to review, such as preparation time or missed follow-ups.

You don't have to fix everything at once. Start where the work is getting stuck, make a change your team can maintain, and check whether it actually helped.

Where Do We Go From Here?

The common theme throughout all of these problems is that organizations don't necessarily recognize inefficiency until it starts affecting their employees, finances, or relationships. Sometimes everything appears to be working perfectly fine because the people behind the scenes are constantly compensating for the weaknesses in the systems they use.

This is exactly why I believe organizational assessments are so important and why I started Harbor Systems. Before recommending new software or Artificial Intelligence, we need to understand how an organization currently operates, where time is being wasted, and which processes could be improved. Sometimes that means implementing a new CRM, connecting existing applications, automating repetitive work, or simply documenting how certain responsibilities should be completed. Changing the way an organization operates can be uncomfortable, and I completely understand the hesitation. But we shouldn't allow our comfort with existing processes to prevent us from finding better ways to accomplish our goals. Churches and nonprofits have incredibly important missions, and the systems supporting those missions should make the work easier, not more complicated.

Just because your systems are working doesn't mean they can't be working better.