Make Small Mistakes Useful Before They Become Expensive

A warehouse assistant catches the wrong delivery address before a vehicle leaves. A payroll officer spots a duplicated allowance before salaries are processed. A clinic receptionist notices that two patient files have similar names.

Nothing disastrous happens. Everyone carries on.

But each incident contains useful information: somewhere, a process made an error possible. If the organisation only learns from mistakes that cause visible damage, it wastes these cheaper opportunities to improve.

For HR leaders, managers and executives across East Africa, this is a practical reason to care about psychological safety. The goal is not simply a workplace where people feel comfortable. It is a workplace where useful information reaches the people who can act on it—even when that information includes, “I got something wrong.”

Treat near misses as operational information

A near miss is an incident that could have caused harm or loss but did not. It might involve safety, money, service quality, stock, personal information or customer trust.

Consider a hypothetical distributor in Kampala. A dispatch clerk notices that two customers have almost identical names. She corrects a delivery note before loading begins. Her manager thanks her, but nobody records the confusion.

A month later, another clerk encounters the same problem and the goods reach the wrong customer.

The first incident was not merely a successful correction. It was an early warning about the customer identification process.

Leaders should ask a different question after a close call: not only “Was it fixed?” but also “What allowed this to happen, and could it happen again?”

That question turns a private correction into organisational learning.

Make admitting an error compatible with competence

Froedtert & MCW describes psychological safety as the belief that someone can share ideas, ask questions or admit mistakes without fear of embarrassment, rejection or punishment.

The reference to mistakes matters. Employees may comfortably suggest a new uniform while feeling unable to acknowledge an incorrect stock count. An invitation to contribute ideas does not automatically make error reporting safe.

Managers help establish the difference through everyday reactions. Compare these responses:

• “How could you make such a basic mistake?”
• “Thank you for flagging it. What needs correcting now, and what made the mistake possible?”

The second response does not excuse the error. It makes correction and understanding possible before blame dominates the conversation.

Leaders can also acknowledge their own ordinary errors: an unclear instruction, a missed approval or an unrealistic deadline. The useful part is not the confession alone. It is explaining what they changed afterwards.

Keep accountability, but separate the questions

Psychological safety is not a promise that every action will be consequence-free. Deliberate wrongdoing, harassment, fraud and serious breaches still require appropriate investigation and action.

A discussion from the Catalyst Center for Work Innovation highlights the combination of psychological safety and rigorous accountability. For managers, that means making room for honest disclosure while maintaining clear standards.

When something goes wrong, separate three questions:

1. What needs immediate protection or correction? This might involve a customer, employee, payment or piece of equipment.
2. What conditions contributed? Look at instructions, workload, training, handovers, access permissions and equipment.
3. Does anyone's conduct require a separate process? Establish facts fairly rather than treating an unfortunate outcome as proof of misconduct.

An employee following an outdated checklist is not in the same position as someone deliberately bypassing a known control. Responding identically to both can discourage honest reporting without addressing the underlying risks.

Add a short learning review to existing work

Most organisations do not need another long meeting. A short discussion within an existing branch, department or shift meeting can be enough to examine one recent near miss.

Use four prompts:

• What nearly went wrong?
• How was it caught?
• What made the error easy to make?
• What one change would reduce the chance of repetition?

Keep the conversation focused on the work, not on identifying someone to embarrass. Avoid circulating personal details when a process-level explanation will do.

In a multi-branch business, the change might be a clearer customer identifier. In a hospitality operation, it might be a more reliable shift handover. In an NGO, it might be removing contradictory instructions from an expense form.

Assign an owner and a check-back date. Otherwise, the discussion becomes another record of a problem everyone understands but nobody resolves.

Let people contribute outside the meeting

Not every useful observation will emerge in a group discussion. A junior employee may hesitate in front of a supervisor. Someone working nights may never attend the management meeting. Another person may worry that a detailed example will expose a colleague.

The WebMD Health Services definition of psychological safety includes asking questions, sharing concerns and admitting mistakes. Organisations need practical ways to support all three—not just a lively meeting culture.

Offer more than one route: a direct conversation, an appropriate reporting contact and an identity-protected digital channel. Explain which route to use for urgent danger or serious allegations; a suggestion box should not replace emergency procedures or formal safeguarding responsibilities.

Suggestion Box Ai provides an Identity Protected digital suggestion box where staff can submit ideas, complaints and reports without revealing who they are. Admins can reply through private reply codes, vote on ideas, and use AI triage and reports. Human leaders still need to assess context and take responsibility for decisions.

Measure changes, not the appearance of perfection

A department reporting no mistakes is not necessarily the department with the strongest controls. Silence alone tells you little about operational reliability.

Instead, track whether reported issues produce useful changes. Which recurring problems have been addressed? Were agreed actions completed? Did a revised handover or checklist actually help staff?

Share brief learning updates without exposing individuals: “Dispatch staff flagged confusion between similar customer names. Customer numbers are now required on loading documents.”

That closes the loop and gives employees a concrete reason to contribute again. The message is simple: reporting a problem can improve the work, not merely create trouble for the reporter.

Give everyday learning a place to start

Suggestion Box Ai plans are Core at $10, Assist at $20 and Executive at $50 per month, with a 30-day free trial. To give staff another way to share useful observations before small problems become expensive, start your free 30-day trial.