Standards often start slipping as a business grows because the informal mechanisms that used to maintain those standards stop scaling.

When the company was small:

You saw everything.

You knew every employee.

New starters worked beside experienced people.

Mistakes reached you quickly.

Customers spoke directly to you.

You knew what “good” looked like.

If something wasn't right, you corrected it.

Then the business grew.

More customers.

More employees.

More managers.

More locations perhaps.

More projects.

More handovers.

More distance between the owner and the actual work.

Suddenly you hear yourself saying:

“We never used to let work go out like this.”

Probably true.

But the important question is not:

“Why don't people care like we used to?”

It is:

“What maintained the standard when we were smaller, and what has replaced it now that I can't personally see everything?”

Very often, the uncomfortable answer is:

Nothing.

Growth does not necessarily lower standards

It exposes standards that were never really institutionalised.

This is an important distinction.

Perhaps your business always had incredibly high standards.

But where did those standards live?

In:

Your head?

Your eye for detail?

Your relationships?

Your direct supervision?

A few long-serving employees?

That can work brilliantly with eight people.

Everyone knows:

“Adam would never let that leave the building.”

So they learn.

Not necessarily from an employee handbook.

From proximity.

They see what gets corrected.

They hear customer conversations.

They watch how experienced people work.

They absorb thousands of tiny judgements.

Then the company hires another 20 people.

Those new employees do not have five years of accumulated exposure to the founder.

They need another mechanism.

If one does not exist, standards drift.

“Everyone used to know” is not a scalable management system

This phrase appears constantly in growing businesses.

“Everyone used to know what was expected.”

Of course they did.

There were twelve of you.

You sat in the same building.

The owner spoke directly to everyone.

The original team helped create the routines.

Information travelled through conversation.

Growth changes that.

Thirty people cannot all participate in every decision.

Sixty people do not all hear the same conversation.

Multiple teams develop.

Managers interpret expectations differently.

New employees learn from whoever happens to be standing nearest.

The organisation acquires distance.

Not merely physical distance.

Interpretive distance.

What the owner means by:

“Customer service must be excellent”

gets interpreted by:

Director.

Then manager.

Then supervisor.

Then employee.

Without clearer standards, every layer adds variation.

Bigger businesses need more structured management

This is one reason more structured management practices tend to appear as organisations grow.

The latest published ONS Management and Expectations Survey found average management-practice scores rising with employment size. Firms with 10–19 employees averaged 0.51 on its 0-to-1 management-practice scale, compared with 0.58 for firms with 20–49 employees, 0.63 for 50–99, 0.65 for 100–249 and 0.68 for firms with more than 250 employees. The ONS measures practices including continuous improvement, KPIs, targets, training, promotion and management of underperformance. These are associations rather than proof that simply adding management processes makes businesses better.

The pattern still makes intuitive sense.

As direct owner visibility disappears, something has to replace it.

More deliberate:

Management.

Measurement.

Feedback.

Training.

Accountability.

Process.

That does not mean turning your company into a bureaucracy.

It means recognising that:

“People know how we do things”

has an expiry date.

The first problem: “good” was never properly defined

Ask five people:

“What does good customer service mean here?”

You might receive five answers.

Reply quickly.

Solve the problem.

Be friendly.

Never say no.

Keep customers updated.

Which is correct?

Perhaps several.

But what happens when those principles conflict?

Customer wants something impossible by Friday.

Does good service mean:

Say yes and somehow make it happen?

Or:

Tell them clearly what is achievable and protect delivery standards?

That requires judgement.

Standards need enough definition that people can make reasonably consistent decisions.

A standard needs to be observable

“High quality”

is not particularly useful.

What would I observe?

Maybe:

Customer scope confirmed before work begins.

Final output independently checked against specification.

No unresolved defects at handover.

Customer updated within four hours if delivery date becomes at risk.

Now we can manage something.

Likewise:

“Professional behaviour.”

What does that mean?

Maybe:

