The Case Was Closed. The Pattern Wasn’t.

When organizations treat every people problem as an isolated event, they can become very efficient at managing consequences—and never address what keeps producing them.

The investigation is complete.

The corrective action is issued.

The resignation is processed.

The position is reposted.

The file is updated.

Case closed.

Then, six weeks later, something familiar lands on someone’s desk.

A different employee. Same manager.

A different complaint. Same underlying concern.

Another resignation from the same team.

Another employee struggling with the same unclear expectation.

Another hiring process stalling at exactly the same point.

Another corrective action addressing behavior we've addressed before.

At some point, leadership has to stop asking only:

What happened this time?

And start asking:

Why does this keep happening?

Because the case may be closed.

The pattern isn’t.

When good case management isn't enough

There is real value in handling individual employee matters well.

Investigations should be thorough. Documentation should be timely. Complaints should be addressed. Performance concerns should not linger indefinitely. Departures need to be processed. Vacancies need to be filled.

That work matters.

But an organization can do all of it correctly and still miss something important.

The case can be resolved without the organization having learning from it.

People issues rarely arrive labeled:

This is the fourth symptom of the same organizational problem.

They arrive separately.

A complaint here. Turnover there. A performance issue somewhere else. A difficult manager conversation. An exit interview. A failed hire. A conflict.

Each has its own facts, people, confidentiality considerations, urgency, and required response.

So we handle them individually.

And sometimes we should.

The problem begins when we handle each issue separately and never step back to see what they may be telling us together.

Every case has an owner.
But who owns the pattern?

Repetition should change the question.

One employee struggling to meet an expectation may be an individual performance issue.

Five employees struggling with the same expectation should make us curious about the expectation.

One resignation may tell us very little.

Repeated resignations from the same team should make us curious about the team.

One complaint about a manager requires us to understand that complaint.

Multiple employees independently describing similar experiences should make us curious about the leadership environment.

One hiring process that goes sideways happens.

A role that repeatedly turns over, remains vacant, or produces unsuccessful hires should make us curious about more than the candidates.

None of this means repetition automatically proves a systemic problem.

It means repetition earns a wider diagnosis.

Pattern recognition is not conclusion-making.

It is knowing when the evidence is telling you to look again—and look wider.

This is where the PLS Framework™ matters.

When something goes wrong at work, the easiest explanation is often the person closest to the problem.

The employee isn't performing.

The manager isn't managing.

The candidate wasn't right.

The team is difficult.

Sometimes that diagnosis is correct.

Sometimes it is incomplete.

The Person–Leader–System Framework™ (PLS Framework™) widens the diagnosis before we decide what to do about the problem.

• PERSON — What belongs to the individual?
  Look at what the person understood, what the expectation was, what choices they made, and what accountability appropriately belongs to them.

• LEADER — What did leadership shape?
  Look at what was communicated, reinforced, tolerated, prioritized, supported, or left unaddressed. Leadership often determines whether an individual problem is corrected—or repeated.

• SYSTEM — What conditions made the outcome more likely?
  Look beyond the immediate people involved. Look to workload, incentives, processes, resources, policies, structures, competing priorities, and other conditions that may keep reproducing the same result.

The point isn't to move accountability away from the person.

It's to put accountability where it actually belongs.

• If we diagnose a leadership problem as a person problem, we may replace the employee and recreate the outcome.

• If we diagnose a system problem as a leadership problem, we may coach the manager without changing the conditions they are managing inside.

• And if the issue truly is individual accountability, a wider diagnosis should make that clearer—not obscure it.

The wrong diagnosis creates the wrong intervention.

The Pattern Test

When a people matter occurs — or closes — five questions can help determine whether you're looking at an isolated event—or something that deserves a wider diagnosis.

1. Have we seen this before?

Don't look only for identical incidents. Look for the underlying issue.

Confusion. Turnover. Conflict. Missed expectations. Manager behavior. Burnout. Communication breakdowns. Repeated escalation.

What feels familiar?

2. Where is it concentrated?

Look across managers, teams, departments, roles, locations, employment stages, processes, and time periods.

A pattern that disappears at the organizational level may become obvious when the information is segmented.

3. What conditions keep appearing?

What conditions tend to be present when this happens?

Unclear decision-making authority? Inconsistent leadership? Too much work and too little capacity? An onboarding process that leaves people guessing? Competing priorities? Communication gaps? Incentives that encourage the wrong behavior? A process people routinely have to work around just to get the job done?

Conditions matter.

4. What response have we repeated?

This one can be uncomfortable.

Another coaching conversation. Another training. Another write-up. Another termination. Another replacement hire. Another reminder email. Another policy.

If the organization's response is as repetitive as the problem, that is information too.

5. Has the response changed the outcome?

This may be the most important question.

If we keep applying the same intervention and the same problem keeps returning, we should be willing to reconsider the diagnosis.

A recurring problem with a recurring solution and a recurring outcome is a pattern.

And patterns deserve executive attention.

Confidentiality should protect people—not create institutional amnesia.

Pattern recognition does not mean casually combining confidential employee matters or making assumptions based on incomplete information. Individual cases still require appropriate privacy, evidence, due process, and context.

And correlation is not causation.

But senior leaders do need to know when one department is experiencing disproportionate turnover, multiple employees independently describe similar management behavior, a policy repeatedly creates the same confusion, corrective action increases without improving the underlying outcome, or the People team repeatedly manages consequences it does not have the authority to prevent.

Leadership needs to know that.

Not so leaders can reach conclusions about individual cases. So they can recognize when the organization itself may need examination.

The job isn't only to close cases. It's to learn from them.

A capable People (HR) function can manage individual employee matters well.

A strategic People (HR) function must also ask:

What are these matters telling us together that we cannot see when we examine them separately?

That requires good records, visibility across time, and leaders willing to examine patterns that may implicate their own teams, decisions, structures, or priorities.

Because sometimes the person is the problem.

Sometimes the leader is the problem.

Sometimes the system is the problem.

And sometimes all three are contributing in different ways.

The goal isn't to choose the most convenient explanation.

The goal is to diagnose accurately enough to know what to do next.

Every case may have an owner.

Someone or something still has to own the pattern.

A question worth carrying into your next leadership meeting:

• What problem has your organization become very efficient at processing—but not at preventing?

If an answer came to mind quickly, that's worth examining.

Recurring people problems don't always need another isolated intervention. Sometimes leadership needs enough distance to examine what is happening across the Person, Leader, and System and determine what is actually producing the outcome.

That's the work I help executive teams do.

REQUEST A CONFIDENTIAL FIT CONVERSATION →

Stay Connected

If this perspective challenged your thinking or gave you a new way to diagnose an issue, I'd love to continue the conversation. You can also:

• Follow me on LinkedIn for executive insights on leadership, organizational culture, and people strategy.

• Explore more Perspectives to deepen your thinking and inspire your leadership.

• Explore more ways we can work together.

• Learn more about The Third Perspective™ and the PLS Framework™.

Kimberly D. Sanders
Executive Strategist • Creator of the PLS Framework™ and The Third Perspective™ • Diagnosing before prescribing.