From Blame Game to Growth Engine

Have you ever felt like the person in the picture during a monthly results meeting? 🙋‍♂️

The cartoon might be a joke, but the feeling is painfully real in many organizations. In my experience leading monitoring and evaluation programs in both the public and private sectors, I’ve often seen KPI review sessions turn into “blame games” where the main goal is to assign fault for missed targets.

The problem is, when these meetings become spaces for confrontation, fear replaces learning.

A Shift in Perspective: From Blame to Learning

A significant part of my consulting work has been dedicated to transforming this dynamic. My methodology focuses on humanizing the data-driven decision-making process by coaching leaders and teams to see these meetings for what they truly should be:

  • ✅ Collaborative learning sessions.
  • ✅ Forums for continuous improvement.
  • ✅ Turning points to realign strategy.

This isn’t about ignoring underperformance. On the contrary, it’s about addressing it constructively, with a deep sense of humanity and respect. When a goal is repeatedly missed, the data will make it obvious. However, the conversation must shift from “Who is to blame?” to “Why did this happen and how can we fix it together?”

The Key: Connecting Data to Action

The secret is to link every results review session to a clear improvement or remediation plan, assigning concrete responsibilities so the team can focus on solutions.

Fortunately, with effective change management and by fostering a culture of respect, I’ve seen teams move from fear to proactivity, using data not as a weapon, but as a compass.


Join the Conversation

Now, I’d like to ask you: What are these sessions like in your company? What strategies do you use to prevent them from turning into “witch hunts”? I would love to read your experiences in the comments. And if your organization struggles with this issue, send me a direct message. I’d be happy to help you find a solution.

Leave a Reply

Your email address will not be published. Required fields are marked *