By the time Liza entered the meeting room, everyone already knew what the conversation was about.

Mark was becoming a problem.

He had missed another deadline. His reports contained errors. He asked questions that other employees seemed able to answer on their own. When the team became busy, someone usually had to check his work or finish what he had started.

His supervisor, Dennis, had reached the end of his patience.

“I have explained the process many times,” Dennis said. “He has been here for almost a year. At this point, I think it is an attitude problem.”

Liza opened the folder in front of her. She was the HR manager, but she had learned not to begin with policies or forms when the problem was still unclear.

“What happened with the latest report?” she asked.

Dennis leaned forward.

“I told him to prepare the weekly operations report. He sent it late, and the numbers did not match Finance.”

“What did you tell him to include?”

“The usual numbers.”

“Is there a checklist?”

“He should know the usual numbers by now.”

“Where did he get the data?”

“From the team trackers.”

“Are the trackers complete?”

Dennis paused.

“Not always. That is why he has to follow up.”

“Did he know which numbers Finance would use?”

Another pause.

“I assume so.”

The conversation had begun with a difficult employee.

Five minutes later, the work itself was beginning to look difficult.

A Person Can Become the Name of the Problem

Workplace problems become easier to discuss when we attach them to a person.

Mark is careless.

Ana is slow.

Joel lacks initiative.

Mina is difficult.

Once we give the problem a name, the situation feels clearer. We know who must improve. We know who needs coaching, correction, or discipline. We can stop examining the work because we have already located the cause.

The person becomes the problem.

Sometimes the diagnosis is accurate. Employees can be careless, dishonest, disrespectful, unwilling to learn, or repeatedly irresponsible. Supervisors must not hide poor behavior behind endless explanations.

But labels can arrive before understanding.

An employee may look slow because the process requires six approvals.

Someone may appear careless because the standard changes depending on who reviews the work.

A person may seem unmotivated because every attempt to make a decision is reversed.

An employee may keep asking questions because the instructions are vague, the files are incomplete, and mistakes are punished more harshly than silence.

Before deciding that the employee is the problem, the supervisor must examine the work the person has been asked to perform.

The Work Was Called “Routine”

The weekly operations report had existed for years.

Every Friday, someone gathered information from the team trackers, compared actual output with the weekly target, identified delays, and sent the report to Finance and Operations.

Dennis considered it routine.

Mark did not.

When Mark took over the report, no one walked him through the full process. A former employee sent him an old template and said, “You’ll get used to it.”

The template contained several columns that were no longer used. Two teams submitted data using different labels. Finance used a different closing time from Operations. Some supervisors updated their trackers before lunch. Others waited until the end of the shift.

Mark gathered the numbers and tried to make them match.

When they did not, he asked questions.

Dennis heard the questions as evidence that Mark still did not understand the job.

Mark experienced the work as a puzzle whose rules changed every week.

The task was routine only to people who had already learned how to survive its confusion.

Familiar Work Can Hide Invisible Knowledge

Experienced employees often carry knowledge they no longer notice.

They know which report is usually late. They know which manager wants to see more detail. They know that one number must be checked with Finance even when the tracker looks complete. They know whom to call when the data does not match.

None of this may appear in the official process.

The work is completed through memory, relationships, workarounds, and unwritten judgment.

Then a new person enters.

The organization gives the employee the form but not the map. The employee makes mistakes. Experienced people conclude that the new person lacks common sense.

What they call common sense may actually be hidden experience.

A supervisor must ask:

What does a capable employee know that has never been made visible?

That question often reveals why one person appears to struggle with work everyone else calls simple.

Example 1: The Employee Who Was “Too Slow”

A customer service employee took almost twice as long as her teammates to complete each case.

Her supervisor believed she lacked urgency.

The employee checked every detail before sending a response. She opened several systems, copied information into a tracker, asked another department to confirm the account, and waited for approval before closing the case.

Her teammates appeared faster because they had learned which steps could be skipped safely. Some kept personal notes. Others knew which approver answered quickly. A few closed cases before all the information was recorded and updated the tracker later.

The official process looked the same for everyone.

The actual process was different.

Before telling the employee to work faster, the supervisor needed to examine:

• Which steps were truly required?
• Which steps added no value?
• Which shortcuts were safe?
• Which shortcuts created hidden risk?
• What knowledge did experienced employees use?
• Could the process be simplified for everyone?

The employee may still have needed to improve her speed.

But speed was not the only problem.

The work had never been designed clearly.

