Why your AMS implementation might not stick, and how to make sure it does

You’ve probably heard some version of this from a peer at another association, or said it yourself: the new system was fine, it just never really took. Six months after go-live, the events team is still running registrations through a spreadsheet, renewals are being chased from someone’s inbox, and the AMS implementation everyone signed off on has quietly become one more place where data lives.

That’s rarely a software problem on its own. More often it comes down to people and sequencing, and the groundwork for both is usually laid well before launch day.

Your team’s history shapes your AMS implementation

If your team has lived through a CRM project that promised transformation and delivered two years of disruption, or a website rebuild that ran over budget, they’re not going to greet the next system with open arms. That isn’t obstruction, it’s experience, and it’s worth taking seriously from the start rather than treating it as a communications problem to tidy up once the technical work is done.

This is especially common in associations that spent years on bespoke builds from external consultants, each of which worked well enough for a while before becoming hard to maintain. By the time a purpose-built AMS arrives, people have been through more than one cycle of expectation and disappointment, and they’ll be watching closely to see whether this one is any different.

The upside is that the people who’ve seen systems fail know exactly what failure looks like. Bring your membership and operations staff in early to map what they actually need the platform to do day to day, and you’ll catch problems that would otherwise only surface after go-live. You’ll also give them a stake in the outcome, which changes how they talk about the project to everyone else.

How to make sure your new AMS sticks

1. Start with the tasks your team does most often

The clearest early sign that an AMS will stick is whether it makes the most frequent jobs noticeably easier in the first few weeks, not once configuration is finally finished. If common tasks get harder, even temporarily, people drift back to their workarounds while they wait for things to improve.

For most associations, those high-frequency tasks are renewals and event bookings. They take up the most time and cause the most friction when they don’t run smoothly. When staff can feel those processes getting easier, they have a reason to use the system that doesn’t depend on a memo from leadership.

2. Sequence your rollout around early wins

The order you roll things out in matters more than it usually gets credit for. It’s tempting to lead with the strategically important features, like a new reporting suite or engagement model, but if most of the team rarely touches them, they won’t build momentum. A team that has spent years chasing renewals by hand will remember the first renewal cycle that runs automatically, and that memory shapes how they feel about the platform for a long time.

3. Make the new system the default, starting at the top

Staff take their cue from leadership. When questions about members get answered from the CRM record, events are built in the event management module rather than a parallel spreadsheet, and board reports come straight out of the platform, it sends a clear signal that this is where the organization actually works. When leaders keep the old processes running alongside the new system just in case, the signal runs the other way, and the implementation settles into a half-adopted state that falls well short of what was planned.

4. Plan for the awkward first few weeks

Even a well-run rollout has a stretch where everything feels unfamiliar. That’s normal, and it’s worth planning for rather than hoping it won’t happen. Regular check-ins with your implementation partner, short training videos staff can revisit, and a named go-to person internally all help people push through rather than retreat to what they know.

The American Association of Professional Landmen (AAPL) went through exactly this when it replaced six separate systems with ReadyMembership. Andrea Spencer, Director of Communications, describes how the mood shifted once staff were working in the platform day to day:

What full adoption looks like

Full adoption is the point where the platform is the first place people go when they need something, not the option they try after the spreadsheet. A question about a member gets answered from the CRM record instead of an email to a colleague, and renewals run from the platform without anyone exporting a list first.

Getting there after a history of disappointing projects takes longer than it would elsewhere, but the route is usually the same: a system that does what it’s supposed to do, in the areas that matter most, early enough to change how people feel about it.

Where to start

• List the tasks your team does most often and agree what “easier” would look like for each
• Talk honestly with staff about past technology projects and what went wrong
• Involve the people who’ll use the system daily in shaping requirements and testing
• Plan your rollout so the first features to go live are the ones that save the most time
• Agree as a leadership team to retire old spreadsheets and workarounds by a set date

If you’re trying to work out why a previous implementation didn’t fully take, the same questions are worth working through in hindsight. The answers usually point to something more specific than the software itself.