Respond to customers respectfully.

Own mistakes.

Do not blame colleagues in front of customers.

Arrive prepared.

Escalate serious problems early.

Again:

Observable.

A standard does not need seventeen paragraphs.

It does need to mean approximately the same thing to different people.

The second problem: new people learn from increasingly inconsistent examples

Your first five employees learned directly from you.

Employees 6–10 learned from those five.

Employees 25–40 may be learning from someone who learned from somebody who learned from you.

That can become a very long game of operational Chinese whispers.

Small deviations spread.

One manager thinks:

“That's close enough.”

Their team learns that version.

Another manager is meticulous.

Their team learns something different.

Soon customers receive different versions of the company depending on:

Branch.

Team.

Shift.

Manager.

Person.

The business has begun developing micro-standards.

Growth amplifies whatever you teach

Good or bad.

Imagine an experienced employee takes a shortcut.

At eight employees, one person takes the shortcut.

At eighty, that person trains another five.

Those five train another twenty.

The workaround becomes:

“How we do it here.”

This is why growth makes consistency more important.

You are no longer managing individual behaviour.

You are managing replication.

Whatever gets copied spreads.

The third problem: onboarding became shorter because recruitment accelerated

You hired occasionally.

New starter spent:

Two weeks shadowing.

Time with owner.

Time with experienced employee.

Plenty of questions.

Then growth arrives.

You recruit:

Five people.

Then eight.

Experienced employees are already busy.

So induction becomes:

Here is your login.

Here is the handbook.

Sit with Dave for the morning.

Off you go.

Two months later:

“The new starters aren't as good as the old team.”

Really?

How much of the difference did the organisation create?

The new employee cannot absorb standards they have never been shown.

Onboarding should teach judgement, not only administration

Induction often covers:

Holiday requests.

Timesheets.

IT.

Policies.

Health and safety.

Useful.

But where does the new employee learn:

What excellent work looks like?

What unacceptable work looks like?

What customers value?

Which mistakes matter most?

When should they stop and ask?

What can they decide independently?

What would make a manager reject the work?

That is the knowledge that protects standards.

Show examples.

Real ones where possible.

This is excellent.

This technically passed, but we would not accept it.

This is why.

People calibrate faster when they can see the difference.

The fourth problem: your best people became managers without becoming managers

Business grows.

You need supervisors.

So you promote:

Best engineer.

Best salesperson.

Best carpenter.

Best administrator.

Best project manager.

Reasonable.

Then they keep doing most of their old job and somehow acquire eight employees as a side project.

Now you expect them to:

Set standards.

Coach.

Review work.

Give feedback.

Manage underperformance.

Develop employees.

Communicate.

Plan capacity.

Deal with problems.

When?

CIPD's 2025 Good Work Index found that employees with more positive perceptions of their line managers were more likely to feel effective in their roles and less likely to report negative health effects or consider leaving. The same research found more managers reporting they had the time, training and knowledge to manage people well, reinforcing the importance of actually investing in management capability rather than simply handing someone a title.

Manager is a job.

Not a reward for technical competence.

Standards increasingly travel through managers

This is the transition owners often miss.

At ten employees, you may directly influence almost everybody.

At fifty, your standards increasingly reach employees through managers.

So your question changes from:

“Do my employees understand the standards?”

to:

“Can my managers consistently teach, model, inspect and reinforce the standards?”

That is a completely different capability.

If Manager A accepts mediocre work and Manager B rejects it, the company does not have one standard.

It has two.

Managers need calibrating too

Put three managers in a room.

Show them examples of completed work.

Ask:

Would you accept this?

Would you send it to the customer?

What would you correct?

When would you escalate?

You may discover surprising differences.

This is extremely useful.

The objective is not to eliminate all judgement.

Different situations require judgement.

You want managers aligned on the important boundaries.

Good enough.

Not good enough.

Needs escalation.

Absolutely unacceptable.

That calibration becomes increasingly important as the business grows.