Check the Work Before Checking the Attitude

Attitude is a serious concern because it affects how a person responds to responsibility, feedback, difficulty, and other people.

It is also difficult to diagnose accurately.

A supervisor sees an employee become quiet during correction and calls the person defensive. The employee may be trying not to cry.

A worker stops suggesting improvements and is described as disengaged. The last three suggestions may have been ignored.

An employee waits for instructions and appears passive. Earlier attempts to act independently may have been criticized.

A person asks many questions and seems dependent. The supervisor may be changing expectations without noticing.

None of these possibilities automatically excuses the employee.

They remind us to separate observation from interpretation.

Observation sounds like this:

Mark submitted three reports after the agreed deadline.

Interpretation sounds like this:

Mark does not care about the work.

The first statement gives us something to investigate.

The second closes the investigation before it begins.

A Useful Diagnosis Has Several Doors

When performance is weak, supervisors often walk through one door: the person.

A stronger diagnosis checks several possible sources.

Clarity

Did the employee understand the expected result?

Was the standard visible?

Were priorities, ownership, deadlines, and decision boundaries clear?

Capability

Does the employee know how to complete the work?

Has the person practised enough?

Is this a knowledge gap, a skill gap, or a judgment gap?

Capacity

Does the employee have enough time, attention, and energy to complete the work?

Is the workload realistic?

Are several urgent demands competing?

Tools and information

Does the person have access to accurate data, working equipment, usable templates, and the information needed to decide?

Process and system

Does the workflow help the employee succeed, or does it create delay, rework, and confusion?

Are approvals, handoffs, and responsibilities clear?

Support

Did the supervisor provide the right amount of guidance?

Was feedback given early enough to improve the work?

Accountability

After the other conditions were reasonably addressed, did the employee accept responsibility and follow through?

These doors are not excuses.

They are parts of the diagnosis.

Accountability becomes stronger when it is attached to the real problem.

Example 2: The “Careless” Warehouse Employee

A warehouse employee repeatedly placed items in the wrong storage locations.

The supervisor corrected him several times.

“Read the labels carefully,” she said.

The mistakes continued.

She began documenting the employee’s carelessness.

During a physical inspection, someone noticed that several labels were faded. Two shelves carried almost identical item codes. New inventory had been placed in temporary spaces because the assigned area was full. The digital record had not been updated.

The employee had made errors.

But the workplace had made correct action unnecessarily difficult.

The solution required more than another warning.

The team replaced damaged labels, separated similar codes, updated the location map, and created a temporary-storage procedure.

After those changes, the errors dropped.

This did not prove that employees should never be corrected. It showed that correction alone could not repair work that invited mistakes.

Example 3: The Employee Who “Lacked Initiative”

Carla’s manager complained that she brought every decision to him.

“Even small things,” he said. “She needs to learn to think.”

Carla had tried to decide independently during her first month. She approved a customer request that seemed reasonable. Her manager reversed the decision in front of the team.

The next week, she adjusted a schedule to prevent a delay. Her manager asked why she had acted without permission.

She learned quickly.

Initiative was expected when the decision worked.

Permission was expected when it did not.

No one had explained which decisions belonged to her.

So she chose the safest path.

She asked.

The manager saw dependency.

Carla saw self-protection.

A supervisor who wants initiative must make the decision space visible.

What can the employee decide alone?

What conditions require consultation?

What limits must not be crossed?

When should the person act first and report afterward?

Without these boundaries, “show initiative” means “guess which decisions I will support.”

Some Problems Begin Before the Employee Touches the Work

A failed output can be created long before the person begins.

The priority may have been changed without notice. The input may be incomplete. The target may conflict with another target. The employee may depend on someone who has no reason to respond quickly.

The person at the end of the process becomes visible because that is where the failure appears.

But visibility is not the same as cause.

Consider a delayed customer order.

The customer service employee may be blamed because she speaks to the customer. But the delay may have begun when Sales promised an unrealistic date, inventory records showed stock that did not exist, and Finance held the account for approval.

The employee may still handle the customer poorly. That behavior should be addressed.

But coaching the employee to sound more positive will not fix the order system.

Supervisors must learn to see the whole path of the work.

Where did the problem begin?

Where did it become visible?

Those may be two different places.

Example 4: The Salesperson Who “Did Not Follow Up”

A salesperson lost an account after failing to send a quotation on time.

The manager concluded that she lacked follow-through.

During the review, they discovered that the quotation required technical specifications from Engineering, updated prices from Procurement, and final approval from Finance.

