ISO 9001: When Did You Last Question the Way Things Have Always Been Done?

Your team spends an hour filling in a report. A manager checks it. Someone saves it in a folder.

Then nobody uses it.

Elsewhere, a customer waits while an order passes through three people for approval. Staff enter the same details twice because two systems need updating. A small mistake happens again, despite another reminder to take more care.

Everyone is busy. Yet some of that work may be making the business slower without making it better.

Ask why these tasks happen, and you may hear a familiar answer:

“We’ve always done it this way.”

That answer can be expensive.

It can protect old habits from useful questions. It can leave staff working around problems that managers never see. Over time, extra steps become so familiar that nobody stops to check whether they still help.

ISO 9001 continual improvement encourages businesses to keep reviewing and improving how they work. Improvement is one of the quality management principles that underpin the standard. www.iso.org

This does not mean changing every process or chasing every new idea.

It means asking a fair question: does the way we work still help us deliver what our customers need?

Familiar work can hide unfamiliar costs

A process may have made perfect sense when it was first introduced.

Perhaps the business was smaller. Orders were simpler. One person handled customer enquiries, and paper records were the easiest option.

Years later, the business has grown. More people are involved. Customers expect faster replies. New software has been added.

The original steps remain.

Staff may now copy information from a paper form into a spreadsheet, then enter it into another system. Each step takes time and creates another chance for error.

Because the work happens every day, its cost becomes easy to overlook.

Ten minutes wasted on each job may feel small. Across a busy week, it can take hours away from useful work.

There is a human cost, too. Repeated effort frustrates people, especially when they cannot see its purpose.

Before asking your team to work faster, check whether the process is asking them to do more than they need to.

Question the work without attacking the people

People can feel protective of familiar ways of working.

They may have helped create the process. They may have used it successfully for years. A question about it can sound like criticism of their judgement.

How you raise the subject matters.

Start with the purpose of the work and the result you need. Ask people to explain how the task works today and where they find it difficult.

Avoid assuming that an old process is a bad process.

There may be a good reason for a step that seems unnecessary. It might protect customer information, confirm an important detail or meet an agreed requirement.

Give people room to explain.

A useful discussion sounds like this:

“What does this check help us catch?”

“When does this step cause a delay?”

“What would happen if we changed it?”

These questions help the team examine the work together. They also make it easier to separate useful controls from habits that have outlived their purpose.

Give every step a clear purpose

Choose one task and follow it from start to finish.

For each step, ask what it achieves.

Does it confirm the customer’s needs? Help someone make a decision? Prevent an error? Provide a record that the business needs?

You may find steps with clear value. Keep them.

You may also find activities that nobody can explain.

A report may have been created for a manager who left years ago. A second approval may have been added after one unusual mistake and never reviewed. A form may ask for details already held elsewhere.

Do not remove these steps without checking their wider role.

Speak to the people who receive the information. Review any customer, legal or other relevant needs before making a change.

The aim is to understand the purpose before deciding what to do.

A shorter process can be helpful. A process that loses an important safeguard can create much bigger problems than the time it saves.

Listen to the people doing the work

Managers often see the planned process.

Employees see what it takes to make that process work on a busy day.

They know which form causes confusion. They know where information is missing and which task needs a phone call before it can move forward.

They may have created their own fixes.

One person keeps a separate list. Another uses an old email as a guide. Someone else checks every order twice because they do not trust the details they receive.

These habits tell you something useful.

The official method may be leaving gaps.

Ask staff where they spend time chasing, copying, waiting or correcting. Invite them to show you a real example.

Then listen before offering a solution.

A change designed without their input may miss the problem or make their work harder.

When people help shape an improvement, you gain practical knowledge and a better chance that the new method will be used.

Look beyond “the job gets done”

A task can be completed while the process behind it remains weak.

A customer receives their order on time, but only because an employee stayed late. A report is accurate because a manager corrected it. A deadline is met after several urgent calls.

The final result looks fine.

The extra effort disappears from view.

If you only measure whether the job was finished, you may miss how much work was needed to rescue it.

Ask what happened along the way.

Was the information complete at the start? How many times did the work come back for correction? Did people have to stop other tasks to help?

Good results matter. So does understanding whether the business can achieve them reliably.

A process that depends on someone repeatedly saving the day deserves attention.

Those employees may be doing excellent work, but their effort should not become a reason to leave avoidable problems unchanged.

Use facts to guide the discussion

A familiar process can attract strong opinions.

One person thinks it works well. Another says it wastes time. A manager believes the problem only happens occasionally.

Useful facts help move the discussion forward.

Look at recent examples. Count how often information is missing. Record how long work waits for approval. Review how many jobs need repeating.

Keep the measures simple and relevant.

If the problem is a slow response to customers, measure response time. If staff are entering details twice, look at the time spent and the errors involved.

Consider the amount and type of work, too. A busy month may produce more errors simply because more jobs were completed.

ISO includes decisions based on evidence among its quality management principles. Reliable information gives a business a stronger basis for deciding what to improve. www.iso.org

You do not need a complicated report. You need enough clear evidence to understand the problem and assess whether a change helps.

Check whether the business has changed around the process

Sometimes a process becomes less useful because the work around it has changed.

A small team may once have shared updates by talking across the office. As the team grows or works from different places, those conversations no longer reach everyone.