The fifth problem: volume started winning against quality

This is brutally common.

You tell employees:

Quality comes first.

Then measure:

Jobs completed.

Calls handled.

Sales volume.

Projects closed.

Utilisation.

Revenue.

Speed.

What did you actually prioritise?

Suppose a project manager knows:

Taking another hour to properly review the job protects quality.

But it hurts utilisation and makes the schedule red.

Which signal wins?

Employees notice what management really rewards.

If every meeting focuses on:

Volume.

Speed.

Output.

and quality appears only when a customer complains, you have taught the company something.

Standards collapse when the economics make them impossible

Imagine the standard requires:

Four hours.

Management allows:

Two and a half.

You can put the standard in the handbook as many times as you like.

The operating model contradicts it.

HSE's Management Standards are aimed specifically at work-related stress rather than commercial quality, but their principle around demands is relevant: organisations should provide demands that are achievable within agreed working arrangements and match people's skills and capabilities to the job.

If employees must choose between:

The quality standard.

And:

The workload expectation.

do not act surprised when something gives.

The sixth problem: customer promises keep creating exceptions

Growth brings bigger sales targets.

Sales gets ambitious.

An important customer asks:

“Can you do this differently for us?”

Yes.

Another wants:

Faster turnaround.

Yes.

Another wants:

Different reporting.

Yes.

Then Operations receives 47 versions of:

“Standard service.”

Consistency collapses because the commercial model keeps creating exceptions.

This is closely connected to Article #84.

If ordinary work continually gets overridden by urgent or bespoke requirements, employees cannot maintain a consistent operating standard.

Sometimes bespoke work is commercially sensible.

Price it.

Plan it.

Resource it.

Do not call something standard while designing an exception every Tuesday.

The seventh problem: people stopped receiving fast feedback

When the business was smaller:

You saw a mistake.

Corrected it.

Feedback loop:

Minutes.

Now:

Employee completes work.

Supervisor is busy.

Nobody checks.

Customer receives it.

Problem appears three weeks later.

Perhaps nobody even feeds the complaint back to the employee.

Feedback loop:

Weeks.

Standards drift when the distance between:

Action.

And:

Consequence.

gets too long.

Acas's current performance-management guidance recommends combining formal reviews with regular informal performance conversations, feedback, coaching and check-ins rather than relying on an annual appraisal to address performance.

That matters because employees need to know:

What was good?

What needs improving?

Soon enough to change the next piece of work.

Annual appraisals cannot carry your quality system

Imagine someone produces slightly below-standard work for ten months.

December:

“A few areas for improvement...”

Bit late.

Standards are built through:

Daily observation.

Quick correction.

Coaching.

Regular check-ins.

Examples.

Peer feedback.

Formal performance processes when necessary.

Do not save everything for the annual ritual.

The eighth problem: small errors became statistically more visible

This deserves nuance.

Sometimes owners believe quality has collapsed when the percentage has barely changed.

Suppose at small scale you completed:

100 jobs.

Two had problems.

2%.

Now:

1,000 jobs.

Twenty have problems.

Still:

2%.

But you now hear about twenty failures rather than two.

It feels dramatically worse.

Maybe standards have not declined.

Volume increased.

Before launching a cultural crusade, measure.

Look at:

Defect rate.

Complaint rate.

Rework percentage.

Credits.

Returns.

Missed deadlines.

Customer retention.

Not just absolute incident count.

Growth creates more opportunities for failure.

You need to distinguish:

More failures.

from:

A higher failure rate.

But unchanged percentages may still be unacceptable

Even if the rate remains:

2%.

At ten times the volume, those twenty failures may create:

Far more reputation risk.

Management time.

Rework.

Cost.

Customer impact.

So scale can still justify improving the system.

Just diagnose accurately.

The ninth problem: the owner still tries to be final quality control

This works for a while.

Business grows.

Owner keeps checking:

Quotes.

Projects.

Products.

Emails.

Customer issues.