The salesperson had followed up with all three groups.

Engineering replied late. Procurement sent an old price list. Finance returned the quotation because one item did not match the approved margin.

The salesperson could have communicated better with the client. She could have escalated sooner. Those were valid performance issues.

But she was not the only owner of the delay.

Calling her careless would have protected a weak handoff system.

A better response was to improve both the person and the process:

• clarify escalation points;
• assign response times;
• use one current price source;
• make approval ownership visible;
• and coach the salesperson to update the customer before the promised date passes.

Accountability does not require choosing between the employee and the system.

Both can improve.

The Wrong Tool Can Make a Good Employee Look Weak

Some employees spend hours working around tools that leaders assume are helping.

A slow computer turns a five-minute task into twenty minutes.

A tracker requires the same information to be entered three times.

A reporting template asks for data no one uses.

A machine stops often, but the operator is measured only by output.

A supervisor sees poor results and asks the employee to work harder.

The employee may already be compensating for the system.

This is why supervisors must go where the work happens.

Do not diagnose everything from a dashboard.

Watch the task.

Ask the employee to show the process.

Notice where the person waits, repeats, checks, searches, repairs, or asks for approval.

The truth about work often appears between the official steps.

Capability Problems Need Practice, Not Shame

Sometimes the work is clear, the process is reasonable, and the tools are available.

The employee still cannot perform.

This is a capability problem.

The person may understand what is expected but lack the knowledge, skill, judgment, or experience to produce it consistently.

Supervisors sometimes treat capability gaps as attitude problems because they are tired of explaining.

“He should know this by now.”

Perhaps he should.

But the useful question remains:

What exactly can the person not yet do?

“Improve your communication” is too broad.

“Summarize the customer’s concern before offering a solution” is teachable.

“Be more careful” is too vague.

“Check the item code, quantity, and delivery date before submitting the order” is observable.

“Use better judgment” gives little help.

“Escalate when the customer asks for a discount above ten percent” creates a boundary.

Capability grows through specific practice.

Shame usually teaches concealment.

Example 5: The Employee Who Kept Making the Same Error

A payroll employee repeatedly entered the wrong effective date for salary changes.

Her supervisor had corrected her three times.

On the fourth error, the supervisor said, “You are not paying attention.”

During a closer review, the employee explained that three dates appeared on the approval form:

• the date the request was submitted;
• the date the manager approved it;
• and the date the salary adjustment should begin.

She believed the approval date was the effective date because the form did not label the fields clearly.

The supervisor had learned the distinction years earlier and no longer noticed that it could be confusing.

They revised the form, added a quick check, and asked the employee to process three sample cases.

The error stopped.

The person did not suddenly become more careful.

The work became easier to understand, and the correct behavior was practised.

Capacity Is Not the Same as Commitment

A committed employee can still have too much work.

Supervisors sometimes respond to overload by teaching time management. That can help when the employee is disorganized, easily distracted, or unable to prioritize.

But a perfect schedule cannot fit fourteen hours of work into eight.

When employees repeatedly miss deadlines, examine the load.

How many tasks are active?

Which deadlines compete?

How often is the employee interrupted?

How much rework occurs?

Which tasks require deep attention?

What was added without anything being removed?

A person may need stronger prioritization.

The team may also need fewer priorities.

Example 6: The “Disorganized” Administrative Assistant

An administrative assistant supported three managers.

Each manager considered their request urgent. One communicated by email, another through chat, and the third often stopped by her desk. Meetings were moved frequently. Travel requests arrived late. Documents required several revisions because instructions changed.

The assistant missed appointments and forgot follow-ups.

Her managers agreed that she needed to become more organized.

She did.

She built a detailed tracker.

The requests still exceeded the available time.

The real improvement began when the managers created one request channel, assigned priority rules, agreed on lead times, and met briefly every Monday to settle conflicts.

The assistant’s personal system mattered.

So did the management system around her.

Not Every Explanation Is an Excuse

Supervisors sometimes avoid deeper diagnosis because they fear becoming too soft.

“If we keep asking why, people will always have a reason.”

That fear is understandable.

People can use explanations to avoid responsibility. A person may blame the process after ignoring clear instructions. An employee may cite workload while spending hours on low-value activity. Someone may claim confusion after failing to ask a question that was clearly needed.

A strong supervisor listens without surrendering judgment.

The purpose of asking why is not to make the problem disappear.

The purpose is to identify the right response.

