Abraham Maslow published his hierarchy of needs in 1943. He was writing about individual human psychology. But I have been thinking — for a while now — that he was also writing about teams. Every layer of that pyramid describes something a team needs before it can reach the next one. Ignore any level and the whole structure stays stuck.
Leadership has many frameworks. Most of them feel like someone else's theory applied to your situation. Maslow's pyramid feels different. It feels true because it describes something fundamental: humans cannot think about growth when they are worried about survival. And teams are human. They obey the same rules.
What follows is how I have learned to read Maslow — not as a psychology textbook, but as a practical guide to building teams that function, and growing teams that excel. Each level has two faces: what you need to do when building a team from scratch, and what you need to do when growing a team that already exists.
Five Levels. Two Dimensions. One Framework.
I want to be direct about what Maslow's hierarchy means in a team context: each level is not a soft aspiration. It is a prerequisite. You cannot skip a level any more than you can build the second floor of a house before the first is in place. The most sophisticated team culture strategies fail — not because the ideas are wrong, but because the foundation beneath them is missing.
The pyramid does not move at the same speed for everyone on the team. Some people arrive already at level three. Others are still anchored at level one. Your job as a leader is to understand where each person actually is, not where you wish they were, and to ensure the environment supports the whole range.
Physiological Needs: The Basics That Are Not Basic
Before a team can function well, its members need their physical and material needs addressed. The right tools. Machines that do not slow them down. A workspace — whether physical or remote — that does not fight against them. Fair compensation that removes the constant background noise of financial anxiety.
This sounds obvious. It rarely is. I have seen teams asked to produce excellent work on laptops from three generations ago, on video calls that drop every ten minutes, in open-plan environments too noisy for sustained concentration. Leadership set ambitious goals. The foundation had not been built. Ambition without adequate resources is just pressure with a positive-sounding name.
As the team develops, the question shifts from do they have what they need to do they have what they need for the next level of work. A team that was capable at one scale may hit resource constraints at a higher one. Identify those gaps early — tooling, access, environments, bandwidth — before they become blockers that stall momentum mid-delivery.
Never assume that because basic needs were met yesterday, they remain met today. Teams grow. Work changes. Revisit the foundation regularly.
Safety Needs: Where Psychological Safety Actually Begins
Safety in a team context has two faces. The first is structural: clear roles, defined responsibilities, transparent decision-making, and reasonable job security. People who do not know what is expected of them, or who feel their position is perpetually at risk, spend enormous cognitive energy on self-protection rather than contribution. That energy is lost forever.
The second face is interpersonal. Early in my leadership career, I ran teams where people were technically skilled but reluctant to speak up. They had opinions — good ones — but the environment did not feel safe enough to voice them. I had created structural safety through clear roles, but had not created interpersonal safety. Both are required.
A growing team needs psychological safety as its engine. This is not softness. It is the prerequisite for innovation. Teams that feel safe enough to propose ideas that might fail, to surface problems before they become crises, and to disagree with each other — and with leadership — in good faith, produce better outcomes. Consistently. The research supports it. So does my experience across three countries.
The test I use: do junior members of the team speak in meetings where senior members are present? If not, safety has not been built at level two. Nothing above it will work as intended.
Belonging & Love Needs: Culture Is What Happens When You Are Not in the Room
Once safety is established, humans need to feel that they belong — that they are part of something, not just performing a role within it. For a team, this means creating genuine community: open communication, real collaboration, and the kind of trust that develops when people see each other handle difficulty with honesty and care.
Belonging cannot be manufactured through team-building events alone. It is built in the small moments: how a mistake is handled in a code review, whether a struggling colleague is supported or ignored, whether diversity of background and thought is genuinely valued or just formally acknowledged.
As a team matures, belonging deepens into something more deliberate: a culture of mutual accountability, inclusive decision-making, and constructive conflict. The goal is not a team that never disagrees — disagreement handled well is how teams stay sharp. The goal is a team where conflict is addressed directly and resolved without residue.
Belonging, at this level, means that every person on the team can say: this team is better because I am here, and I am better because this team exists. That is the standard. It is worth holding to.
Esteem Needs: Recognition Is Not a Nice-to-Have
Recognition matters. This is not about flattery or performance theatre. It is about acknowledging contribution in a way that is specific, genuine, and timely. When someone solves a difficult problem, names it as good work — publicly, clearly, with context. When a team delivers under pressure, make the effort visible to the people above them in the organisation.
Alongside recognition, esteem is built through opportunity: chances to learn new skills, to stretch into adjacent areas, to take on work that is slightly beyond current capability. People who feel their professional development is valued by their employer feel more confident, take more initiative, and stay longer.
A growing team needs structured opportunities for members to develop leadership at every level — not just formal leaders, but domain leads, mentors, and decision-owners at the appropriate scope. Esteem grows when responsibility is earned and then trusted. It erodes when people are given titles without authority, or authority without support.
Constructive feedback is the other half of esteem at this stage. Feedback that helps someone improve — direct, specific, delivered with care for the person — is one of the highest forms of professional respect. It says: I believe you are capable of more, and I am willing to help you get there.
Self-Actualisation: Where Teams Create the Future
Self-actualisation, for individuals, is the pursuit of full potential. For a team, it looks like this: people doing the most meaningful work of their careers, in an environment that challenges them, trusts them, and gives them genuine ownership over the outcome. This is the level where teams stop executing plans and start creating them.
Getting to this level requires deliberately protecting the conditions that support it. Autonomy without direction becomes chaos. Challenge without support becomes burnout. The leader's role at this level is less manager and more environment architect — designing the conditions in which self-actualising work can happen consistently, not occasionally.
A team operating at self-actualisation is continuously learning, continuously improving, and — crucially — continuously questioning whether current approaches remain the right ones. This is where the difference between optimisation and disruption becomes important. Sometimes you improve the engine. Sometimes you build the bullet train.
The team that has climbed to this level has earned something rare: the confidence to challenge its own assumptions. That is the highest form of team growth. It requires all four levels beneath it to be stable, intentional, and sustained.
The Pyramid as a Leadership Habit
What I have found, over years of building and growing teams across three countries, is that the pyramid is never fully climbed once and left behind. It requires ongoing attention. A team that has reached self-actualisation can slide back to level two if safety is undermined — by reorganisation, by a toxic new hire, by a leader who stops listening. The foundation needs maintenance.
The most useful thing Maslow's pyramid offers a leader is not a checklist. It is a diagnostic. When a team is underperforming, the question is not: how do I motivate them? The question is: which level of the pyramid is not being met right now? That question almost always has a clear answer. And that answer almost always points to something the leader can act on.
A team does not need inspiration to perform well. It needs its hierarchy of needs to be met. Inspiration comes after that — naturally, almost inevitably.
I have led teams that were technically excellent but deeply uncomfortable at level two — they had no safety, no willingness to surface problems, and as a result they over-engineered quietly rather than raising concerns loudly. I have led teams with tremendous belonging and almost no esteem — everyone liked each other, no one grew. Each gap produces a specific kind of underperformance. Each gap has a specific kind of fix.
Maslow did not write his hierarchy for managers. But I am glad I found it in a context where it could be applied. It is one of those rare frameworks that becomes more useful the longer you work with it — not because it is complicated, but because it is true.