There is a particular way the word Ujima arrives in modern conversations. It is invoked, often, as a slogan — pinned to a wall in a corporate office, dropped into a leadership keynote, printed on a tote bag. Ujima and the Job You Don't Want to Take? The slogan version of Ujima is easy to admire and easy to ignore. The actual concept, the one that has shaped Swahili / East African life for generations, is harder. It demands more. And it is, I think, more useful.
What Ujima Actually Means
The most commonly cited definition: 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. That sentence is true, as far as it goes. It is also incomplete. Ujima is held inside a wider Swahili grammar — a set of related concepts, social practices, and proverbs — that the standalone definition cannot carry.
If your neighbour's house is on fire, wet your own roof.Yoruba
The Question This Post Is About
Walking through a real career choice using Ujima as the question. 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
There is no certificate at the end of Ujima. There is only the slow accumulation of choices made differently — meetings shaped differently, relationships tended differently, decisions weighed differently. The reward is not visible. The cost is real. Over time the difference becomes a kind of life.