If the work was unclear, create clarity.

If the skill was missing, build capability.

If the system created the error, improve the system.

If the workload was unrealistic, reset priorities.

If the employee understood, had the ability, had the resources, and still chose not to act, address accountability directly.

Good diagnosis does not weaken standards.

It prevents us from applying the wrong solution.

Separate “Can’t” from “Won’t”

One of the supervisor’s hardest tasks is deciding whether the employee cannot perform or will not perform.

The difference is not always obvious.

A person who cannot may look resistant because repeated failure has made the employee defensive.

A person who will not may pretend to be confused because confusion feels safer than refusal.

Supervisors need evidence.

Ask the employee to demonstrate the task.

Observe what happens without taking over.

Clarify the standard.

Provide reasonable support.

Agree on a clear next action and deadline.

Then follow through.

Patterns become easier to see over time.

A person who cannot often improves with specific guidance and practice.

A person who will not may continue avoiding responsibility even after the path becomes clear.

Do not decide from one bad day.

Do not ignore a repeated pattern either.

The Performance Conversation Must Name the Whole Truth

After Liza and Dennis examined the weekly report, they met with Mark.

Dennis did not begin with, “You have an attitude problem.”

He began with the facts.

“The last three reports were submitted after the deadline. Two contained numbers that did not match Finance. This delayed the operations review.”

Mark explained the difficulties with the trackers and the different closing times.

Dennis listened.

Then he said, “Those problems are real. We also need to talk about what you did when the numbers did not match. You waited until Friday afternoon before escalating.”

The conversation became more accurate.

The process was weak.

Mark’s response was also weak.

They agreed on several changes.

The team trackers would use the same labels and closing time. Mark would receive a current checklist. He would send an early comparison on Thursday and escalate missing data before noon.

The final report would still be his responsibility.

Mark was not declared innocent.

He was given work he could reasonably own.

That is what fair accountability looks like.

Check the Work in the Right Order

When performance fails, use this sequence.

See the result

What happened?

Use facts, dates, outputs, errors, delays, and observable behavior.

Trace the work

Where did the task begin?

What inputs, handoffs, approvals, tools, and decisions shaped the result?

Check clarity

Did the employee know the outcome, standard, priority, boundary, and deadline?

Check capability

Could the person perform the task at the required level?

What specific move was missing?

Check capacity and resources

Did the person have enough time, information, access, and support?

Check behavior

What did the employee do after difficulty appeared?

Did the person ask, hide, delay, escalate, solve, or avoid?

Set the next move

What must change in the work?

What must change in the employee’s behavior?

Who owns each action, and when will you review it?

This prevents the supervisor from jumping from weak results directly to blame.

Supervisory Training Must Teach Diagnosis

Many supervisory programs teach leaders how to correct employees.

That is necessary.

But correction becomes dangerous when the supervisor has diagnosed the wrong problem.

A supervisor may discipline someone for failing to follow an unclear process. The employee becomes resentful, and the process remains broken.

Another supervisor may keep coaching a person who fully understands the work but repeatedly refuses to meet the standard. The employee learns that every missed commitment produces another gentle conversation.

Supervisors need judgment.

They need to distinguish clarity problems from capability problems, system problems from behavior problems, and explanations from excuses.

Effective supervisory training must help supervisors examine real workplace situations, choose the right response, and return with proof that the work and behavior improved.

The goal is not to make supervisors softer.

The goal is to make them more accurate.

The Label Can Wait

Mark’s next weekly report was submitted on time.

The numbers matched Finance.

The new checklist helped. The common closing time reduced confusion. The Thursday checkpoint exposed missing data before the deadline.

Mark also changed.

When one team failed to update its tracker, he escalated before noon instead of waiting. He documented the missing input and followed up with the owner.

The improvement did not prove that every earlier mistake belonged to the system.

It proved that the old label had been too small for the whole problem.

Mark had needed better work.

He had also needed to respond to that work with greater ownership.

Both things could be true.

That is what supervisors must learn to hold.

People work inside systems, but they still make choices.

Systems shape behavior, but they do not remove responsibility.

Standards matter, but standards become fairer when the path to meeting them is clear.

So before you call someone a problem employee, check the work.

Look at the instructions, tools, process, load, handoffs, practice, and support. Find where the difficulty begins. Then look clearly at what the employee does with the conditions provided.

You may discover a person who needs correction.

You may discover a process that needs repair.

Often, you will discover both.

That is not a weaker conclusion.

It is a more useful place to lead.