A weekly review may have suited a low number of orders. Higher demand may now mean problems wait too long for attention.

Customer needs can change as well.

They may require different information, clearer progress updates or a new delivery arrangement.

Review processes when there is a meaningful change in the business. Growth, new equipment, different services and staff changes can all affect how work should be managed.

Ask whether the old method still fits the new situation.

Keeping a process unchanged does not always keep the level of risk unchanged.

A method that worked well for five people may need adjustment when twenty people depend on it.

Use internal audits to ask better questions

An internal audit is a structured review of how work is managed.

It can help you check whether people follow agreed methods and whether those methods support the results you need.

Its value grows when the review goes beyond checking that a form exists.

Follow a real job. Speak to the people involved. Compare the written instructions with what happens in practice.

If everyone uses a different method, find out why.

The instruction may be unclear. It may be difficult to find. It may describe work that has changed.

If people follow the process but still face delays or repeat mistakes, review the process itself.

Useful questions include:

“Where does work stop?”

“What do you need that you do not receive?”

“Which checks help, and which cause confusion?”

The findings should help managers choose practical actions.

An audit that produces the same unresolved issue each time offers limited value. The business needs to act and review what happens next.

Make leadership decisions part of improvement

Some process problems cannot be solved by the person doing the task.

Staff may need better equipment, clearer priorities or permission to change an approval step. They may be struggling with promises made elsewhere in the business.

Leaders need to understand these limits.

If the team keeps reporting the same difficulty, ask what decision or support is missing.

A manager may need to agree who owns a task. Senior leaders may need to review workloads. Different departments may need to settle how information should be shared.

Improvement needs time as well as encouragement.

Telling people to suggest changes while leaving them no time to review or test anything can make the request feel empty.

Give important issues a clear owner and a sensible review date.

Then check progress.

When leaders take practical action, they show that quality is part of running the business rather than an extra task for one person to manage.

Test a change before applying it widely

Once you find a weak point, it can be tempting to change everything at once.

A smaller test often makes learning easier.

Suppose customer orders frequently arrive with missing details. Your team suggests a revised order form.

Try it with a suitable group of jobs. Explain what you want it to improve and ask staff to record any difficulties.

Review whether orders arrive with better information. Check whether customers understand the questions and whether the form creates extra work elsewhere.

Use what you learn to adjust it.

The test should suit the importance of the process. Changes affecting safety, legal duties or other serious matters need appropriate checks and approval before use.

For routine work, a limited trial can reveal problems without disrupting the whole business.

It also gives you a clearer answer to an important question: does this change improve the result, or does it simply make the process different?

Explain the change and update the guidance

Even a sensible improvement can fail if people do not understand it.

An email saying “please use the new process” may leave staff unsure about what has changed or why.

Explain the problem you are trying to solve. Show people the new method and give them a chance to ask questions.

Make clear when it starts, who it affects and where the current instructions are kept.

Remove old copies from everyday use where appropriate, so people do not have to guess which version to follow.

Check understanding through the work itself.

Can someone complete the task using the new guidance? Do they know what to do when information is missing?

Ask for feedback after the change has been used for a while.

People may spot difficulties that were not obvious during planning.

Keeping that conversation open helps the business improve the method before a new problem becomes another familiar habit.

Review the result, not just the completed action

Changing a form is an action.

Reducing missing information is a result.

Holding training is an action. Helping people complete the task correctly is the result you are looking for.

This difference matters.

A business can complete every item on an action list without solving the original problem.

Before making a change, agree how you will know whether it has helped.

Use the same measures you used to understand the issue, where they remain suitable. Compare similar work and allow enough time to see a useful pattern.

Speak to staff as well.

Has the change made the task clearer? Are they still finding ways around it? Has a delay moved to another team?

If the result falls short, review the reasons.

The first idea may need adjusting. New information may show that the main cause sits elsewhere.

Learning from the result is part of improvement, even when the first attempt does not work.

The benefits of an ISO consultant’s support

An outside view can help when familiar work has become difficult to question.

One of the benefits of an ISO consultant’s support is having someone ask about the purpose of a process without sharing the assumptions built around it.

A consultant can help your team review real work, compare it with agreed methods and identify areas that need attention.

They can also explain ISO 9001 in plain language and support more useful internal audits, clearer instructions and practical improvement plans.

For example, they may help investigate why orders keep returning for correction or why the same issue appears at each review.

The business still needs to make decisions and carry out the work.

A consultant cannot guarantee that every change will succeed or that errors will disappear.

Useful support builds your team’s understanding. It helps people ask better questions, use evidence and manage the system with more confidence, so improvements remain part of daily work.

Choose one habit to question this week

You do not need to challenge every process at once.

Start with one task that causes repeated frustration, delay or extra work.

Ask the people involved to explain what happens and why. Follow a recent example. Check the purpose of each step and gather enough evidence to understand the difficulty.

Then agree one change worth testing.

Keep any controls the business needs. Explain the new method, give someone responsibility for the trial and set a date to review its effect.

A useful starting point is a task your team regularly describes as “just the way we do it”.

At your next meeting, ask:

If we designed this task today, with what we now know, would we do it the same way?

Use the answers to look more closely.

Some habits will stand up well to that question. Others will reveal a chance to make work clearer, reduce repeated mistakes or save time.

That is where a practical improvement can begin.