Negative feedback done well improves performance. Done badly, it damages trust permanently. Here is the structure and language that makes it land in African workplaces.
Marketing Lead
April 15, 2026
•
7 Mins Read
Most managers in Africa are not afraid of having difficult conversations. They are afraid of the aftermath.
They worry the employee will shut down, take it personally, or quietly start looking for another job. So the feedback gets softened until it means nothing, or delayed until it is too late to matter, or delivered in a way that is technically said but not actually heard.
According to a Harvard Business Review survey, 92% of respondents agreed that negative feedback, when delivered appropriately, is effective at improving performance. The issue is almost never whether to give the feedback. It is how.
This article gives you the structure, the language, and the practical guidance to deliver negative feedback in a way that is honest, specific, and respectful, particularly in Nigerian, Kenyan, and Ghanaian workplace contexts where hierarchy and relationship dynamics shape how feedback lands.
Most negative feedback conversations fail before the manager opens their mouth. The problems are structural:
A 2025 Gallup analysis found that employees are six times more emotionally impacted by negative interactions than positive ones. That asymmetry does not mean you should avoid negative feedback. It means you should deliver it carefully, because the impact is real and lasting.
The Situation-Behaviour-Impact (SBI) model from the Center for Creative Leadership is the most practically useful framework for negative feedback because it keeps the manager's language anchored to observable events rather than personality conclusions.
Situation: When and where did this happen? Be specific about context.
Behaviour: What did the person actually do or not do? Stick to the observable action. Avoid adjectives like "careless" or "dismissive."
Impact: What was the result? On the team, the client, the project, the outcome.
Example using SBI:
"During the Abuja client call on Wednesday [Situation], you responded to the client's concern about the timeline by saying the delay was the operations team's fault [Behaviour]. The client then called the MD to ask about internal issues, which escalated the relationship risk significantly [Impact]."
Compare that to: "You blamed the operations team in front of a client and it was unprofessional."
Both say the same thing. Only the SBI version gives the employee enough precision to change the behaviour.
Negative feedback should always be delivered in private, never in front of peers, never through a group message, and never in passing in a corridor. In Nigerian and Ghanaian workplaces where public embarrassment carries particular social weight, this is not optional.
Schedule a specific meeting and tell the employee you want to discuss something about their recent work. Do not use the word "feedback" in the meeting invite if it triggers anxiety in your environment. A simple "I want to talk through something that came up this week" is enough.
"I want to talk about something specific that I think is important for your development. I am raising it because I want to help you address it, not because I am building a case against you."
In cultures where a manager calling an employee in for a private conversation is assumed to mean trouble, naming the purpose explicitly reduces the defensive posture before the feedback is even delivered.
State the situation, the behaviour, and the impact clearly. Then stop. Do not add qualifications, apologies, or softening language that dilutes the message. The employee needs to hear the observation clearly before they can respond to it.
Ask: "What is your perspective on what I have just described?"
Then wait. This is the hardest part. The silence after delivering negative feedback is uncomfortable. Fill it with curiosity, not more words.
The employee's response may contain information the manager did not have. A client call that went wrong because the operations team did, in fact, miss a commitment. A missed deadline explained by a family health emergency the employee had not disclosed. That context does not excuse the behaviour, but it may change the development conversation significantly.
Close with one specific, agreed action. Not a list. One thing the employee will do differently, and if relevant, one way the manager will support it.
"What I would like from you going forward is that when a client raises concerns about another team's work, you redirect the conversation by saying you will follow up and get them a complete picture. I can help you prepare for how to handle those moments before the next client call. Does that work for you?"
In many Nigerian, Kenyan, and Ghanaian organisations, an employee receiving negative feedback from a senior is not simply processing information about their performance. They are navigating the social dynamics of hierarchy. Losing face in this context is a real and significant experience.
The mitigation is not to soften the feedback into meaninglessness. It is to deliver it in a way that separates the behaviour from the person. The behaviour was wrong; the person's worth to the team is not in question. Making that distinction explicit in the language of the conversation makes a meaningful difference.
When feedback needs to travel upward, or from a peer to someone with more seniority, the framing requires additional care. The receiver may interpret peer feedback as insubordination rather than development input if it is not carefully positioned.
Talstack's 360 Feedback feature provides a structured format for this: feedback is collected against defined behavioural competencies, anonymised where appropriate, and presented as a development tool rather than a rating judgment. That context changes how it is received by employees and senior leaders who might otherwise be defensive.
"Thanks for making time. I want to talk through something specific that came up recently. My intention is to help you address it, not to criticise you as a person, and I want to hear your perspective after I share what I observed. Can we start there?"
Avoid it. Research on feedback delivery consistently shows that the sandwich approach causes confusion: employees often remember only the positive parts, or they learn to discount the praise because they are waiting for the "but." Deliver positive and negative feedback separately, as they arise, so each has its own weight. If you have both in the same meeting, be explicit about the shift: "I also want to share something that needs to change."
Pause and acknowledge the emotion directly: "I can see this is hard to hear. Let us take a moment." Do not push through the agenda as though the emotional response is not happening. In most African workplace cultures, an employee showing emotion in a one-on-one is telling you something important about how the message landed. Treat it as information, not disruption.
As soon as possible after the event, once both parties are composed and there is privacy. Feedback given within 24-48 hours of the behaviour is significantly more actionable than feedback given weeks later. The employee can still connect the feedback to the specific situation, which makes the learning more precise and more likely to change behaviour.
In-person is almost always better for substantive feedback. As psychology researcher Jeremy Sutton notes, a phone call masks body language, and email lacks context and can feel like a formal written record rather than a development conversation. Reserve written documentation for formal performance improvement situations where HR requires a paper trail. For coaching conversations, do it in person.
Negative feedback is not the opposite of respect. Delivered well, it is one of the most respectful things a manager can do: it treats the employee as a person capable of changing and worthy of an honest conversation.
The structure is simple: specific situation, observable behaviour, clear impact, space for their perspective, one forward-looking action. That formula, applied consistently, makes negative feedback a development tool rather than a damage event.
Talstack's Performance Reviews module supports structured feedback documentation, making the evidence behind development conversations accessible to both managers and HR without relying on memory or informal notes.
