Performance Ecosystem Management

Table of Contents

The P.O.S.H. Leadership Curriculum

Learning Objectives

By the end of this module, you will be able to:

Distinguish between individual failure and system failure
Identify the hidden structures that shape behaviour in your team
Map a performance problem to its root cause using a simple diagnostic tool
Remove one source of friction from your team’s workflow this week
Explain to others why blaming people is almost always wrong

The Story

Kofi was six months into his role as operations director at a medium‑sized logistics company in Tema. He had a problem. His dispatch team was consistently missing delivery windows. Not by much. Fifteen minutes here. Twenty minutes there. But enough that clients were noticing. Enough that his phone rang at 7pm with complaints.

His instinct was to blame the dispatchers. He had inherited them from the previous director. Maybe they were lazy. Maybe they lacked discipline. Maybe he needed to replace them.

But something held him back. He had read something once about systems thinking. About how most performance problems are not people problems. They are design problems.

So he did something unusual. He spent a week just watching. Not judging. Not correcting. Watching.

Here is what he saw.

The dispatchers were using a paper logbook to track vehicles. When a driver returned, they wrote down the time. Then they manually calculated turnaround time. Then they entered it into a spreadsheet. The whole process took about seven minutes per vehicle.

With fifteen vehicles returning each evening, that was nearly two hours of manual data entry. By the time the dispatchers finished, they were rushing to assign the next day’s routes. Mistakes happened. Routes were suboptimal. Deliveries ran late.

The problem was not lazy dispatchers. The problem was a broken system.

Kofi replaced the paper logbook with a simple WhatsApp based check‑in. Drivers sent a message when they returned. A free integration logged the time automatically. The dispatchers went from two hours of data entry to fifteen minutes of review.

Late deliveries dropped by 60 percent within three weeks. He did not fire anyone. He did not threaten anyone. He just fixed the system.

Kofi learned something that changed how he leads forever. When you see a performance problem, your first question should never be “Who is to blame?” Your first question should always be “What is making it hard for good people to do good work?”

Insights from Psychology

The psychological research on performance is clear. Context shapes behaviour more than personality.

The Fundamental Attribution Error. This is the most researched bias in social psychology. When we see someone else fail, we attribute it to their character. They are lazy. Careless. Unmotivated. When we fail ourselves, we attribute it to our circumstances. The traffic was bad. The deadline was unreasonable. I was exhausted.

For leaders, this bias is dangerous. It turns every performance problem into a personnel problem. You start replacing people who were never the issue. You create a culture of fear where everyone hides their mistakes. And the real problem, the system, never gets fixed.

The Stanford Prison Experiment. You know this study. Zimbardo assigned students to be guards or prisoners in a simulated prison. Within days, the guards became cruel. The prisoners became passive and depressed. The study was stopped early because it became unethical.

The disturbing lesson is this. Ordinary people placed in a bad system will do bad things. Not because they are bad people. Because the system shapes them. The same is true for performance. Good people placed in a broken system will underperform. Not because they lack skill. Because the system makes it impossible to succeed.

The Hawthorne Effect. Researchers at the Hawthorne Works factory in Chicago wanted to know what improved productivity. They tried brighter lights. Productivity went up. They tried dimmer lights. Productivity went up. They tried changing break times. Productivity went up.

The conclusion was unexpected. Productivity improved not because of the changes themselves. Productivity improved because someone was paying attention. The workers felt seen. They felt valued. They performed better.

The lesson for leaders is subtle but powerful. Sometimes the problem is not the system or the people. Sometimes the problem is that no one has bothered to look. Your attention alone can shift performance.

Cognitive Load and Decision Fatigue. Psychologists have shown that humans have limited cognitive bandwidth. When people are overwhelmed with unnecessary decisions, their performance degrades. They make errors. They take shortcuts. They burn out.

Every friction point in your system, every approval required, every manual data entry, every confusing form, adds cognitive load. Reduce the friction. Improve the performance. It is that simple.

Insights from Business

The business literature on performance management has undergone a quiet revolution. The old wisdom was to blame people. The new wisdom is to design systems.

Deming’s 85 Percent Rule. W. Edwards Deming, the quality management pioneer, famously argued that 85 percent of performance problems are caused by systems. Only 15 percent are caused by people. Yet most organizations spend 85 percent of their energy blaming people and only 15 percent fixing systems.

Deming wrote: “A bad system will beat a good person every time.” Think about that. You can hire the smartest, most motivated person in the world. Put them in a broken system. They will fail. And then you will blame them for failing. That is not management. That is self deception.

