Quality management

Why it matters

Poor quality is expensive in ways that rarely appear on one line of the accounts: rework, warranty call-backs, credits and refunds, staff time spent apologising, and customers who leave quietly. Many businesses spend a large share of their effort on correcting mistakes that a small amount of prevention would have avoided. Consistent quality is also the foundation for growth: you cannot delegate, franchise or scale what you cannot reliably reproduce.

Define what good looks like

You cannot manage quality you have not defined. For each product or service you deliver, write down the standard in terms the customer would recognise and the team can check: the coffee is served within four minutes at this temperature; the invoice matches the quote with no unexplained lines; the site is left clean and photographed before leaving. Standards should be observable, so that two people would agree whether the work met them.

Involve the people doing the work and, where you can, the customer. Ask what "done well" means to them and where they have been let down before. The result is a short set of standards per service, which become the basis of your SOPs, your checks and your training.

• Make each standard observable and checkable, not a vague adjective.
• Base standards on what customers notice and complain about.
• Keep the list short: five to ten standards per service is plenty to start.
• Build them into SOPs and onboarding so they are taught, not assumed.

Understand the cost of quality

Quality costs fall into four buckets. Prevention is what you spend to stop defects happening: training, clear procedures, good suppliers, maintained equipment. Appraisal is what you spend checking: inspections, test batches, reviewing work before it goes out. Internal failure is the cost of defects you catch before the customer sees them: rework, scrap, wasted time. External failure is the cost of defects the customer finds: refunds, warranty, repeat visits, lost customers and damaged reputation.

The pattern that matters is that costs rise steeply down this list. A dollar of prevention saves many dollars of external failure. Most small businesses under-spend on prevention and appraisal and absorb failure costs without ever adding them up. Simply tallying rework hours, credits and call-backs for a quarter is usually enough to justify the investment in doing it right the first time.

Check work before the customer does

Quality control is the checking step: comparing output against the standard before it leaves the business. The form it takes depends on the work. A manufacturer inspects a sample from each batch. A trades business has a second person photograph the completed job against a checklist. A professional services firm has every deliverable reviewed by someone other than its author. A café tastes the first coffee from each new bag of beans.

Checks cost time, so place them where defects are most likely or most expensive: at hand-offs, after new staff or new suppliers, and immediately before the customer sees the result. Record what the checks find, because the record is what lets you spot patterns and fix causes.

Fix causes, not symptoms

When a defect or complaint occurs, the instinct is to fix it for that customer and move on. Do that, and then ask why it happened, repeatedly, until you reach something you can change in the process. A wrong order was packed because the pick list was unclear because the product codes are similar because nobody owns the product catalogue. Fixing the catalogue prevents the next hundred wrong orders; apologising fixes one.

Run this as a simple log: date, what went wrong, root cause, action taken, owner, and whether it recurred. Review the log monthly. Over time the same few causes will appear repeatedly, and those are your improvement agenda. This habit, run through the plan-do-check-act cycle, is what people mean by continuous improvement. Businesses that sell software or depend heavily on systems can apply the same discipline to testing and release; SMBH Consulting’s quality engineering practice helps with that end of the spectrum.

How to build quality into a small business

1. Write standards for each service Five to ten observable, checkable statements of what good looks like, drawn from what customers notice.
2. Tally your cost of quality For one quarter, record rework hours, scrap, credits, refunds and call-backs. Put a dollar figure on it.
3. Add a check before the customer A second person with a short checklist at the point of release or hand-over.
4. Start a defect and complaint log Date, issue, root cause, action, owner, recurrence. Make logging easy and blame-free.
5. Ask why until you reach the process For each logged issue, trace the cause to something you can change in procedures, training, suppliers or equipment.
6. Run one PDCA improvement a month Pick the most frequent cause, plan a change, trial it, check the numbers, adopt or adjust.
7. Review quality numbers monthly Defect rate, complaints, rework and cost of quality, alongside the financials.

Real-world example

A Brisbane commercial cleaning company cuts call-backs

Clearview Commercial cleans offices and medical suites with 22 staff across night shifts. Clients call back about missed areas roughly 14 times a month across about 380 jobs, and each call-back costs a supervisor visit and typically two hours of labour, around $150 each, or about $2,100 a month before counting the two contracts lost that year. The owner writes a twelve-point standard for each site type with clients and starts a call-back log.

Within two months the log shows that most call-backs trace to three causes: new cleaners not knowing site-specific requirements, meeting rooms being locked at the usual time, and bins on upper floors being skipped when the lift is out of service. He adds a site card with photographs to every job, a supervisor photo-check of five random areas at the end of each shift, and a rule that locked rooms are reported before leaving site rather than silently skipped. Call-backs fall to three or four a month within a quarter, saving around $1,500 a month in direct cost, and the business wins a medical centre contract that requires documented quality checks.

Common mistakes

• Inspecting quality in at the end Checking only the final output catches defects after the cost is spent. Prevent upstream with standards, training and good inputs; check at hand-offs.
• Blaming people instead of processes Most defects come from unclear standards, poor tools or bad hand-offs. Blame drives problems underground; a blame-free log brings them out.
• Fixing the symptom only Resolving the complaint without asking why guarantees it comes back. Ask why until you reach something in the process you can change.
• Not counting the cost of quality Rework, credits and call-backs are spread across the accounts and feel like business as usual. Add them up once and the case for prevention makes itself.
• Over-documenting to chase a certificate Pursuing ISO 9001 before the basic habits exist produces paperwork without quality. Build the habits, then certify if customers require it.

KPIs to track

• Defect or error rate Defects per hundred jobs, orders or deliverables. Define a defect clearly and track the trend monthly.
• Right first time Share of work completed without rework or correction. The positive mirror of defect rate.
• Complaints and call-backs Count per month, and per hundred jobs so growth does not hide improvement.
• Cost of quality Rework hours, scrap, credits, refunds and warranty as a share of revenue. Should fall as prevention improves.
• Recurrence rate Share of logged issues that happen again after a fix. High recurrence means you are fixing symptoms.

Frequently asked questions

Do I need ISO 9001 certification?

Only if your customers or tenders require it, which is common in government, construction and manufacturing supply chains. The habits in this article are the substance of such a system; certification adds documentation and external audit. Build the habits first.

What is the difference between quality control and quality assurance?

Quality control checks outputs against the standard. Quality assurance designs the process so that defects are less likely in the first place: procedures, training, supplier selection. Most small businesses need more assurance and smarter control, not more inspection.

How do I get staff to report problems?

Make logging quick, treat every report as useful information rather than a confession, and visibly fix things that are reported. Reporting rises when people see it leads to improvement rather than blame.

Does quality management apply to a service business?

Completely. Services are harder to inspect, so standards and second-person review before delivery matter even more. Response times, accuracy, and how problems are handled are all measurable.

Key takeaways

• Quality is consistency against a promised standard, not luxury; it is what creates repeat business.
• Define observable standards for each service and build them into procedures and training.
• Prevention is far cheaper than failure; add up your cost of quality to see the case.
• Check work with a second pair of eyes before the customer sees it, and record what you find.
• Fix root causes through a monthly plan-do-check-act loop driven by a blame-free issue log.