PROCESS vs RELATIONSHIP: Two Paths to Handling Workplace Performance Issues

It usually starts the same way.

A team member who was once reliable begins missing deadlines. Emails go unanswered a little longer than they should. The energy dips. Something feels off.

As a senior leader, you’ve seen this before. And in many organisations, the response is almost automatic: document the issue, schedule a formal conversation, begin tracking performance more closely. If it continues, escalate.

Process kicks in.

It’s not wrong. In fact, it exists for good reason—fairness, consistency, protection. But over time, I’ve found that the instinct to reach for process first can quietly make things worse.

Because once you move into process mode, something shifts. The focus changes. The relationship changes. And often, the outcome changes too.

The question worth asking is this: what if the way we start handling performance issues is what determines how complex they become?

A while ago, I watched a situation unfold that captured this perfectly.

Let’s call the employee Aarav.

Aarav had been a strong performer—steady, reliable, well-liked. Then, gradually, things started to slip. Deadlines were missed. Contributions in meetings became quieter. Nothing dramatic, just enough to be noticed.

The manager did what many would consider best practice. They began noting the missed deadlines. They reviewed expectations. Eventually, they scheduled a more formal conversation, referencing performance standards.

By the time Aarav walked into that meeting, the tone had already been set.

The conversation focused on gaps—what hadn’t been delivered, what needed to change, what would happen if it didn’t. A performance plan followed shortly after.

From the organisation’s perspective, this was structured, consistent, and fair.

From Aarav’s perspective, it felt very different.

The energy shifted from improvement to defence. Explaining the past became more important than shaping the future. Trust, once quietly present, became something more fragile.

And the issue, which started small, became formal—and harder to resolve.

Now, imagine the same situation handled differently.

Instead of documenting first, the manager starts with a conversation.

Not a scripted one. Not a formal one. Just a simple, private check-in:

“I’ve noticed a few deadlines slipping recently. That’s not like you—what’s been happening?”

It’s a small shift, but an important one.

The conversation doesn’t begin with judgement. It begins with curiosity.

And often, what emerges in those moments changes everything.

Maybe Aarav is carrying more workload than anyone realised. Maybe priorities have become unclear. Maybe something outside of work is affecting focus. Or perhaps there’s a capability gap that hasn’t been surfaced.

Once that context is visible, the path forward becomes clearer—and shared.

Together, they adjust priorities. Add support. Schedule regular check-ins. Rebuild clarity.

Nothing formal. Nothing escalated.

Just addressed.

In many cases, that’s enough. The issue stabilises before it ever becomes something larger.

And if it doesn’t—if performance doesn’t improve—something else has been built instead: a foundation of fairness, support, and good faith. A very different starting point for any next step.

This is the difference between a process-led response and a relationship-led response.

The process approach is built on structure. It values consistency, documentation, and defensibility. These are essential things—particularly when decisions carry legal or organisational risk.

But when applied too early, process has a tendency to pull focus toward compliance rather than resolution. It can turn a performance issue into a case to be managed, rather than a problem to be understood.

The relationship approach starts somewhere else.

It starts with the belief that performance is not just an output issue—it’s a reflection of clarity, context, capability, and connection. It assumes that most problems are not fixed through control, but through understanding.

Importantly, this isn’t about being “softer” on performance.

It’s about being more effective.

Because when trust is high, feedback lands differently. People engage with it rather than resist it. They take ownership rather than deflect it. The same message can lead to completely different outcomes depending on the strength of the relationship it sits within.

There’s also a very practical reality here for leaders.

Most performance issues don’t begin as serious problems. They begin as small, manageable gaps—unclear expectations, competing priorities, capability stretches, or simply a bad week that turns into a bad month.

Handled early, these are easy to correct.

Handled late—once formalised—they become significantly more expensive.

Not just financially, but in time, attention, and team energy. Managers find themselves drawn into lengthy processes. Teams feel the disruption. Often, good people leave—sometimes unnecessarily.

Every organisation knows the visible costs of poor performance. Fewer track the hidden cost of how performance is managed.

The research in this space reinforces what many leaders have experienced intuitively.

People are far more likely to accept feedback—and act on it—when it comes from someone they trust. High-quality manager–employee relationships consistently predict stronger performance outcomes than purely transactional systems.

Put simply: relationships aren’t a “soft” factor sitting alongside performance. They are one of the most powerful drivers of it.

For senior leaders, the implication is not to replace process.

It is to rethink its role.

Process matters. It creates fairness, consistency, and protection. But it works best as a backstop, not a starting point.

The most effective leaders I’ve seen do three things consistently:

  • They invest early in relationships—so that when performance conversations happen, they land constructively.
  • They intervene sooner—when issues are still fluid and fixable.
  • And when process is needed, they use it with precision—built on a foundation of prior support and clarity.

In the end, this isn’t really a choice between process and relationship.

It’s a choice about sequence.

Lead with process, and you often get compliance, defensiveness, and escalation.

Lead with relationship, and you give performance the best chance to recover early and sustainably.

The next time something feels off with a member of your team, there’s a moment of choice.

You can reach for the documentation.

Or you can start with a conversation.

One builds a case. The other builds understanding.

And more often than not, it’s understanding that leads to better performance.

Reach out to The Workplace Coach today and explore how coaching can elevate your leadership style and help you be even more effective in your role.

Buy the Workplace Coach a coffee Large Nitro Coffee please

Leave a comment