Eventually you become the bottleneck.

So one of two things happens.

Either:

Everything waits for you.

Or:

Things bypass you because there is too much.

Now standards become inconsistent.

The objective is not to get better at personally inspecting 1,000 things.

It is to create a system where quality survives without your eyes on every output.

That is a huge leadership transition.

Stop being the standard

Build one.

This is the heart of the problem.

If employees say:

“Adam likes it done this way.”

you still have a founder-dependent standard.

Better:

“This is the accepted company standard, and here's why.”

Now the organisation can teach it.

Inspect it.

Improve it.

Defend it.

The founder's judgement may have created the standard.

It should not need the founder's physical presence forever.

The tenth problem: consequences became inconsistent

Employee produces weak work.

Manager A corrects it.

Manager B ignores it.

Senior employee gets away with it because:

“They're difficult to replace.”

New employee gets hammered for the same thing.

What is the standard now?

People watch what happens.

Article #81 covered this from the wider culture perspective.

Standards require consistency.

Not identical treatment in every circumstance.

But broadly predictable expectations.

Acas performance guidance recommends making expectations clear and assessing employees against agreed objectives and behaviours, with appropriate support and regular feedback where improvement is needed.

If poor standards carry no consequence, they eventually become normal.

The eleventh problem: long-serving employees are not automatically guardians of the old standard

This can be awkward.

Owners sometimes divide the workforce into:

Original people who get it.

And:

New people who don't.

Sometimes true.

Sometimes not.

A long-serving employee may have accumulated:

Shortcuts.

Cynicism.

Outdated methods.

Territory.

They may actively teach new employees:

“Ignore that. Nobody actually does it.”

Do not judge quality by tenure.

Judge quality by quality.

Your strongest cultural carrier might have joined eighteen months ago.

Your biggest source of drift might have been there fifteen years.

The twelfth problem: nobody owns quality anymore

When the business was small:

You did.

Now?

Operations says:

Managers.

Managers say:

Employees.

Employees say:

Quality team.

Quality team says:

Operations.

Customer says:

“Can somebody please just fix it?”

Quality should be everyone's concern.

But that does not mean accountability should be vague.

Who owns:

The standard?

Training?

Measurement?

Recurring failure?

Improvement?

The quality function, if you have one, may support the system.

Managers still need to own the standard inside their teams.

Do not create a Quality Department so everyone else can stop caring

This is a trap.

Quality Inspector catches problems at the end.

Employees begin to think:

“They'll check it.”

Now quality is outsourced internally.

Inspection has value.

Especially in:

Safety-critical.

Regulated.

Technically sensitive.

High-value work.

But the best place to protect quality is as close as possible to where the work is created.

Employees should understand what good looks like and be capable of checking their own work.

Managers should maintain standards.

Inspection becomes verification.

Not rescue.

Current quality-management thinking still centres on leadership and continual improvement

The newly published ISO 9001:2026 places renewed emphasis on leadership, quality culture, strategic alignment, people and continual improvement while retaining the long-standing process and customer-focus principles of the ISO 9000 family. A company does not need ISO certification for those underlying principles to be useful.

The interesting point is that mature quality systems do not rely on:

“Tell everyone to try harder.”

They rely on:

Clear expectations.

Process.

Leadership.

People capability.

Measurement.

Learning.

That is exactly what a growing business needs.

The thirteenth problem: issues get fixed but not learned from

Customer complains.

Manager sorts it.

Refund issued.

Customer happy.

Close.

Same thing happens next month.

This is service recovery.

Not organisational learning.

Standards improve when failure feeds back into:

Training.

Process.

Product.

Equipment.

Management.

Workload.

The latest ONS Management and Expectations Survey includes continuous improvement as a core part of structured management practice, explicitly distinguishing firms that repeatedly review processes to minimise future problems from those that simply react to issues as they arise.

Fix the customer.

Then fix the reason the customer needed fixing.

The fourteenth problem: growth changes the job before the role catches up