The Toyota Production System. Toyota became one of the most successful companies in history by doing one thing differently. When a problem occurred, they did not ask “Who caused this?” They asked “What caused this?” Then they dug deeper. And deeper. They asked “Why?” five times until they reached the root cause.

This is called the Five Whys. It is deceptively simple. A worker stops the production line because a part is missing. Why? Because the parts bin was empty. Why? Because the supplier was not notified of the new schedule. Why? Because the scheduling system does not automatically notify suppliers. Why? Because no one ever built that feature.

The root cause is not a lazy worker. The root cause is a missing feature in a software system. Fix that. The problem disappears permanently.

The Cost of Friction. Bain & Company studied the hidden costs of organizational friction. They found that the average employee spends 20 to 30 percent of their week on non‑productive work. Manual data entry. Waiting for approvals. Searching for information. Attending unnecessary meetings.

That is one full day per week. Per employee. Multiply that across your team. Across your organization. The cost is staggering. And almost all of it is invisible.

Psychological Safety and Error Reporting. Edmondson’s research at Harvard showed that the best performing teams report more errors, not fewer. Why? Because they feel safe enough to admit mistakes. Lower performing teams hide their errors. The errors still happen. They just never get fixed.

Leaders who punish mistakes create silence. Silence creates hidden failure. Hidden failure creates catastrophe. The only way to build a learning organization is to make it safe to be wrong.

Insights from Philosophy

The philosophers have been thinking about systems longer than the business schools.

Aristotle on Four Causes. Aristotle argued that to truly understand something, you must understand four different causes. The material cause (what it is made of). The formal cause (its shape or structure). The efficient cause (what made it). The final cause (its purpose).

Apply this to a performance problem. The material cause is the people and tools. The formal cause is the process and structure. The efficient cause is what triggered the failure. The final cause is the goal the system was designed to achieve.

Most leaders stop at the efficient cause. Who pushed the wrong button? Who made the error? Aristotle would say you have not understood anything until you have examined all four.

The Stoics on Control. Epictetus wrote: “Some things are within our power, while others are not.” The Stoics spent their lives learning to distinguish between what they could control and what they could not.

For a leader, the distinction is essential. You cannot control another person’s character. You can control the system they work within. You cannot guarantee that people will never make errors. You can design processes that catch errors before they become disasters.

Focus your energy on what you can actually change. That is almost never the people. It is almost always the system.

Meadows on Leverage Points. Donella Meadows was a systems thinker who studied where to intervene in a complex system. She identified twelve leverage points, from weakest to strongest.

The weakest leverage point is changing the numbers (adjusting budgets, tweaking targets). The strongest leverage point is changing the paradigm (the mindset out of which the system arises).

Most leaders pull the weakest levers. They adjust targets. They change incentives. They rearrange reporting lines. Meadows would say: go deeper. Change the goal. Change the rules. Change the mindset. That is where real leverage lives.

Insights from African Wisdom

The African philosophical tradition has always understood interconnectedness. Western management thinking is only now catching up.

Nsempi (Interconnectedness). In the Akan tradition, nothing exists in isolation. Every action has ripples. Every person is part of a web. When a leader sees a performance problem and blames an individual, they are seeing a single thread and ignoring the whole web.

Nsempi teaches that you cannot understand the part without understanding the whole. The dispatcher who misses a deadline is not an isolated failure. They are a symptom of a system that made success difficult or impossible.

The Palaver Tradition. When a conflict or problem arose in traditional West African communities, the elders would call a palaver. Everyone sat together. Everyone spoke. No one was blamed at the start.

The goal was not to find a guilty party. The goal was to restore balance. To understand how the community had contributed to the problem. To find a solution that would prevent the problem from recurring.

The palaver tradition is systems thinking. It assumes that problems are rarely the fault of a single person. They emerge from relationships, processes, and structures. Fix the structure. The problem dissolves.

The Talking Drum. The talking drum does not produce sound in isolation. It produces sound in relation to the drummer’s hand, the tension of the skin, the shape of the wood, the air in the room. Change any one element. The sound changes.

Performance is the same. It emerges from the interaction of many elements. The leader who only looks at the drummer is missing most of the music.

Ubuntu and Shared Accountability. “I am because we are.” Ubuntu does not erase individual responsibility. It places individual responsibility within a communal context. When one person fails, the community has failed to support them. When one person succeeds, the community has enabled that success.

For a leader, Ubuntu means that you are accountable not just for your own actions but for the systems you have built. If your team underperforms, the question is not “Who is lazy?” The question is “What have I failed to provide?”

Insights from Sacred Tradition

The sacred texts warn against the rush to blame.

