top of page

A Tool No One Knows About Is Just a Cost: A Real-World Change Management Success Story

Oct 30
4 min read

Updated: 2 days ago

Author: Christine Flott, Project and Change Management Consultant


For organizations that haven't worked with a change management practitioner before, it can be difficult to understand exactly what change management adds to a project.

You may recognize some of the symptoms that signal a need for it: employees overwhelmed by constant change, new tools that aren't being used as intended, confusion about new processes, or support teams fielding questions they weren't prepared to answer. But what does a change practitioner actually do to prevent those problems?


Here's one example from a large organization where a relatively small change management effort helped bridge the gap between building a new technology and getting people ready to use it.


The project: Moving away from fax


A large health insurance company I worked with was frequently affected by changes in government regulations. As part of a broader effort in the healthcare industry to "ax the fax," pending state legislation was prompting the company to give medical providers - physicians, nurse practitioners, and others - a way to submit claims documentation digitally.


Until then, fax had been the primary way providers submitted that documentation.

The technology team was building a portal that would allow providers to submit documents electronically. From a development standpoint, the work was moving forward.

But the product manager recognized a problem: Who was preparing the 100s of providers who would actually use and dozens of others that would support it?

She knew me from a previous change management effort and reached out for help. Her concern was straightforward. Her team was developing a valuable new capability, but no one was focused on introducing it to providers or preparing the internal teams who would support them.


That's where change management came in.


Start by understanding the change


I began joining project meetings and learning how the new claims submission process would work. My questions included:


  • What does the current process look like?

  • How will the new tool change that process?

  • Who needs to use it?

  • Who else needs to know about it or support it?

  • When do those groups need to know?

  • How do they typically receive information from the organization?

  • How intuitive is the new process? What training will users need?

  • Where does documentation for the current process live?

  • Who owns that documentation, and how can it be updated?


None of these questions involved writing code or changing the portal itself. They were about connecting the technology being built to the people expected to use it.


Identify everyone affected — not just the end user


The most obvious stakeholders were the medical providers who would use the portal to submit claims documentation. But they weren't the only ones.


The company's provider relations and support teams also needed to understand what was changing. If providers had questions after launch, those internal teams needed to be ready with answers. That meant we needed to prepare multiple audiences with information about the new portal, its go-live date, how to use it, and where to go for support.


Meet people where they already get information


The organization had three primary ways of communicating this type of information to providers: email, a provider newsletter and - somewhat ironically, given the project - blast faxes. Rather than creating entirely new communication channels, we used the ones providers already knew and relied upon.


Working with contacts across the organization, I coordinated messaging through each of those channels. I also shared key information directly with the provider support team through their existing monthly meetings.


In each case, I partnered closely with a communications team member to make sure the language and tone were consistent with the organization's established communications.


Don't forget the documentation


Communication alone wasn't enough.


I also tracked down the existing documentation providers used to understand the claims-submission process. If we told providers about the new portal but left instructions describing the old process, we would be creating confusion at exactly the moment we were trying to reduce it.


Working with the technical team, I gathered the correct screenshots and process steps so the documentation could reflect the new experience after go-live.


Because I didn't have direct access to the portal myself, collaboration with the people who did was essential. Change practitioners don't have to be the technical experts. We do need to know which questions to ask, who has the answers, and how to translate those answers into something useful for the people experiencing the change.


Depending on the project, change management doesn't have to be a massive undertaking


By the time I joined the project, we had only a matter of a couple of months before go-live.

Fortunately, the product manager recognized something important: a product isn't truly ready simply because the technology is ready. The people who use and support it need to be ready, too.


With her support and the help of key members of the provider relations, communications and technical teams, I was able to quickly connect with the right people, answer the right questions, and put the pieces in place to support the rollout.


This wasn't a massive change management program. It didn't require a large team or months of additional project work. It required someone to deliberately look at the project through the eyes of the people affected by it.


Who needs to know? What do they need to know? When do they need to know it? What do they need to do differently? And what needs to be in place so they can do it successfully?

Those questions can make the difference between implementing technology and actually realizing its value.


After all, an organization can build an excellent tool. But if the people it's intended for don't know about it, don't understand why or how to use it, or can't get help when they need it, that investment isn't delivering the value it was designed to create.



If your organization is investing in a new technology or process, ask one more question alongside: 

'Is it ready to launch?' OR ‘Are our people ready for it?


Learn more about our Change Management Services on our website, and reach out if you'd like to talk more.

Comments


bottom of page