Your employee used to:

Manage eight customers.

Now:

Twenty-five.

Same job title.

Same process.

Same quality expectation.

Very different job.

Or:

Supervisor used to manage four people.

Now:

Fourteen.

You are surprised they spend less time coaching.

The role changed.

HSE guidance on role design emphasises that employees should understand their responsibilities and that organisations should avoid incompatible or conflicting demands where possible.

When businesses grow quickly, role design often lags behind reality.

Standards then suffer because nobody consciously redesigned the work.

The fifteenth problem: management capacity did not grow at the same rate as headcount

This is one of the biggest.

Twenty employees.

Three managers.

Then:

Forty-five employees.

Still three managers.

Management workload more than doubled.

But leadership assumes:

“They already know how to manage.”

Now:

One-to-ones disappear.

Training gets rushed.

Quality checks get skipped.

Problems arrive late.

Underperformance lingers.

Managers become firefighters.

CIPD's evidence on line management is particularly relevant here because capability is not enough on its own. Managers also report needing time and organisational support to manage people effectively.

Ask:

How much real management capacity does the next stage require?

Not:

How thinly can we stretch the current managers before somebody breaks?

The sixteenth problem: the organisation outgrew informal communication

Someone changes a standard.

At twelve people:

Mention it Monday morning.

Done.

At sixty:

Did Sales hear?

Night shift?

Remote employees?

New location?

Subcontractors?

Employees on leave?

Communication needs designing.

Not overengineering.

Perhaps:

Manager briefing.

Updated process.

Short training clip.

Team discussion.

Worked example.

The exact method does not matter.

The standard needs to reach everybody who relies on it.

HSE's guidance on organisational change emphasises timely information, employee understanding of likely impact and appropriate training where roles or ways of working change.

A change nobody understood is not an implemented change.

The seventeenth problem: your standards have become contradictory

Leadership says:

Spend time with customers.

Also:

Reduce non-billable time.

Leadership says:

Check everything thoroughly.

Also:

Increase output 25%.

Leadership says:

Take ownership.

Also:

Ask before making decisions.

Leadership says:

Protect quality.

Also:

Never miss a sales promise.

Employees are forced to choose which standard actually wins.

Then managers complain they chose incorrectly.

Review conflicting expectations.

Standards need hierarchy.

When quality, speed and cost conflict, what matters most?

There may be different answers depending on the situation.

Make those trade-offs understood.

Growth requires standards to become more explicit, not more bureaucratic

This distinction matters.

I am not suggesting you respond to growth by writing:

Quality Manual Volume 1–19.

The aim is clarity.

The critical standards might fit on one page.

For each important area:

What outcome is required?

What are the non-negotiables?

What can employees decide?

What requires escalation?

How do we check it?

What happens when it is missed?

Simple.

The process underneath may contain more detail where genuinely required.

Do not mistake document weight for management quality.

Identify the standards that really matter

Not everything deserves equal control.

Choose standards linked to:

Customer outcome.

Safety.

Legal or regulatory obligation.

Margin.

Reputation.

Critical delivery performance.

Perhaps:

Quotation accuracy.

Installation quality.

Response time.

Project handover.

Invoice accuracy.

Technical compliance.

Focus there first.

If management treats:

Wrong font on internal form

and:

Serious customer defect

with equal intensity, employees stop understanding what matters.

Build a Standards Ladder

I would start with four levels.

Non-negotiable

Safety, legal, regulatory, ethical or absolutely critical customer requirements.

No discretion below the defined threshold.

Core company standard

The normal level customers should consistently receive.

Preferred practice

The best normal way of working, with reasonable judgement allowed.

Individual style

Employees can choose.

This avoids trying to standardise every human movement while giving genuine standards the weight they deserve.

Define the acceptance test

For every critical standard ask:

How would a competent manager know whether this passed?

If the answer is:

“They'd just know”

keep going.

Could you define:

Tolerance?

Checklist?

