But are you really willing to change?

But are you really willing to change?

When any organization is making a change in data management systems, one of the most important considerations during implementation is what business processes need to be changed. Or put another way, when we change the software, are we also willing to change how we do the things we do?

It is not uncommon to hear an executive director say to the vendor during implementation, "Tell us how to do this better so that we can really leverage your software." This is the correct sentiment. But too often, the reality is that while senior management may expect this, very often the staff who actually use the system are more resistant to changing how they do things. Which can lead to trouble.

So what can be done? Here are some suggestions:

  1. Eliminate things that simply don't need to be done anymore. This is the easiest kind of behavior change to make; STOP doing it! You'd be amazed at how many processes exist now that you simply don't need to be doing.
  2. Focus on the outcome, not the input. If the outcome is for someone to be registered for an event and to have data for an attendees list and badge, focus on that, not on how we get there. Then let the vendor tell you the best way to get there using their software.
  3. Highlight how the change will benefit the staff person. Too often we say "This will be good for the association" or "this will be good for the customer." Those are fair desires, but are not terribly appealing to the person whose behavior has to change. You have to explain how the change is better for the person who has to change.
  4. Acknowledge that change can be frightening and unsettling, while also acknowledging that mistakes will be made during the learning period. What I hear from staff is they don't want to change processes for fear of making mistakes.

Changing software is one big step toward improving data management. But changing your processes is another critical element for success. Don't overlook it.

Wes's Wednesday Wisdom Archives

Ownership is Required

July 28, 2021

Ownership is required When asked for the most common reason AMS implementations fail, I typically respond …

Ownership is Required Read More »

It’s all relative…

July 21, 2021

It’s all relative… Over the course of my 22 years of consulting, I’ve consulted with …

It’s all relative… Read More »

Eliminate to optimize

July 14, 2021

Eliminate to optimize So much of data management is habit (both good and bad) which is …

Eliminate to optimize Read More »

For data governance, ask “Why?”

July 7, 2021

For data governance, ask “Why?” Recently I’ve had the opportunity to work on several data …

For data governance, ask “Why?” Read More »

More on Meetings

June 30, 2021

More on Meetings I’ve written before about the importance of making sure your meetings are …

More on Meetings Read More »

Action produces momentum

June 23, 2021

Action produces momentum Another great quote from James Clear: “Motivation often comes after starting, not …

Action produces momentum Read More »

My #1 Best Practice…

June 16, 2021

My #1 Best Practice… A client recently asked me: “If you had to pick a single …

My #1 Best Practice… Read More »

Encourage engagement with prizes!

June 9, 2021

Encourage engagement with prizes! One of the biggest challenges any organization faces when implementing a new …

Encourage engagement with prizes! Read More »


June 2, 2021

Inertia One definition of inertia is “to remain unchanged.” My sense is that many association processes, projects, or …

Inertia Read More »

When’s the “least bad” time?

May 26, 2021

When’s the “least bad” time? When working with clients on a new project, especially a …

When’s the “least bad” time? Read More »

Scroll to Top