As simple as it can be

Simplifying things is a challenge for any business. If you have a simple process, people can follow it without making mistakes. If you have a complex process, mistakes can and will be made.

I find that quality management systems often appear to be over-complicated. There’s a theory that goes something like this –

‘The system is important. Important things are complex and difficult to understand, so they are written in complex language.’

If you add to this theory the individual who overplays the difficulty of their job, you have the quality management system that becomes a bureaucratic nightmare  –  otherwise known as the business prevention system.

Those are the systems that people hate. They are seen as restrictive, serving only to enforce compliance.

One recent experience with a customer – a very large organisation – illustrates this. They were returning a unit to us for some additional development work, but the unit had been purchased as a standard unit, not for development.

We’d agreed in April to do some further work. In July, after several emails, we got a reply from someone in the customer’s team, a frustrated engineer. He told us –

‘I can’t send you the unit. It’s sitting on my desk, but it’s so far into our systems that I can’t work out  how to send it back to you.’

I’m sure these were exceptional circumstances, but it’s an example of a system hindering the business.

However, if you can take a step back and look at the reasons why particular processes or procedures exist, you may find some nuggets of value.

A procedure or process often came into existence to resolve a problem. Over time, extra layers were added. The result is that you end up with a complex mess.

When you set about simplifying a process or procedure, start by asking, ‘Why does this exist?’ and create a simple process to deal with just that: ‘Why?’.

If that’s not possible, perhaps the process is trying to do too much?

You’re likely to find examples of trying to do too much when you examine  complex assembly processes. We have processes that are extremely complex – one product we analysed recently had 174 parts. Any process that tries to capture such a large assembly of parts is going to be complex.

However, it’s possible to view that product as a number of different sub-assemblies. Each of those can still be regarded as complex, but there are probably only 30 parts in the most complex of them.

We have an overall procedure in place to assemble this product, but the lead procedure is simple and refers to the sub-assembly procedures, which in turn are also simple.

Making a process or procedure simple isn’t easy – but it can add great value to your business.

What does success look like?

For some people, success means having a fancy car or a big house.  For others, it might be finding a perfect balance between work and home life.  For yet others, it might mean being able to afford exotic holidays.

People are different and are motivated by different rewards.

When you’re leading a team, one huge challenge  is identifying what motivates the different individuals within that team.

A bigger challenge is being able to communicate clearly how an individual will know what success means for their job or area of responsibility.

Many years ago, I surveyed the staff of a somewhat dysfunctional organisation.  One of my questions was, ‘When doing your job, how would you know when you’ve been successful?’

Most could not answer this. They had not thought about the real purpose of their role, why their job existed, or how the company would benefit from employing them.

There needs to be a reason for the existence of every role in a company and there needs to be an expected outcome for each role. That’s how success can be measured – that’s where the company receives its return for the wages and salaries it’s investing.

A useful exercise that’s often set for people in start-ups or small businesses aiming to grow is to get them to draw the organisation chart they feel will be appropriate to their business in (say) 5 years’ time. This exercise helps business leaders define the roles a business needs to foster growth – rather than simply hiring someone else to do more of the same.

What’s more difficult, but probably even more valuable, is to apply a similar discipline to existing businesses. Break the business down and look at each area:  Why does this function exist? What’s the purpose of this role? What does success look like in this job?

That can easily lead to a realisation that an organisation is shaped around the skills and personalities within it. How the organisation has developed is not the culmination of premeditated design but the result of happenstance and unplanned growth.

Those same factors could well explain what’s preventing further growth. That’s why it’s important to ask defining questions – identify goals for each role and what success in achieving them looks like, then consider how they align with the goals of the organisation as a whole.