Example?

Customer requirement?

Sign-off?

Measurement?

Photograph?

Test?

Peer review?

A standard becomes scalable when different competent people can reach reasonably similar conclusions.

Use real examples

Especially for subjective work.

Show:

Excellent.

Acceptable.

Not acceptable.

Why?

This is brilliant for:

Design.

Writing.

Customer emails.

Joinery.

Finishes.

Reporting.

Proposals.

Photography.

Technical reports.

People learn far faster from examples than vague exhortations to:

“Maintain quality.”

Train managers to inspect without micromanaging

The answer is not standing over everybody.

Managers need to know:

What needs checking every time?

What can be sampled?

What can employees self-check?

Where is the consequence of failure high enough to require independent verification?

Sampling can be powerful.

Maybe a manager checks:

10% of routine jobs.

100% of high-risk jobs.

New starters more frequently.

Experienced employees less.

Use risk.

Do not make every task pass through another person's hands unnecessarily.

Track the right evidence

Depending on your business:

Rework.

Defects.

Customer complaints.

Credits.

Returns.

First-time pass rate.

Late delivery.

Warranty.

Repeat visits.

Project margin affected by failure.

Again:

Do not build a dashboard with 47 quality measures.

Pick what tells you whether the standard is holding.

Segment the data

Overall defect rate:

3%.

Okay.

What if:

Team A: 1%.

Team B: 7%.

Now we learned something.

Break down where useful by:

Manager.

Branch.

Product.

Service.

New versus established employees.

Customer type.

You may discover company-wide standards are fine.

One part of the organisation is not.

That changes the intervention completely.

Do not automatically blame the manager

If one team performs badly:

Investigate.

Perhaps the manager needs development.

Or:

That team handles the hardest customers.

Has lowest staffing.

Uses old equipment.

Receives worst inputs.

Has impossible targets.

Numbers identify where to look.

They do not always tell you why.

Make customer feedback operational

Do not simply report:

NPS.

Five-star reviews.

Complaints.

Ask:

What specifically are customers telling us about standards?

Are they saying:

Communication deteriorated?

Finish inconsistent?

Deadlines less reliable?

People less knowledgeable?

Response slower?

Then connect customer feedback to the process capable of changing it.

Quality data that never changes behaviour is decoration.

Reset consequences

This is delicate but necessary.

If an employee repeatedly ignores an established reasonable standard despite:

Clear expectations.

Training.

Support.

Feedback.

then eventually you have a performance issue.

Deal with it fairly.

Acas recommends regular performance conversations, clear agreed objectives and support for improvement, with records where appropriate.

Do not allow an endless gap between:

What the company says is required.

And:

What employees learn is actually tolerated.

That gap is the culture.

The owner needs to stop creating exceptions too

If the owner repeatedly says:

“I know that's the standard, but just this once...”

employees notice.

Sometimes exceptions are commercially justified.

Fine.

Call it an exception.

Understand the cost.

Do not pretend the standard remains intact while leadership repeatedly teaches everyone to bypass it.

The owner also needs to stop personally rescuing every standard failure

You see something wrong.

Fix it yourself.

Faster.

Customer protected.

But what did the manager learn?

Perhaps:

Adam will catch it.

Instead:

Correct the immediate risk if necessary.

Then take the issue through the responsible manager.

They need to own:

Correction.

Feedback.

Prevention.

Otherwise the owner remains the invisible Quality Department.

Growth should make quality more organisational, not more founder-dependent

The UK government's August 2026 analysis of high-growth firms found that firms experiencing high growth had persistently higher average management scores than non-high-growth firms, including before entering high-growth periods. The researchers are careful not to claim that a sudden improvement in management automatically causes growth, but the pattern supports the wider point that organisational capability matters in businesses operating at greater scale.

You cannot personally scale your standards indefinitely.

The organisation has to carry them.

I learned this while growing a company myself

When you grow from roughly £1.5 million towards £8.5 million turnover, one thing becomes painfully obvious:

