Ubuntu Philosophy ("I Am Because We Are"): How to Live More Interconnectedly, Inspired by Desmond Tutu

---

The Ubuntu Philosophy of Interconnectedness: A Practical Guide

You got the promotion because you hit your numbers. Fair enough. But you also got it because someone covered for you during a bad quarter, someone trained you when you were useless at the job, and someone vouched for you in a room you weren't in. Most performance reviews don't have a line item for that. Most people don't either.

This is the gap Ubuntu philosophy points at. It's an African philosophical tradition, associated in public consciousness with Desmond Tutu, who invoked it during South Africa's transition out of apartheid to argue for a different basis for human worth — one built on relationship instead of individual output.

The phrase people know is "I am because we are." It sounds like a poster. It's actually a claim about how identity works.

What "I Am Because We Are" Actually Means

The individualist story most professionals operate on goes like this: you are your skills, your decisions, your discipline. Other people are either helpful or in the way. Your career is something you built.

Ubuntu rejects the premise. It holds that a person becomes a person through other people — you learn to speak because someone spoke to you, you learn what fairness means because someone treated you fairly or unfairly, you learn what competence looks like because someone modeled it. Your capacity to be a good colleague, a clear thinker, a decent boss, was formed in relationship before you ever exercised it alone.

Tutu applied this at national scale. Ubuntu informed the reasoning behind South Africa's Truth and Reconciliation process — the idea that restoring a person's humanity and restoring the community are the same project, not two separate ones. That's a bigger claim than "be nice to your coworkers." It says your well-being and others' well-being aren't two separate accounts. They're one.

You don't need to run a country to test this. You need to notice where you've been treating colleagues, family, or your team as instruments for your own outcomes rather than as the actual substance of your outcomes.

Where This Shows Up at Work

Think about the last time a project went well. Now trace it backward. The client relationship that closed the deal was built over years by someone else. The clean code you shipped depended on documentation someone wrote before you arrived. The confidence you had walking into that pitch came from a manager who once gave you a hard project and didn't let you fail at it.

None of that shows up on your LinkedIn. All of it is why you're capable of what you're capable of.

The Ubuntu argument isn't that you should feel guilty about this. It's that you should see it accurately. When you see it accurately, your behavior changes:

• You stop hoarding credit, because you can actually trace where the credit is owed.
• You stop treating mentorship as charity, because you understand you were built the same way.
• You stop optimizing only for your own metrics, because you understand the team's capacity is your capacity, distributed.
• You get less defensive about feedback, because your growth was never a solo project to begin with.

This isn't soft. It's a more accurate model of how value actually gets created in any organization bigger than one person.

The Trap: Confusing Interconnection With Losing Yourself

The obvious objection: doesn't this erase individual accountability? Doesn't a team-first philosophy get used to excuse bad performers and overwork good ones?

It can, if applied badly. Ubuntu isn't asking you to dissolve into the group or take on everyone's failures as your own. It's asking you to recognize a fact: your capability was co-created, and your continued capability depends on maintaining those relationships, not extracting from them.

There's a useful contrast here with the Golden Mean — Aristotle's idea that virtue sits between two extremes. Ubuntu without boundaries becomes self-erasure. Individualism without Ubuntu becomes isolation dressed up as independence. The competent move is holding both: strong individual standards, held inside real relational responsibility.

Try This: A Weekly Ubuntu Audit

Once a week, ask three questions:

1. Who made this week's work possible? Name them specifically. Not "the team" — actual people.
2. Where did I take credit that belonged partly to someone else? Correct it directly, even briefly.
3. Who's building their capability right now because of something I did or didn't do? A junior colleague, a report, a friend outside work.

This takes ten minutes. It rewires how you assign credit and attention, which changes how you lead, how you delegate, and how you handle conflict — because all three get easier once you stop pretending you're operating alone.

The Real Shift

Ubuntu doesn't ask you to be less ambitious. It asks you to be accurate about where ambition comes from and where it goes. Your growth was never private. Neither is your impact.

If you want to apply this concretely — in how you manage a team, mentor someone junior, or rebuild a working relationship that's gone flat — a mentor at Get Mentors can help you turn the principle into a specific plan for your situation this month.