Insights · Workplace guidance · 4 minute read

Keep the Lesson You Paid For

An honest mistake can teach someone a lesson the company has already paid for. Give that person a chance to apply it and capture what the rest of the team can use.

By Vitaver Staffing ·

Two questions in an auditorium

Picture an auditorium full of students. A speaker asks, “Raise your hand if you learned anything from a success.” In the story, nobody raises a hand. Then the speaker asks who learned something from a failure or a mistake. Most hands go up. The show of hands captures a familiar experience. A result that goes according to plan may leave your assumptions intact. A result that goes wrong can show you exactly which assumption has to change.

That insight matters at work, where the price of a lesson can be real. A missed handoff costs a day. A defective release disrupts a customer. A proposal built around the wrong requirement takes time to redo. The organization has already paid for that experience. When a manager fires someone for a first good-faith mistake, the company can lose the person who now understands it best. Their next employer may get the benefit of the lesson.

Ask what the team can learn while the details are fresh

Suppose a recruiter submits a qualified engineer for an assignment before confirming a required worksite schedule. The candidate withdraws after hearing about the travel, and the team loses time. Ask the recruiter to reconstruct the handoff. Where was the schedule recorded? What did the recruiter ask the candidate? When did the account manager confirm the client’s requirement? A useful review identifies the step that would have caught the mismatch while there was still time to act.

Have the recruiter and account manager fix that step together. For the next comparable assignment, write the schedule and worksite into the intake, ask the candidate to confirm availability, and check the record before submission. Give someone a date to review a sample of submissions. The test is whether candidates and the client now hear the same terms before an interview is arranged. The recruiter who made the mistake can help teach the correction to colleagues and show that it works.

Google’s site reliability engineering guidance describes a similar practice for reviewing technical incidents. The team records what happened, examines the conditions that contributed to it, and identifies steps to reduce a repeat. That gives managers a practical standard for a review. Make it safe to tell the full story, then assign the fix and follow it through.

Make the next lesson less expensive

A failed attempt is most useful when it changes what people do. For a new process, test the uncertain assumption at a scale you can afford. Pilot a new handoff with one assignment. Try a system change in a test environment. Decide in advance what result would make you change course. Harvard Business School professor Amy Edmondson describes this kind of deliberate experiment as a setting for intelligent failure, where new territory makes a useful result uncertain and the costs can be kept within bounds.

For work with known requirements, use the controls you already have and improve the ones that proved inadequate. If the person made an honest mistake, let them demonstrate the correction under appropriate supervision. If the same error continues after the requirement is clear and support has been provided, make a separate decision about who should do the work. Deliberately hiding an error raises a question about trust. The facts of each case should determine the response.

Keep the lesson in the company

At the next review, ask the person who made the mistake to show the old assumption, the changed practice, and a result that demonstrates the difference. Put the change where the next employee will encounter it, such as the intake form or release checklist. A repair that lives only in one person’s memory leaves the team exposed whenever that person is away.

The next time a capable employee makes a first honest mistake, give them a chance to put the lesson to work. Keep the experience you have already paid for, and make sure the team can use it.

← All Insights