A new process has been introduced. The relevant people have been briefed, documentation has been updated and the change has gone live.
Management of Change complete?
Perhaps not quite.
A lot of attention naturally goes into preparing for change. We assess the risks, consider the impact, identify actions and make sure the organisation is ready to move from the old way of working to the new one.
But some of the most useful information about a change only becomes available after it has happened.
Once people begin working with it every day, we get to see whether the assumptions made during planning were right, whether the controls work as expected and, ultimately, whether the change has achieved what it was intended to achieve.
That's why implementation shouldn't necessarily be the end of Management of Change.
What Did We Expect to Happen?
Every change starts with an objective.
Perhaps a new system is intended to improve visibility. A revised process might remove duplication. A change in responsibility could improve accountability, while a new supplier may provide better capability or resilience.
Whatever the reason, there was an expectation that things would be different afterwards.
That gives us something important to come back to.
Once the change has had time to settle, we can ask whether it actually delivered the outcome we expected. Has the process become easier to manage? Are responsibilities clearer? Has the original problem been resolved, or has it simply moved somewhere else?
Without that review, it's surprisingly easy for a change to be considered successful simply because it was implemented successfully.
Those aren't necessarily the same thing.
The Difference Between Implementation and Effectiveness
Getting a change live is an achievement. It can involve significant planning, coordination and effort across an organisation.
But implementation tells us that the change happened. Effectiveness tells us whether it worked.
That distinction matters.
A new process may have been introduced exactly as planned but prove cumbersome in day-to-day use. A new responsibility may look perfectly clear on an organisation chart but create uncertainty when applied operationally. A new system may provide additional functionality while unintentionally making another task more difficult.
None of those outcomes necessarily mean the original decision was wrong.
They mean we now know something we couldn't fully know before the change was introduced.
The question is whether the organisation has a mechanism for recognising it.
Listen to the People Using the Process
One of the best sources of information after any change is often the people closest to it.
They experience the practical reality of the new process. They know where it works well, where it creates additional effort and where the original assumptions don't quite match everyday operations.
That feedback is valuable.
If people are regularly finding ways around a new process, for example, it can be tempting to see the workaround as the problem. But the more useful question might be why the workaround became necessary in the first place.
Perhaps the process takes longer than anticipated. Maybe information isn't available at the point it's needed. Perhaps responsibilities aren't as clear in practice as they appeared during planning.
Listening to that experience doesn't undermine the change. It helps improve it.
Look for the Unintended Consequences
Not every consequence of a change will be obvious during an initial assessment.
A control may technically still exist but become harder to perform. A task that previously sat naturally within someone's workflow may now rely on a handover. Information may be captured differently, creating an unexpected gap elsewhere.
Individually, these can seem minor.
Over time, however, small points of friction can influence behaviour. People adapt, informal processes develop and the way work is actually carried out can gradually move away from the process that was originally designed.
This is one reason post-implementation review can be so valuable. It gives the organisation an opportunity to identify those consequences while they're still relatively small.
Give Change Time — But Don't Forget About It
Reviewing effectiveness doesn't necessarily mean checking everything immediately after implementation.
Some changes need time to settle.
People need an opportunity to become familiar with a new process or system, and early difficulties don't always indicate a fundamental problem. Equally, waiting too long can allow unintended behaviours or weaknesses to become established.
The appropriate point to review will depend on the nature and significance of the change.
What's important is that the review is considered from the outset rather than becoming something the organisation intends to return to eventually.
A simple question during the original MoC can make a significant difference:
How will we know this change has worked?
If that question can be answered before implementation, reviewing effectiveness afterwards becomes considerably easier.
Closing the Loop
Good Management of Change isn't about producing more paperwork around every organisational decision.
It's about helping the organisation change with confidence.
That means understanding the potential impact before implementation, managing the transition and then being willing to look back once the change is operating in the real world.
What worked?
What didn't?
What have we learned?
And is there anything we now need to adjust?
Closing that loop turns Management of Change from an approval exercise into a genuine tool for organisational learning.
Because the objective isn't simply to demonstrate that a change was controlled.
It's to make sure the organisation is stronger after the change than it was before.
At NS Aero, we support aviation organisations in strengthening Management of Change and wider compliance processes, helping ensure change is effectively considered, implemented and reviewed.
We make almost ready, audit ready.