The Woman Caught in Adultery (John 8). The religious leaders brought a woman to Jesus. They said she had been caught in the act. The law demanded she be stoned. Jesus did not ask for her side of the story. He did not examine the evidence. He simply said: “Let any one of you who is without sin be the first to throw a stone.”

One by one, they walked away. Jesus was not excusing the woman’s action. He was refusing to participate in a system that punished one person while ignoring the failures of everyone else.

When you are about to blame an employee for a performance problem, ask yourself: “Who else contributed to this outcome? What have I done to make success possible? What have I failed to provide?”

The Speck and the Log (Matthew 7). “Why do you see the speck that is in your brother’s eye, but do not notice the log that is in your own eye?” Jesus was teaching about judgment, but the metaphor applies to performance management.

It is easy to see the speck in your employee’s performance. The missed deadline. The sloppy report. The poor decision. It is much harder to see the log in your own systems. The confusing process. The missing training. The impossible deadline.

Remove the log first. Then help with the speck.

The Body Metaphor (1 Corinthians 12). Paul wrote that the church is like a body. The eye cannot say to the hand, “I have no need of you.” When one part suffers, the whole suffers.

When a team member underperforms, the whole team suffers. But the solution is not to cut off the part. The solution is to understand why the part is struggling and what the rest of the body can do to help.

Practical Exercise

This exercise will take approximately 45 minutes. Do it alone first. Then do it with your team.

Step One. Identify a Performance Problem.

Write down one recurring performance problem in your team or organization. Be specific. Not “low productivity.” Something like “The dispatch team misses delivery windows 20 percent of the time.”

Step Two. Map the System.

Draw a simple map of the process. Use a piece of paper. Write down every step from start to finish. Include:

Who does each step
What tools they use
What information they need
Where delays happen
Where errors happen

Do not judge yet. Just map.

Step Three. Ask “Why?” Five Times.

For the problem you identified, ask “Why?” Write down the answer. Then ask “Why?” again. Keep going until you have asked five times.

Example:

Problem: Dispatchers miss delivery windows.
Why? Because they are rushing to assign routes.
Why? Because they spend two hours on manual data entry.
Why? Because they use a paper logbook.
Why? Because no one ever set up a digital check‑in system.
Why? Because the previous director did not see it as a priority.

The root cause is not lazy dispatchers. The root cause is a missing system and a previous leader who did not prioritize it.

Step Four. Identify Leverage Points.

Look at your map. Where is the friction? Where do delays happen? Where do errors happen? Where does information get stuck?

Circle three places where a small change could have a big impact.

Step Five. Choose One Change.

Pick the smallest change that could produce the biggest improvement. Do not try to fix everything. Choose one thing.

Write down:

What you will change
Who needs to be involved
What resources you need
When you will implement it
How you will measure success

Step Six. Test the Change.

Implement the change for one week. Measure the result. If it works, keep it. If it does not, try something else.

Application

This week, do two things.

First. When you see a performance problem, pause before you blame anyone. Say to yourself: “What is making it hard for good people to do good work?” Then look for the answer in the system, not the person.

Second. Remove one source of friction from your team’s workflow. A pointless approval. A confusing form. A manual data entry. A meeting that could be an email. Just one. Remove it. Watch what happens.

Do not announce it. Do not take credit. Just fix it. That is what leaders who understand systems do. They do not blame. They build.

References

Deming, W. E. (1986). Out of the crisis. MIT Press.
Edmondson, A. C. (2018). The fearless organization. Wiley.
Kahneman, D. (2011). Thinking, fast and slow. Farrar, Straus and Giroux.
Kpodo, P. E. (2026). Managerial soft skills in the structure of effective leadership. Master’s thesis, HSE University.
Meadows, D. (1999). Leverage points: Places to intervene in a system. Sustainability Institute.
Ross, L. (1977). The intuitive psychologist and his shortcomings. In L. Berkowitz (Ed.), Advances in experimental social psychology (Vol. 10, pp. 173‑220). Academic Press.
Senge, P. M. (1990). The fifth discipline. Doubleday.
Zimbardo, P. G. (2007). The Lucifer effect. Random House.

A Final Word

Module 23 is not about being nice. It is about being effective.

Blaming people feels satisfying. It is quick. It is simple. It protects your ego. But it does not fix anything. The problem will return. The next person will fail the same way. You will blame them too. The cycle will continue.

Fixing systems is harder. It requires patience. It requires curiosity. It requires the humility to admit that you might have designed something poorly. But it works. The problem stays fixed. Your team stops walking on eggshells. Performance improves permanently.

Choose the harder path. Fix the system. Not the person.

This module is part of the P.O.S.H. Leadership Curriculum, available for free at [www.poshlifeplan.com]. The curriculum was developed through research conducted for a master’s thesis at HSE University.