Ubuntu and the Long-Standing Conflict

Ubuntu · Southern African (Bantu)

If you have heard Ubuntu only in the context of corporate diversity training or a viral leadership quote, you have not really heard Ubuntu. Ubuntu and the Long-Standing Conflict? The version of the word that survives in Southern Africa is older, stranger, and more demanding than the version that travels.

What Ubuntu Actually Means

The most commonly cited definition: Ubuntu, in its most cited form, is captured in the Nguni phrase 'umuntu ngumuntu ngabantu' — a person is a person through other people. It names a worldview in which the self is not a fortress but a node in a network, and in which dignity, identity, and success are inherited from and accountable to community. It has shaped post-apartheid South Africa, modern leadership theory, and increasingly the way thoughtful organisations think about teams. That sentence is true, as far as it goes. It is also incomplete. Ubuntu is held inside a wider Bantu grammar — a set of related concepts, social practices, and proverbs — that the standalone definition cannot carry.

Motho ke motho ka batho.Sotho — A person is a person because of others.

The Question This Post Is About

Two colleagues, ten years, one persistent disagreement. What Ubuntu does. The question is worth taking seriously, because Ubuntu is one of those concepts that loses its shape when handled carelessly — and recovers it as soon as the reader is willing to slow down and listen.

Take a small, ordinary case. A team of nine. A project that was supposed to take a quarter is now in its second. The manager has the option to find a single person to assign blame to and to move on. The Ubuntu reading offers a different question: what did we, as a team, fail to make possible for the person carrying this work? Every retrospective begins with the question of what the team made possible together, not who failed individually. The case is not unusual. The reading of it, in the spirit of Ubuntu, is.

A Second Angle

Notice what the case is not asking. It is not asking who is to blame. It is not asking how to make the situation more efficient. It is asking what Ubuntu would have us do here, with these particular people, in this particular knot. Every retrospective begins with the question of what the team made possible together, not who failed individually. The discipline of asking the Ubuntu question — instead of the efficiency question, or the blame question — is what changes a working life over years.

Where the Concept Resists

There is also the question of authority. Who gets to speak for Ubuntu? The traditions in which it lives are old, plural, sometimes in disagreement with each other. Anyone — including the writer of this essay — who claims a definitive reading is overreaching. The careful reader treats every restatement of Ubuntu, including this one, as one voice among many.

What to Do With This

What can you do with this? Begin small. Choose one place — one meeting, one relationship, one daily ritual — and run it through Ubuntu for a month. Not as a project. As a quiet experiment. Notice what changes. Ubuntu is not learned by reading; it is learned by repetition.

Ubuntu: I Am Because We Are by Amara Osei

The full philosophy, as a book

The full philosophy of shared success — across leadership, conflict, accountability, and the digital age.

Read on Amazon