The Employee Who Isn’t You

The Employee Who Isn’t You

The Accidental Manager · Article 3 of 6
By Michael Garrett

You ask someone to sweep the warehouse.

A few minutes later, you watch them work. They started at the wrong end. At least, it looks like the wrong end to you. They’re moving through the space differently than you would. You’ve done this a million times, and you already know how you would get it finished.

You feel yourself wanting to step in.

Before you do, ask yourself: Are they doing it wrong, or are they doing it differently?

It took me a while to learn to pause long enough to answer that question.

I had other things to do, and I hated micromanaging. But I still had to learn to watch someone do a job differently without correcting every choice they made.

Having experience doesn’t automatically make that easy. Sometimes, experience is exactly what makes it difficult.

You can see a faster way. You know which steps you would take. You know where you would start and what you would avoid.

The person doing the work may not know any of that yet.

You may have 30 years of experience. They may have three.

Some methods are requirements

There are processes that have to be done a certain way. That is why we have standard operating procedures.

On a production line, the sequence matters. A step may protect quality, keep someone safe, or prepare the work for the next person. An employee needs to understand and follow those requirements. A manager needs to explain them.

There is a difference, though, between a required method and a method you prefer.

“Sweep the warehouse” may allow more room for judgment. So might organizing a project or planning the order of several tasks. Some people work left to right. Others work right to left. People choose different driving routes for different reasons.

Your way may work very well. That alone doesn’t establish that everyone needs to use it.

The manager has to know where flexibility exists and make that clear to the employee. Otherwise, the employee is left trying to discover which instructions are requirements and which are preferences that were never explained.

Tell them what finished looks like

Giving people room to work starts with making sure they understand the outcome you expect.

For the warehouse, what needs to be swept? What needs to be clear when they finish? When should the work be completed? Are there areas or activities they need to work around?

You may know all of that so well that you no longer think about it. The employee still needs to know.

Once the expectations and boundaries are clear, you have something useful to evaluate. You can look at the result, the time involved, and whether the requirements were followed.

I had to keep reminding myself: if the work was done properly, within a reasonable amount of time, and I didn’t have to do it, where was the harm?

Sometimes, the only thing bothering me was watching someone take a route I wouldn’t have taken.

That was something I needed to work on.

Understanding comes before improvement

Over time, I learned that some processes are easier to improve once a person already understands how to do them.

It is hard to keep telling someone, “Don’t do it like that,” when they don’t yet understand why they are doing it in the first place.

They are trying to learn the task. You are already trying to make them more efficient at it. Every correction changes something they are still working to understand.

Giving someone reasonable room to work through a process helps them connect the steps with the outcome. They begin to understand what they are doing and why it matters.

Then your advice has somewhere to land.

They can understand why changing the order saves time, why a particular step creates extra work, or why preparing something first makes the rest easier.

You can also begin asking them where they see opportunities to improve. Once they understand the work, they have a better chance of finding those opportunities themselves.

That takes patience. It took me time and wisdom to recognize when that patience was part of my job.

Room to learn has limits

If a three-minute process is taking 27 minutes, you need to pay attention.

Allowing someone to learn their way doesn’t mean ignoring the time, the result, or the requirements. It means having a reason to intervene beyond “That isn’t how I would do it.”

I step in when:

  • I see someone struggling.
  • The work is producing a different result than expected.
  • The task or project is taking longer than expected.
  • They ask for help.

Those are signs that my involvement is needed.

The question then becomes what kind of help will move them forward. Do they understand the outcome? Is a step unclear? Are they missing something they need? Have they reached a point where experience would help them see a better approach?

The purpose of stepping in is to help them succeed and understand the work well enough to do it again.

Before you correct the next person

Think about someone whose way of working frustrates you.

Can you identify the requirement they are missing? Is the result wrong? Is the time unreasonable? Are they struggling?

Or are you watching someone work right to left when you have always worked left to right?

Your experience is valuable. Use it to establish clear expectations, explain the requirements, recognize struggle, and help people improve.

But give them room to build experience of their own.

The next time you feel the urge to say, “Here, let me show you,” pause long enough to ask whether they need your help or you need to let them finish.