TRADE MERCHANT HUB · LEARN

Operations & StockLeadership & Management

Making operational standards stick

Reduce process drift and dependence on individuals by making essential standards practical, repeatable and owned.

11 questions answered

Questions answered on this page

01Why do good processes get ignored at branch level?
02How do I standardise operations without creating unnecessary bureaucracy?
03What processes should every merchant branch follow?
04How do I make operational standards stick?
05Who should own operational standards?
06How often should branch standards be reviewed?
07How do I make sure new employees learn the right way of doing things?
08How do I stop shortcuts becoming normal practice?
09Why does performance fall when an experienced manager leaves?
10How do I reduce dependence on individual employees?
11How do I make a business easier to run consistently?

Why do good processes get ignored at branch level?

Processes are often ignored when they feel disconnected from the pressure and decisions of the branch. They may be too detailed, difficult to find, designed without input from users or contradicted by targets and leadership behaviour. An instruction to protect stock accuracy will not hold if speed is always praised and corrections are tolerated later. Managers may also believe local experience gives them a better method, particularly when nobody reviews the agreed standard. Start by identifying whether the process is essential, workable and understood. Observe how the task is actually performed and why people depart from it. The cause may be poor discipline, but it may also be an unrealistic process, missing tools, unclear ownership or competing expectations. A good process only becomes useful when normal work supports it.

How do I standardise operations without creating unnecessary bureaucracy?

Standardise the parts of the operation where inconsistency creates material customer, safety, stock, cash or commercial risk. Keep the required outcome, ownership and essential steps clear, while allowing local judgement where different customer or branch conditions genuinely matter. Involve branch teams in testing whether the standard works under real counter, yard, warehouse and delivery pressure. Remove duplicate forms and approvals that do not improve control. A standard should make the right action easier to understand and repeat, not create a document for every possibility. Use short guidance, visible measures and proportionate review. Bureaucracy grows when controls exist without a clear risk or decision behind them. Useful standardisation protects the business while leaving managers responsible for sensible local execution.

What processes should every merchant branch follow?

Every branch needs reliable processes around the risks and customer promises central to the business. These normally include opening and closing controls, cash and credit handling, pricing authority, stock receipt and adjustment, picking and delivery, returns and credits, safety, housekeeping, complaints and the handover of important customer commitments. The exact list depends on the merchant model, branch format and central support available. Prioritise processes where failure can harm people, customers, cash, margin, stock accuracy or legal compliance. Avoid treating every routine as equally critical. Define the minimum standard, named owner and evidence that shows it is working. Branches can then adapt lower-risk activity without weakening the controls the wider business depends on.

How do I make operational standards stick?

Standards stick when they are clear, workable, taught through real tasks and reinforced by managers in normal branch routines. Explain the reason behind the standard and the risk it controls. Give one person clear ownership, make the expected evidence visible and review it often enough for drift to be noticed early. Managers must respond consistently when shortcuts appear, including when the branch is busy or the shortcut produces a short-term result. Use feedback from branches to improve a standard that is genuinely impractical, but do not allow silent local versions to multiply. The aim is not perfect compliance theatre. It is repeatable behaviour that protects customers, colleagues, stock, cash and performance even when experienced people are absent.

Who should own operational standards?

Ownership should sit with a role that can maintain the standard across the business, but branch managers must own its local execution. Central operations or the relevant functional leader may define the minimum requirement, provide guidance and review recurring failures. The branch manager should ensure people understand it, have the tools to follow it and correct drift. Individual tasks can have named owners, but accountability should not disappear between departments. Be explicit about who approves changes, who checks performance and who acts when the standard cannot be met. Shared interest is not shared ownership. When everybody is described as responsible, problems are often passed between branch, regional and central teams until a senior leader intervenes.

How often should branch standards be reviewed?

Review frequency should reflect the risk, rate of change and evidence of drift. Safety-critical, cash, credit or high-volume stock controls may need frequent operational checks, while a stable lower-risk process may only need periodic review. Separate checking whether people follow the standard from reviewing whether the standard itself remains useful. A branch opening, system change, recurring complaint, stock loss or repeated workaround should trigger an earlier review. Avoid annual exercises that produce a burst of paperwork and little behaviour change. Use a proportionate rhythm, sample real evidence and compare themes between branches. The right frequency is often enough to identify deterioration before it becomes normal, without turning managers into full-time auditors.

How do I make sure new employees learn the right way of doing things?

