Why Organisational Change Often Creates More Work Before Less

Why Organisational Change Often Creates More Work Before Less

November 09, 2026•4 min read

Why Organisational Change Often Creates More Work Before Less

Most organisational change is introduced with the promise of improvement.

A new system will make things easier.

A restructure will create clearer accountability.

A new process will reduce duplication.

A new way of working will improve efficiency.

Yet during many change initiatives, employees experience the opposite.

There are more meetings.

More administration.

More things to remember.

More systems to navigate.

More uncertainty about how work should actually be done.

Leaders can interpret this as resistance to change.

Sometimes it is.

But sometimes employees are responding quite rationally to something else.

The organisation has introduced the new way of working without properly removing the old one.

Change becomes exhausting when organisations add the new without letting go of the old.

A new reporting process is introduced, but the old spreadsheet is still maintained “just in case”.

A new system is implemented, but employees continue recording information elsewhere because people still rely on the previous process.

Responsibilities are redistributed, but former role holders remain involved because nobody is completely confident about the transition.

A new meeting rhythm is established, but the existing meetings remain in the calendar.

A new strategic priority is announced, but none of the previous priorities are removed.

Each decision can seem sensible in isolation.

Keeping the old process temporarily reduces risk.

Maintaining the spreadsheet provides a backup.

Keeping an experienced person involved makes the transition easier.

Continuing an existing meeting ensures nothing gets missed.

But when these decisions accumulate, employees end up operating two versions of

the organisation at once.

The old one has not disappeared.

The new one has simply been layered on top.

This is where change fatigue can begin.

People are not necessarily tired of change itself.

They may be tired of carrying the additional complexity created by incomplete change.

That distinction matters.

Because if leaders diagnose the problem as resistance, the response is often more communication about why the change is important.

More presentations.

More updates.

More encouragement to embrace the new direction.

But employees may already understand the reason for the change.

Their concern is more practical.

What are we supposed to stop doing?

That question deserves far more attention during organisational change.

Leaders naturally focus on what needs to begin.

What new behaviours do we need?

What system are we introducing?

What process should people follow?

What capability needs to be developed?

Far less attention is often given to what the organisation needs to deliberately stop.

Yet every meaningful change should eventually make something else unnecessary.

A process.

A behaviour.

A responsibility.

A meeting.

A report.

A system.

A decision pathway.

A way of working that belonged to the organisation before the change occurred.

If nothing disappears, the organisation has not necessarily changed.

It may have simply become more complicated.

This is particularly important because the people designing change are often not the people carrying its full operational load.

From a leadership perspective, the new process may appear straightforward.

From an employee’s perspective, it sits alongside customer demands, existing KPIs, reporting requirements, meetings, deadlines and all the informal work required to keep the organisation functioning.

The cost of change is therefore not only financial.

It is also cognitive.

Every additional process creates something else people need to understand, remember and navigate.

Every unclear responsibility creates another conversation.

Every duplicated system creates another opportunity for inconsistency.

Every legacy process that remains creates another decision about which way of working should take priority.

Eventually, the organisation becomes harder to operate inside.

Good change management therefore requires more than introducing something new.

It requires actively removing what the new approach was designed to replace.

That may mean leaders making uncomfortable decisions.

Turning off the old system.

Cancelling the meeting.

Removing the report.

Closing the old process.

Clarifying that a former responsibility no longer sits with someone.

Accepting that the organisation cannot keep every previous practice while also creating something different.

There may be a transition period where old and new genuinely need to coexist.

But transition should have an end point.

Otherwise temporary duplication quietly becomes permanent complexity.

When people say they are overwhelmed by another change initiative, it is worth looking beyond whether they are resistant.

Ask instead:

What have we asked people to start doing without giving them permission to stop doing something else?

The answer may reveal that the problem is not the amount of change happening

across the organisation.

It is the amount of the old organisation that nobody has been willing to leave behind.

If your organisation is navigating significant change, Objective Consulting can help

strengthen leadership alignment, clarify accountability and translate change into

practical ways of working across your business.

Get in touch with Brad from Objective Consulting.

www.objectiveconsulting.com.au

03 5640 8088

Brad Semmens

Brad Semmens

Brad Semmens - Director and Head Consultant at Objective Consulting.

LinkedIn logo icon
Instagram logo icon
Youtube logo icon
Back to Blog