Managing Change When the Operating Environment Shifts

Fabmundo Insights

Change does not always arrive in the same way.

Sometimes it is imposed by regulation. Sometimes circumstances change so quickly that established plans no longer make sense. At other times, an organisation grows and the processes that worked previously begin to show their limitations.

I have encountered each of these situations at different points in my career.

Brexit changed elements of the operating environment for bringing internationally manufactured products into the UK. COVID disrupted established channels and priorities. Growth created the need for more developed forecasting and stock planning. My work on the Procter & Gamble account also involved adapting activity across different retail environments.

The circumstances were very different.

What connected them was what happened next.

A change becomes operationally meaningful only when the way work gets done changes with it.

When external requirements change the process

Brexit provided one of the clearest examples.

For a business coordinating internationally manufactured food products into the UK, changes to the trading and import environment could not simply be acknowledged and filed away.

We had to understand what they meant for the way products actually moved through the system.

Processes and documentation needed to reflect changing requirements. Manufacturers, logistics partners and other stakeholders needed the right information. Existing assumptions had to be revisited while maintaining continuity for wholesalers, retailers and customers further down the chain.

The intended outcome had not fundamentally changed.

Products still needed to move through the supply chain compliantly and reach customers.

Parts of the process supporting that outcome had.

That meant looking beyond the requirement itself.

What needed to be captured differently? Did another step now need to happen earlier? Were responsibilities sufficiently clear? Did external partners understand what was required from them? Could an old assumption create a problem later in the process?

This was where regulatory change became operational change.

The requirement created the trigger. The real work was incorporating it into everyday delivery without losing sight of everything else that still needed to happen.

When circumstances change faster than the plan

COVID created a different type of change.

A significant part of developing international food brands in the UK involved direct engagement with independent organic and wholefood retailers. Store visits, buyer conversations and product sampling were important ways of introducing unfamiliar products and building new relationships.

The pandemic disrupted that model. Independent retailers were dealing with their own immediate operational pressures, while normal opportunities for face-to-face engagement and product sampling became much more limited.

That changed what was realistically achievable.

Continuing with the same activity simply because it had formed part of the original plan would not have made sense. Priorities had to be reconsidered, expectations adjusted and activity focused on the routes that remained practical while conditions continued to change.

That experience sharpened a distinction I still find useful.

Responding to change is not the same as reacting to it.

Reaction can create activity very quickly.

A useful response starts by understanding what has actually changed, what that affects and what still matters most.

Those questions create some structure when the environment itself has become less predictable.

They also help preserve the intended outcome even when the original route towards it no longer makes sense.

When growth changes what the organisation needs

Not every change begins with a crisis or new external requirement.

Some arrive much more quietly.

As customer demand and distribution activity developed, forecasting and stock planning became increasingly important.

At relatively small volumes, planning can operate through fairly simple assumptions. As activity increases across different customers and channels, the consequences of those assumptions being wrong become more significant.

Too little stock can affect availability and customer relationships.

Too much can tie up working capital and create a different set of operational pressures.

The response was not a dramatic transformation programme. The planning approach simply had to become more developed as the operating environment became more complex.

That meant paying closer attention to sales patterns, customer requirements, lead times and available stock, then using that information to make better decisions about future requirements.

I think this type of change is particularly easy to overlook because nothing necessarily appears to be wrong.

The organisation has simply moved beyond some of the processes and assumptions that were appropriate at an earlier stage.

Growth is normally discussed as an outcome organisations want to achieve.

But growth also tests the systems underneath it.

A process that works well at one level of activity may become increasingly fragile at another. Recognising when that point is approaching can be just as important as responding when something has already failed.

When plans meet different operating environments

A different perspective came from my time working on the Procter & Gamble account.

My role involved managing activity across major UK grocery accounts, including product launches, promotional programmes, account planning and performance analysis. The overall objectives could be consistent, but the environment in which they had to be delivered was not always the same.

Different retailers had their own priorities, operating requirements and constraints. Plans therefore had to translate into activity that worked within the reality of each account and retail environment, while still maintaining the standards and objectives expected across the wider programme.

Performance information also mattered. Reviewing what was happening in stores and across accounts helped identify where execution was working as intended and where activity needed to be adjusted.

That experience reinforced something I have seen in other settings since.

The difficult part is often the middle

Across these examples, the trigger for change was easy enough to identify.

Brexit introduced different requirements.

COVID disrupted the environment.

Growth put pressure on existing planning.

Different retail environments required plans to be adapted in practice.

The more interesting part sits between the trigger and the intended outcome.

A requirement has changed, but the new process is not yet established.

Circumstances have shifted, but priorities have not yet fully adjusted.

A planning weakness has been recognised, but better information is not yet consistently shaping decisions.

A plan has been agreed, but execution still needs to work within the reality of the operating environment.

That middle is implementation.

It can involve interpreting requirements, changing processes, coordinating stakeholders, communicating what is different, resolving practical problems and making further adjustments once the new approach meets operational reality.

It is rarely a single action.

That is one reason change can look much simpler on a presentation than it feels to the people responsible for making it work.

Changing the system while operating within it

There is another complication.

Most organisations do not get to stop normal delivery while they change how that delivery works.

Customers still need responses.
Suppliers still need decisions.
Teams still have responsibilities.
Costs, deadlines and operational pressures continue.

The challenge is often to change the system while continuing to operate within it.

I think this is where some of the real judgement around change sits.

Move too slowly and the organisation can remain exposed to a requirement or problem that has already moved.

Move too quickly without understanding the consequences and the solution can create difficulties elsewhere.

Not everything needs to change at the same speed. Some things may require immediate attention, while others can be phased. Certain requirements or controls may need to remain fixed regardless of the pressure to move quickly.

Understanding those differences matters.

Adaptation still needs boundaries

Experience has made me cautious about treating flexibility as an objective in itself.

Being able to adapt is valuable.

Constantly changing direction is not.

When circumstances shift, the question is not simply how quickly an organisation can change. It is whether it can identify what needs to move and what needs to remain protected.

Regulatory and quality requirements may still need to be satisfied.

Responsibilities still need to be understood.

Commercial realities do not disappear.

Important decisions may still need to be documented.

This is where governance supports change rather than preventing it.

It creates boundaries within which adaptation can happen without losing control of the wider objective.

That is particularly important where several teams or organisations are involved, because one response to change can easily create consequences somewhere else.

When change becomes part of delivery

Looking back, the changes themselves were rarely the hardest part to identify.

Brexit created new requirements. COVID disrupted established assumptions. Growth put pressure on existing planning, while different retail environments required plans to adapt without losing sight of the wider objective.

The harder part was translating those changes into everyday delivery while the work itself continued.

That meant understanding what had changed, identifying what it affected, adjusting processes or priorities where necessary, and observing what happened once the response met operational reality.

The first response will not always be the final one.

Implementation also means recognising when something is not working as intended and being prepared to adjust again without losing sight of the outcome.

Because change is not fully implemented when a new process is agreed or a different approach is introduced.

It is implemented when the organisation can work differently because of it.