
In a company with a real HR department, an underperformance conversation is a process. There is a policy, a template, someone in the room who has done this a hundred times. In most Nigerian SMEs and startups, there is you. You are the founder, the line manager, the payroll officer and the HR function, all in one Monday morning. And the person whose work has been slipping for three weeks sits across from you, waiting.
The temptation is to avoid it entirely, or to explode in a way you regret. Both are expensive. Avoidance lets one weak link quietly reset the standard for everyone else; the blow-up costs you the person and, often, a claim at the National Industrial Court. There is a third way, and it is learnable. This guide gives you the preparation, the structure, and the exact words.
A performance conversation is not a verdict you deliver. It is a problem you and the employee are, at least at the start, trying to solve together.
Before you say a word: prepare on specifics, not vibes
The single biggest mistake untrained managers make is walking in with a feeling instead of a file. "You have not been serious lately" is not feedback. It is an accusation the person can, and will, argue with. "On the 3rd, 9th and 14th, the client report went out after the noon deadline" is a fact. Facts end debates before they start.
So before the meeting, write things down. You do not need an HR system for this: a dated note, a WhatsApp timestamp, an email you can point to. For each concern, capture three things: what happened, when, and what the consequence was. Documentation is what separates a defensible conversation from a personal one, and it matters more when you are the only record-keeper in the building.
Separate the pattern from the incident. One late report is a bad day. Three in two weeks is a pattern. Name the pattern, use the incidents as evidence.
Check your own house first. Was the target ever stated clearly? Did the person have the tools, the login, the brief? Sometimes what looks like defiance is a broken system. Our piece on why good employees break workplace rules is worth reading before you assume bad faith.
If this is a scheduled review rather than a flare-up, the groundwork in our guide to preparing for a performance review in Nigeria will save you an hour.
The model that keeps you out of trouble: SBI
You need a structure so that, under pressure, you describe rather than attack. The most durable one is SBI: Situation, Behaviour, Impact, developed by the Center for Creative Leadership. You name three things in order:
Situation — the specific time and place. "In yesterday's 10am client call..."
Behaviour — the actual, observable action, facts only. "...you interrupted the client twice while she was explaining the scope."
Impact — the effect it had. "...and afterwards she messaged me to ask whether we were still interested in the account."
The power of SBI is what it forces you to leave out. "You interrupted the client" is a behaviour. "You are rude and don't respect people" is a character verdict, and feedback aimed at the person rather than the behaviour puts people on the defensive and rarely changes anything. You cannot fix a personality in a meeting. You can absolutely ask someone to stop interrupting. Extend it to SBII by adding an inquiry into intent: after the impact, ask "What was going on for you there?" This turns a monologue into a conversation and often surfaces the real cause.
The conversation, step by step
Have it in private, face to face, never over a group chat and never in front of the team. Give it a real slot, not a corridor ambush.
1. Open plainly, without the sandwich
Skip the fake-compliment sandwich; people see it coming and stop trusting your praise. State the purpose in one calm sentence.
"Thanks for sitting down. I want to talk about the client reports this month, because I have noticed a pattern I am concerned about, and I want to understand it and fix it with you."
2. Deliver the SBI, then stop talking
"On the 3rd, the 9th and the 14th, the report went to the client after the noon deadline, once by almost three hours. The impact is that two of those clients emailed me directly to chase, and it makes us look disorganised. What is happening from your side?"
Then be quiet. Let the silence sit. This is where you learn whether you have a capability problem, a workload problem, or a will problem.
3. Listen, and reflect back what you hear
If they say the data comes late from another team, that is real and you note it. If they go defensive, do not match it; restate the facts. The skill of holding steady while staying warm is the same one covered in our first one-on-one guide for new managers.
4. Agree the standard and the next step
End with a specific, shared expectation and a date. "From Monday, reports go out by 11:45 so there is buffer. If the upstream data is late, message me by 10 so I can chase it. Let us review this on Friday the 31st."
The scripts
Underperformance script
"Emeka, I asked for this time because I am worried about something and I would rather talk than let it slide. Over the last three weeks, three of the daily reconciliations had errors I had to catch, on the 8th, the 12th and yesterday. The impact is that I am now re-checking work I used to trust, and that slows us both down. That is not like your first two months here. What is going on?"
[Listen. Then:]
"Okay. Here is what I need. From this week, reconciliations get a self-check against the bank statement before they reach me, and anything you are unsure of, you flag rather than guess. I will sit with you on Thursday for thirty minutes on the two that keep tripping you. We will look at this again in two weeks. Are you good with that, and is there anything you need from me?"

