I reached a point in our company’s journey where I began facing serious and recurring problems with the front-desk team.
I would teach them something, explain why it mattered and workshop the process with them.
Sometimes, I would simplify the workflow.
Other times, I would create a clearer chart, redesign the instructions or provide a printed guide they could refer to later.
Then an incident would happen, and it would feel as though the conversation had never taken place.
The same mistakes returned. The same explanations were requested. The same responsibilities came back to me.
At my most frustrated, it felt like the team had the memory of a goldfish.
But my first assumption was still that I had failed to explain the process properly.
So I explained it again.
I kept solving the wrong problem
My response was always to improve the teaching.
I changed my technique. I simplified the language. I made workflows easier to follow. I broke processes into smaller steps and removed anything that might create confusion.
Every repeated mistake became another design problem for me to solve.
There is nothing wrong with doing this initially.
Before holding someone accountable, a leader should make sure that the expectation is reasonable, the instructions are clear and the employee has been given the tools and training necessary to perform.
But there comes a point when further simplification stops being leadership.
It becomes compensation.
Without realizing it, I was carrying responsibility that belonged to the team.
They did not have to make sure they fully understood the process because I would explain it again.
They did not have to retain every important instruction because I remained available to reconstruct it.
They did not have to feel the full weight of repeated failures because I kept treating each incident as another coaching opportunity.
My helpfulness had created a form of dependency.
I thought I was supporting the team.
I was teaching them that remembering, following through and maintaining the standard were ultimately my responsibilities.
The change did not come from another workflow
Eventually, my frustration reached a point where my response changed.
When a serious incident occurred, I stopped automatically returning to explanation and retraining.
I became firmer.
When appropriate, repeated failures resulted in verbal warnings. Incidents were formally investigated. Responsibilities were documented, and employees were expected to answer for whether an established process had been followed.
The response from the team changed noticeably.
People paid closer attention.
Processes that had previously seemed difficult to remember suddenly became easier to retain. Expectations that had repeatedly required clarification became much clearer.
The information had not changed.
The consequence of ignoring it had.
That was when I realized that I had misdiagnosed the problem.
It was no longer a training problem.
It was a leadership problem.
Coaching is only one part of leadership
I had been behaving like a supervisor, team leader or coach: someone standing close to the work, correcting mistakes and helping people improve their execution.
Those functions are important.
But leading an organization requires another position.
An organizational leader must make it clear that employees are responsible for understanding their roles, retaining important instructions and applying established standards.
The leader remains responsible for providing clarity.
The employee becomes accountable for what they do with it.
When that distinction is missing, the organization develops an unhealthy pattern:
The leader becomes responsible for explaining.
Then for reminding.
Then for checking.
Then for correcting.
Eventually, the employee performs the task, but the leader carries nearly all the mental responsibility behind it.
That is not delegation.
It is dependency disguised as support.
A four-stage leadership sequence
The lesson I am currently applying, not only with the front desk but across other teams, is to move through four stages.
1. Clarify
Explain the expected result, why it matters and what acceptable execution looks like.
Do not assume that a job title automatically creates understanding.
2. Equip
Provide the training, tools, documentation and authority required to perform.
If the process is unnecessarily complicated, improve it.
3. Verify
Confirm that the employee understands the expectation.
Ask them to explain the process back, demonstrate it or apply it under supervision.
This distinguishes genuine confusion from passive agreement.
4. Hold accountable
Once the expectation has been clarified, supported and verified, repeated failure should no longer restart the entire training cycle automatically.
It must enter the organization’s accountability process.
That might involve documented feedback, a verbal or written warning, a formal investigation, corrective action or another proportionate response.
The purpose is not punishment.
It is to make the standard real.
Firm leadership is not hostile leadership
This lesson can easily be misunderstood.
Firmness without clarity becomes intimidation.
Consequences without proper investigation become arbitrary.
Accountability without adequate support becomes unfair.
But the opposite is also true.
Clarity without accountability eventually becomes a suggestion.
A process that can be repeatedly ignored without consequence is not truly a process. It is a preference expressed by management.
I may discover that parts of my approach need to evolve as the organization grows. Leadership is contextual, and no single method applies perfectly to every person or situation.
But my experience so far has taught me something important:
Not every repeated problem requires a better explanation.
Sometimes the employee already understands.
What is missing is the recognition that understanding and applying the standard are their responsibilities, not responsibilities their leader will continue carrying on their behalf.
Leadership is not only helping people perform.
It is making ownership unavoidable.