Begin with the word itself. Ujima, in Swahili, sits in a different grammatical and emotional register than its closest English equivalents. Ujima and the Difficult Manager? You cannot answer that question without first sitting with the word — and noticing what English doesn't quite have a slot for.
What Ujima Actually Means
Translators usually settle on something like: Ujima is the third principle of Kwanzaa and a long-standing Swahili concept meaning 'collective work and responsibility.' It is the recognition that a community's problems are not an individual's burden alone, and that the welfare of the whole is the proper concern of every member. In practice it shows up as ownership mentality, shared maintenance, and the willingness to do work that doesn't have your name on it. It is a defensible translation. But translation is the surface. Ujima carries underneath it a set of assumptions — about what a person is, what owes what to whom, and what success even means — that the English sentence cannot deliver.
Ujima.Swahili — Collective work and responsibility.
The Question This Post Is About
A composite case: the manager whose problem Ujima would diagnose differently. The question is worth taking seriously, because Ujima 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 Ujima reading offers a different question: what did we, as a team, fail to make possible for the person carrying this work? The maintenance of shared systems — documentation, onboarding, internal tooling — is a promotable contribution. The case is not unusual. The reading of it, in the spirit of Ujima, 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 Ujima would have us do here, with these particular people, in this particular knot. The maintenance of shared systems — documentation, onboarding, internal tooling — is a promotable contribution. The discipline of asking the Ujima 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 Ujima? 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 Ujima, 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 Ujima for a month. Not as a project. As a quiet experiment. Notice what changes. Ujima is not learned by reading; it is learned by repetition.