It was the second morning of a team-building workshop at a public consortium whose mission is to build bridges with Africa. We were talking about what working culture they wanted to have. And someone on the team said a word that wasn’t on my agenda: Ubuntu.
The brief was specific. About twenty people from all areas of the organisation, two three-hour sessions, and two problems that the team itself had put on the table on the first day: information wasn’t circulating between departments and the building separated them. This isn’t a metaphor: there are isolated areas, a media library at the back, and that translates into very real operational silos.
We had already worked on leadership, delegation, and difficult conversations. The second morning was dedicated to the most uncomfortable part of any team workshop, the part that cannot be solved with a tool: what culture do we want to have among ourselves? And that was when the word appeared.
What Ubuntu really means: beyond a pretty phrase
The African origin of the ethical concept and its impact on management
You’ve probably seen it on a T-shirt or in a corporate presentation, translated as “we are all one”. Put like that, it commits you to nothing.
Ubuntu is an ethical concept from the Bantu languages of southern Africa that is summarised in a proverb: umuntu ngumuntu ngabantu, a person is a person through other people. Desmond Tutu explained it by saying that someone with Ubuntu is accessible, hospitable, willing to share, and understands that their own humanity is bound up with that of others. Nelson Mandela used it as the key to the reconstruction of his country and to transform the social management of his nation.
The key difference between the traditional cooperative model and the Ubuntu vision
Notice the difference with our “unity is strength” (la unión hace la fuerza). Ubuntu doesn’t say that it’s convenient to cooperate. It says that without others, there is no one there at all.
And here is what made that morning pause for a moment: in an institution whose raison d’être is dialogue with Africa, the most exact description of the working culture the team wanted came from Africa. There was no need to import a Scandinavian model or an Anglo-Saxon framework. The method was already inside what the house defends every single day outwards.
Why it is hard to apply the Ubuntu philosophy in organisations
Because our working culture is built on individual merit. We evaluate people, we promote people, we reward people. And with that logic, three behaviours appear that anyone can recognise, whether in a public administration or in any type of business.
The danger of hoarding information and creating operational silos
The first is hoarding information. Not out of malice: because knowing something others don’t gives security, value, and a place. No one would say it out loud, but the result can be seen in any organisation where you have to reconstruct by phone calls what should be in a common repository. For a team that manages external communication, this has a direct consequence: what arrives at the end is published late.
Retaining the “how” and the hidden cost of failing to delegate in teams
The second is retaining the “how”. “I’ll do it faster myself” is an honest phrase, almost always true in the short term and profoundly expensive in the medium term. Whoever retains the “how” ends up overloaded and surrounded by disengaged people.
When disagreement turns into a personal problem
The third is turning disagreement into a personal problem. When disagreeing is experienced as a threat to one’s own position, people argue against someone instead of arguing about something.
The Ubuntu philosophy does not solve this with good intentions. It solves it by changing the unit of measure: if I am through others, what the team lacks, I lack. This is not generosity. It is arithmetic.
The three practical translations of the Ubuntu philosophy for organisation management
1. Information as a common good and shared repository
Information is a common good, not a personal asset. The question stops being “who do I need to inform?” and becomes “who will need this and won’t know it exists?”.
- Operationally: A single repository and an agreement on what is uploaded, where, and within what timeframe after each activity.
2. Delegating the “how” based on the group’s capacity
The “how” is delegated because the capacity belongs to the group. In a public body, the “what” is given by the mandate, and the “what for” by the mission. The margin for leadership lies precisely in the “how”.
- Exercise to check if you are letting go: Take three tasks that are not delegated today and write down, for each one, what exactly is feared and what acceptance criteria would be validated. The three usual reasons — fear, control, and lack of time to explain — hold up much worse in writing during decision-making.
3. Separating the person from their role in conflict management
Separating what someone does from who they are. In feedback: observable facts and the impact they have on me, never character traits. And quickly, because what isn’t said in time festers and ends up being told to others.
What the team decided to take away: small and verifiable decisions
Spaces for face-to-face coordination and operational empathy
This is what interests me most about that morning: Ubuntu didn’t end up on a poster. It ended up in small, verifiable decisions.
- Return to having one face-to-face coordination meeting a week and recover team breakfasts in the courtyard.
- Replace, before the next session, at least one conversation that would normally go through a digital channel with a face-to-face conversation.
- And a half-day rotation pilot between areas, what other organisations call front days or “visit my life”: spending a few hours working where the other person works, which is the fastest and cheapest way to generate operational empathy.
The methodological closure: what to keep, start, and stop (Keep, start, stop)
The closure wasn’t a list of good intentions either: each person wrote on three post-it notes what they maintain, what they start, and what they stop doing. Keep, start, stop. Personal, individual, and with a review agreed upon at two months.
What the Ubuntu philosophy is not in the corporate environment
Limits, responsibility, and regulatory clarity without losing cohesion
It is worth mentioning, because this is where the concept is distorted within a business or organisation.
- It is not diluting responsibility: tasks continue to have a name and a deadline.
- It is not permanent consensus: decisions are made, and sometimes a single person decides; what cannot happen is that people find out through the grapevine.
- And it is not renouncing limits. Quite the opposite: in an institution that manages public funds, where the rule is not negotiable, caring for the relationship is precisely what allows you to say “no” clearly and keep working together the next day.
Why cohesion is infrastructure and not a soft value
I work with organisations of small teams, heavy workloads, and little room for improvisation. There, cohesion is not a soft value: it is infrastructure. A team that shares what it knows, that lets go of the “how,” and that speaks its mind in time is not just a nicer team. It is a team that delivers.
And I am left with the clue from that morning: sometimes the method an organisation needs is already inside what that organisation defends. At Sibega, we accompany you to identify it, activate it, and turn it into real culture.
So I close this text with the very same question with which I closed the workshop that day:


