The value of technology isn’t in owning the platform. It’s in changing how the organization works.
We see the same story often. An organization finally invests in a CRM, a donor database or a new project management system. The demos were impressive. The contract is signed. The data gets migrated, a consultant configures the basics, and the team attends a training.
Six months later, the reports still come from spreadsheets. Half the team logs activity in the system and half doesn’t. Leaders don’t trust the numbers, so they ask for them by email. The organization is now paying for a CRM and still running on its old workarounds.
The software usually isn’t the problem. The problem is that buying it was treated as the change, when it was only the start.
Why CRM implementations stall
The old process moved into the new tool
Most implementations copy the current way of working into the new system. If the old process was messy, unclear or built on workarounds, the new system inherits all of it, now with a subscription fee. Sometimes, the workarounds themselves are unclear, and therefore overlooked.
A CRM investment is an opportunity to define how work should flow: who is responsible for what, what data is entered and by whom, when, and what happens next. Skip those decisions and the tool has nothing solid to support, and the team remains mired in a lack of clarity.
No one agreed on what the data means
What counts as a “lead,” and what happens in the sales pipeline? When is a donor “lapsed”? Is a client “active” when they sign or when work starts? Different teams answer differently, so the same report gives different numbers depending on who pulls it. Before long, nobody trusts the system.
It was configured for leaders, not for the people entering the data
Dashboards get the attention. Data entry gets whatever time is left. But a CRM is only as good as what people put in it, and the people entering data are often the busiest, least consulted, and most under-resourced. If entering data is laborious, it won’t happen consistently.
Training ended at launch
One training session teaches people where the buttons are. It doesn’t build habits, or adapt to the new challenges that emerge from a team undergoing change. New staff arrive, questions pile up, and without someone who owns the system, small problems become reasons to stop using it.
Nobody owns it
In many small organizations, the CRM belongs to whoever happened to set it up. When that person leaves or gets busy, the system drifts. Fields multiply, duplicates pile up and the data slowly stops being useful.
What makes a CRM worth the investment
- Decide what the system is for. Name the two or three questions it must answer reliably, such as “Which donors gave last year but not this year?” or “How long does it take a lead to become a client?” Design around those.
- Agree on definitions first. Write down what your key terms mean and how records move from one stage to the next.
- Map the process before configuring the tool. Walk through how the work should happen, with the people who do it. (See Process mapping for small teams.)
- Make entry easy. Cut fields nobody uses. Automate what can be automated. Fit the system to the way people actually work.
- Retire the workarounds. If the old spreadsheet is still available, people will use it. Set a date, move the reports and close it.
- Name an owner. One person is responsible for data quality, training new staff and deciding on changes.
- Check adoption at 30, 60 and 90 days. Look at who is using the system and how. Fix friction early, before habits harden.
Technology change is organizational change
A new CRM changes who does what, how decisions get made and what information leaders can see. That’s organizational change, and it needs the same attention as any other. For more on that, read why change management fails in small organizations.
How we help
The Change Up Group helps small businesses, nonprofits and purpose-driven organizations choose, implement and get real value from their CRMs and data systems. Whether you’re about to buy a system or trying to rescue one you already have, we start by understanding how your organization works. Learn more about our data, technology and operations work.
Start a conversation about getting more from your systems.