top of page
Search

How To Manage Underperformance Early Without Rushing Into A Capability Process


If you’ve read our recent article on why avoiding underperformance conversations is not kindness, you’ll know our view already: saying nothing doesn’t help. It usually makes the issue harder, more awkward, and more serious than it needed to be.


But once you have accepted that the conversation needs to happen, the next question is usually the harder one.


What do you actually do?


A lot of managers can get lost. They know something is off, that the standard is not where it needs to be. But they are trying to work out whether this calls for a quiet word, more clear expectations and more support, firmer management, or a formal process.

Usually, the answer they come to is not “go formal”... yet. 


Managing underperformance early takes a few sensible steps in the right order. 1. Not ignoring it. 2. Not dramatising it. 3. Just dealing with it properly while it is still manageable.


Start With The Facts, Not Your Frustration


Before you do anything, get clear on what the actual issue is.

A lot of managers jump into these situations with a general feeling that someone is underperforming, but that is too vague to be useful. If you cannot explain clearly what is not working, the employee has no real chance of improving it.


So start by asking yourself:

  • What exactly is slipping?

  • Has quality dropped?

  • Are deadlines being missed?

  • Is work taking too much correction?

  • Is follow-through inconsistent?

  • Is this a one-off wobble or a pattern?


You are not building a case against the employee. You’re attempting to be specific enough to be fair.


Don’t say this: “You’re not pulling your weight.”
Instead, try this: “The last three reports you’ve shared have all needed significant rework, and two deadlines were missed without warning.”

That difference matters. 


Check Whether The Standard Was Ever Clear


Before you treat this as a capability issue, be honest about whether expectations were clear in the first place.


Sometimes poor performance is poor performance. But many times…

  • It’s a badly managed handover.

  • It’s weak onboarding.

  • It’s a role that has grown faster than the person in it.

  • It’s a manager assuming things have been understood when they have never actually been said out loud.


This is where leaders need to pause and ask a better set of questions, ideally grounded in evidence:

  • Did we make the standard clear?

  • Did we explain what good looks like?

  • Did we give useful feedback early enough?

  • Did this person have the right support, training, and context?

Don’t say this: “You should just know.”
Instead, try this: “Before we go further, I want to make sure we’ve properly explained what good looks like in this role.”

Remember, you’re making sure that you are solving the right problem.


Have The Conversation Early, Not Perfectly


One of the biggest reasons performance issues drift is because managers wait until they know exactly what to say. But sometimes that moment doesn’t come. 

Let us reassure you that you do not need a flawless script, but you do need to stop waiting.

A good early conversation should be clear, calm, direct, and human. This isn’t a disciplinary meeting. It’s you sounding like a manager doing their job.


You’re aiming to explain:

  • What you have noticed

  • Why it matters

  • What needs to change

  • What support is available

  • When you will review progress


Don’t say this: “I just wanted to have a little catch-up because there have been a few concerns.”
Instead, try this: “I wanted to check in because a few things haven’t been landing as they should, and it felt important to talk about that early.”

Kind, clear, and impossible to misunderstand.


Don’t Confuse Support With Avoidance


This is where lots of businesses get tangled up. They want to be supportive, which is good. But instead of offering support, they offer vagueness, endless patience, or repeated second chances with no real clarity attached. 

Support should help someone improve. Avoidance delays the moment of truth.

Depending on the issue, support might look like:

  • Clearer priorities

  • Weekly check-ins

  • Extra training

  • A tighter review period

  • More direct feedback

  • Better boundaries around the role

Don’t say this: “Let’s just give it another month and see.”
Instead, try this: “Let’s be clear on what needs to improve over the next few weeks, and how I can support you to get there.”

That is what practical performance improvement looks like.


Write Things Down Without Making A Big Deal


Documentation scares people because they think it instantly makes the situation formal.

It doesn’t.


Writing down what was discussed, what improvement is needed, and when it will be reviewed is good management. It protects both sides. It creates a clear path forward. And if the issue does continue, it means the next step is not based on memory or emotion.


Don’t do this: A conversation that feels clear in the moment, then gets remembered differently by everyone a week later.
Instead, try this: A short written summary so everyone is clear on what was discussed, what needs to change, and what happens next.

You’re not being formal for the sake of it. This is just fairer for everyone.


Watch For The Wider Team Impact


Employee performance issues are rarely felt by just one person. We talk more about that in Why Avoiding Underperformance Conversations Is Not Kindness, especially how quickly the wider team starts to feel it.


When underperformance happens, the wider team usually feels it first. Work gets redistributed. Standards wobble. Frustration builds. Stronger performers end up carrying more than they should.


This matters because good management is not just about being fair to the individual. It is also about being fair to everyone else, especially when the wider team has started to feel the impact and is looking to you for reassurance. 

If the team comes to you with questions…


Don’t say this: “Leave it with me.”
Instead, say this: “I know this has had an impact on the team, and I want you to know it is being addressed. Whilst I can’t share every detail, I do want to be clear that it is not being ignored.”

For SMEs and charities, this matters a lot. There is usually less slack in the system, which means one unresolved issue can affect morale, delivery, and leadership time very quickly.


Know When It Is Time To Go Formal


Early action is not the same as formal action. But there does come a point where a more formal capability process may be the right next step.


Usually, that point comes when:

  • The concerns have been raised clearly

  • The expectations have been made clear

  • Support has been offered

  • A fair/agreed amount of time has passed

  • The required improvement still has not happened


At that stage, it may be appropriate to move from informal performance management into a more formal capability route.


Don’t say this: Especially after another incident… “Right, I think we need to make this formal.”
Instead, do/say this: Be clear that this is the next step, not the first one. “We’ve talked this through, we’ve been clear about what needs to change, and support has been put in place. As the improvement hasn’t been where it needs to be, we now need to move this into a more formal process.”


That distinction matters. A capability process should never feel like it has come out of nowhere. It should feel like the next fair step after earlier, sensible management action has not worked.


The Aim Is To Deal With Underperformance Before It Gets Heavier


Managing poor performance early is noticing the issue, understanding it properly, and dealing with it early enough, so that it does not grow into something bigger than it needs to be.


  • Be specific.

  • Be honest.

  • Be fair.

  • Be clear.


Stop hiding behind silence or process.


If you are dealing with a performance issue and you are not sure whether it needs a clear conversation, more structure, or a formal capability process, Cape Consulting helps SMEs and charities work that through without adding unnecessary drama.

 
 
 

Comments


bottom of page