What worked because a handful of experienced people knew how everything should happen stops being enough.

At smaller scale, you can compensate for weakness personally.

You notice something.

Speak to somebody.

Fix it.

At larger scale, you can no longer be present at every point where quality gets created.

That means management, process and accountability have to mature before your personal oversight becomes impossible.

Otherwise growth creates a strange feeling.

The company becomes objectively more successful.

While the owner increasingly thinks:

“We're not as good as we used to be.”

Sometimes they are right.

The answer is not going backwards.

It is building the management infrastructure the larger company now requires.

A 90-Day Standards Reset

If you believe standards are genuinely slipping, I would not start with a company-wide speech about:

“Getting back to basics.”

Do this instead.

Weeks 1–2: Prove where standards are slipping

Look at:

Customer complaints.

Rework.

Returns.

Credits.

Late jobs.

Defects.

Margins.

Manager feedback.

Employee feedback.

Do not rely entirely on owner frustration.

Identify the specific areas.

Week 3: Select the critical standards

Choose perhaps three.

For example:

Job handover quality.

Customer communication.

Finished-work acceptance.

Not twenty-three.

Week 4: Define them properly

For each:

What exactly is required?

What does good look like?

What does failure look like?

Who owns it?

What can employees decide?

What requires escalation?

How is it checked?

Weeks 5–6: Calibrate managers

Put managers through real examples.

Would you accept this?

Why?

What feedback would you give?

When would you intervene?

Make sure the management layer understands the same standard.

Weeks 6–8: Retrain and re-onboard

Existing employees where required.

New-starter induction.

Examples.

Short practical training.

Do not simply email the revised procedure.

Weeks 8–10: Fix structural conflicts

Does workload make the standard impossible?

Do incentives reward speed over quality?

Does Sales create exceptions?

Does equipment cause defects?

Does one manager have eighteen direct reports?

Fix the conditions.

Weeks 10–12: Measure

Has:

Rework fallen?

Complaints reduced?

First-time pass improved?

Manager intervention changed?

Do not settle for:

“Feels better.”

Week 13: Review and tighten

What worked?

What remains inconsistent?

Where did people misunderstand?

What should now become normal management?

Then move to the next important standard.

Do not launch a “quality initiative”

Please.

Banner.

Logo.

Internal campaign.

PROJECT EXCELLENCE 2027.

No.

Just manage the bloody business better.

Quality should become part of:

Onboarding.

One-to-ones.

Team meetings.

Process review.

Manager coaching.

Performance.

Customer feedback.

Normal work.

The objective is not creating excitement about standards for six weeks.

It is creating boring consistency for six years.

Good standards should make work easier

Employees generally do not want to produce rubbish work.

Poor systems frequently make good work unnecessarily difficult.

If maintaining the standard requires:

Extra unpaid hours.

Constant owner approval.

Three duplicate systems.

Workarounds.

Guesswork.

then investigate the environment too.

ISO's current quality-management principles emphasise the interaction between leadership, people, processes, evidence and continual improvement rather than treating quality as an inspection activity sitting at the end of production.

That is the better model.

Create conditions where doing it right is the normal path.

The standard should survive your absence

This is the final test.

You leave for two weeks.

Would:

Customers receive the same experience?

Managers reject the same poor work?

Employees understand what matters?

Problems be corrected?

New starters learn the same expectations?

If standards only hold when the owner is physically present, the business has not scaled its standards.

It has scaled around an inspector.

Growth inevitably creates distance between you and the work.

Your job is not to eliminate that distance.

It is to make sure quality does not depend on closing it personally every day.

Define what good looks like.

Build managers capable of maintaining it.

Give people enough capacity and training to achieve it.

Measure what matters.

Correct deviations early.

Learn from recurring failures.

Apply consequences fairly.

And stop relying on everybody somehow knowing what the founder would have done.

Because as the company grows, standards can no longer live in the owner's head.

They have to live in the business.