Skip to main content

Effective MRP needs senior buy in

Over the past year I have been involved in a number of MRP projects; systems to help drive manufacturing operations. Most of these projects have involved working with businesses that have already done the hard work of specifying, selecting and installing the software. Similarly, staff have been trained – it’s all ready to go live! 

So, if a business is still operating in chaos and / or is not achieving the results needed from a system like this, well there’s a problem! But what is the issue? In my experience it is often lack of ‘buy-in’ to the project by senior members of staff.

And yes, this really does make all the difference.


If senior managers are not involved with day-to-day usage of the system, how can they hold people accountable? By being involved, I don't mean undertaking transactions in the system, i.e. raising purchase orders. I mean that they are involved with the flow of information at some level.

If your senior team aren't 'visible' on the system then you risk a decay of standards for your business. Like the empty warehouse windows that get smashed by vandals when minor repairs aren't dealt with*, a lack of management presence doesn't help good system disciplines to be maintained.
I have heard stories of senior people boasting that they don't use their computer system (because they think that either they shouldn't need to or it’s a badge of 'success'). These stories pervade the organisation and it doesn't help users get enthused.

One method to get over the issue of senior member ‘buy-in’ is to use a Sunrise meeting format. Sunrise meetings are a great way of bringing together key players in the business at the start of each working day. Priority data is pulled together and reviewed. If it isn't right then there is a need for action.

The direct use of an ERP / MRP outputs is a great way testing the quality of your system’s data, as well as helping direct business efforts. When a suite of management reports are part of this mix there is even more opportunity for your senior team to get involved. They will soon realise how well the system is working and the impact this is having.

I remember one occasion during my time in Operations Management. There had been a slow uptake in part of our ERP system. I was struggling to get interest from the teams, to help resolve this, so lobbied my boss. After part education, part exploring opportunities and part begging, I brought him round. The end result was a plan.

My boss decided to stop spoon feeding the shop floor with data and make them become self-sufficient; if they didn't use the system they wouldn't get their information. Their system would work, if only they had a reason to use it. This data then fed our Sunrise meetings and it worked beautifully. Our system became both self-sustaining and effective.

When developing your MRP system it is critical that the right senior people are participating in the right kind of ways. In my experience, the projects that have really been painful have been the ones where the senior team have resisted getting involved. Whether they thought it was beneath them, that they were too busy, or something else, all I can report on are the results. And these are bad when the senior team isn't pro-actively engaged.

Inversely, the projects that have gone (relatively) like a dream, have had the right support from the senior team. They understood the benefits of MRP, what they needed to do to create the right environment for it to work, and also how they can use the system for their own benefit.
The results, as they say, speak for themselves.

If your system isn't where it needs to be, and your senior team isn’t fully engaged, then why not try involving them with a Sunrise meeting and see whether that strategy works?


* If you haven't heard of 'Broken Window Theory' and how it affects disciplines and standards, check out this link: http://en.wikipedia.org/wiki/Broken_windows_theory


Giles Johnston
...optimising MRP systems and re-engineering business processes

Popular posts from this blog

Where there is a (performance) gap there is a concern

I had a really good day yesterday working with a client's team.

The team has issues. Plenty of issues. Some are managerial issues, some are people issues and some are production issues.

When I first met the team they didn't know what to do with their issues, so I started by helping them to see more issues.

Issues everywhere, they didn't seem very impressed.

And then we captured the issues as 'concerns' into the tried and tested 'concern cause countermeasure' format and followed the process:

Concerns probed for root causes and root causes converted into countermeasures.
Soon they realised that some of their root causes dealt with numerous concerns and they gained momentum.

Yesterday we pulled another one of their processes apart and identified all of the gaps. The gaps became concerns and we fed them back into the process. Now they have a practical action plan (of countermeasures) to upgrade the process in question.

What do you do with your performance gaps? …

Continuous Improvement and the Five Legged Race

Many improvement projects need the buy in of several people before they can progress. Amongst these people there will be some that have a firm view of what needs to happen and are keen to make progress. Some of the people won't be sure and they will need more time. Other people might not be that interested and have other priorities they want to focus on.

None of this is wrong.

It is an observation of mine and one that I see repeat on a regular basis with the businesses that I come into contact with.

But, if we take the principle from the observation we have an interesting improvement strategy (one that I personally use when I get stuck with my client's improvement projects).

You might have worked out the approach from the title of this blog post, but it is analogous to a three-legged race (or four, five, nine...). If someone in the group moves in the wrong direction and / or at the wrong speed then the whole group falls over.


In the example I gave at the start it is no differe…

Do you have time to prepare (in order to become super productive)?

I had a funny conversation a few weeks ago with a team that was complaining about one of their colleagues spending 'ages' preparing their workstation within their factory. I meet a lot of people that spend too long preparing (and effectively procrastinating) so I was intrigued by their comment. It turns out that this individual didn't spend too long but rather his colleagues dived into their work without thinking through what the best way to work was...

The slower to start gentleman did in fact prepare his work area. He was also able to produce a far greater amount of work in the same time period because he had invested in a smarter way of working than his counterparts. The time spent preparing his working area was valuable and not overdone.

This example reminds us of the importance of the second S in 5S (set in order) and how workstation design is critical if we want to maximise the productivity of our teams. Whether this is a physical work area in a factory, the filing s…