Give new employees a structured introduction to the tasks, standards and risks relevant to their role. Combine clear guidance with demonstration, supervised practice and confirmation that they can perform the task correctly. Use experienced colleagues carefully; length of service does not guarantee that their version matches the agreed standard. Explain why key controls matter, particularly around safety, stock, credit, pricing, customer commitments and equipment. Managers should review learning during the first weeks rather than assume induction is complete because information was issued. Keep a reliable record of essential training, but focus on demonstrated behaviour. New employees learn the real standard from what colleagues and managers do under pressure, not only from what the induction document says.

How do I stop shortcuts becoming normal practice?

Address shortcuts while they are still exceptions. Understand why the agreed method is being bypassed, then decide whether the standard, resources or behaviour needs correction. A shortcut may reveal an unnecessary step, but it may also shift risk into stock errors, credits, safety, margin or customer service that appears later. Managers weaken the standard when they overlook the shortcut during busy periods and challenge it only after a loss. Make the consequence visible, correct the immediate issue and remove the cause where possible. If a better method has genuinely been found, approve and communicate the change properly. The business should learn from practical improvement without allowing every branch to create its own untested process.

Why does performance fall when an experienced manager leaves?

Performance falls when important knowledge, relationships and controls were held by the individual rather than built into the branch. The manager may have remembered customer commitments, corrected stock informally, approved exceptions and coached people without making the approach visible. Their capability disguised weak processes, unclear ownership or an undeveloped team. When they leave, decisions slow and gaps appear together. Identify which outcomes depend heavily on one person and transfer knowledge before a departure is announced. Build deputies, document essential controls and ensure information sits in recognised systems rather than private notes or memory. The aim is not to remove the value of experience. It is to stop the branch losing control because experience was never converted into shared capability.

How do I reduce dependence on individual employees?

Start by finding tasks, decisions and relationships that only one person understands or can complete. Assess the consequence if that person is absent, then prioritise the highest customer, safety, cash, stock or commercial risks. Clarify the process, store information in an accessible place and train at least one suitable colleague through real practice. Rotate appropriate responsibilities and test cover during planned absence rather than waiting for an emergency. Avoid treating every specialist skill as a problem; expertise is valuable. The risk arises when knowledge is hidden, authority is unclear or nobody else can recognise an error. Reducing dependency creates resilience and development opportunities while allowing experienced people to spend less time being the only answer.

How do I make a business easier to run consistently?

Make the essential work clear, remove avoidable variation and give managers reliable information about the outcomes they own. Focus first on the few processes that protect customers, margin, stock, cash, safety and people. Define minimum standards, decision boundaries and escalation routes, then ensure systems and targets support them. Develop cover for key roles and remove duplicate reports or local workarounds that create confusion. Consistency does not mean every branch behaves identically. It means the business can rely on important controls and service commitments while managers apply judgement within clear limits. A business becomes easier to run when normal performance depends on a sound operating model, not constant reminders and exceptional effort from a small number of people.

What you may be seeing

Branches follow different versions of the same stock, credit, returns or customer-service process.
Standards improve briefly after an audit or incident and then drift back under daily pressure.
New employees learn mainly by copying whoever happens to be available.
Experienced managers hold important controls and customer knowledge in memory rather than shared systems.
Operational reviews identify repeated exceptions but rarely correct the process or ownership beneath them.

What good looks like

A consistent merchant business is clear about the standards that protect customers, people, stock, cash and commercial performance. Those standards are practical, easy to find and understood in the context of real branch work. Central teams own the minimum requirement and branch managers own local execution, with clear routes for improving a process that no longer works. New employees learn through demonstration and supervised practice. Managers notice drift early and respond consistently, including during busy periods. Essential knowledge is shared through systems, capable cover and developed teams. Branches still use local judgement, but the business does not depend on shortcuts or individual memory to remain under control.

What may be happening underneath

Purpose: People have been told what to do without understanding the customer, safety or commercial risk the standard protects.
Practicality: The documented process does not fit the tools, capacity or sequence of work in the branch.
Ownership: Central and branch teams assume the other is responsible for maintaining and correcting the standard.
Leadership: Managers tolerate shortcuts during busy periods or model a different behaviour from the one being requested.
Capability: Training transfers information but does not confirm that employees can perform the task reliably.
Dependency: Knowledge and control sit with experienced individuals rather than the operating model and wider team.

Questions worth asking

01Which process failures create the greatest customer, safety, stock, cash or margin risk?
02Where does actual branch practice differ from the documented standard, and why?
03Can each manager explain which standards they own and the evidence that shows they are working?
04Which tasks or decisions would stop if one experienced employee were absent?
05What are our leaders rewarding or tolerating when the branch is under pressure?

Where to go next

Turn agreed standards into normal branch practice. BGC operational resources help merchant leaders clarify essential processes, strengthen ownership and reduce the variation and dependency that make branches harder to run.

Take the Business Control Score Explore Operations & Standards toolkits