Skip to content
Enneagram Growth
On this page

Team Dynamics by Center

~9 min read

How Body, Heart, and Head center teams operate -- and what happens when a center is missing

The most common team dysfunction is not personality conflict. It is the absence of an entire way of seeing. A team of analysts who never check how people feel. A team of relationship-builders who never ship anything. A team of doers who never ask whether they are doing the right thing. The Enneagram's three centers explain why teams get stuck, and what is missing when they do.

Need a refresher on the three centers? Read The Three Centers first.

Team Dynamics by Center

Body Center Teams (8, 9, 1)

Body Center teams are action-oriented. They want to do something. Decisions get made quickly, and there is a bias toward movement. The shared emotional undercurrent is anger, though it surfaces differently in each type: Eights express it openly, Ones channel it into criticism and standards, and Nines suppress it until it leaks out sideways.

Scenario: The leadership team. Picture a leadership team of an Eight CEO, a One COO, and a Nine head of HR. The Eight drives decisions at speed, the One immediately starts refining and correcting the execution plan, and the Nine quietly absorbs the tension between them without voicing the objection that could prevent a major misstep. The shadow side: unacknowledged anger simmers beneath the surface. The Eight is openly frustrated, the One is silently resentful, and the Nine is numb.

Scenario: The operations floor. Now picture a warehouse operations team with mostly Body types. The morning stand-up lasts four minutes because no one wants to talk about problems; they want to fix them. A shipping error happens at 10 a.m. and is resolved by 10:20. Efficiency is remarkable. But when a new safety protocol requires slowing down and filling out additional forms, the entire team bristles. The Eight supervisor calls it "bureaucratic nonsense." The One quality lead redesigns the form to be "less stupid." The Nine shift managers just forget to distribute it. The team's strength (decisive action) becomes its weakness (resistance to anything that feels like friction).

Scenario: The conflict that nobody names. A Body Center project team has been underperforming for weeks, but nobody can articulate why. The Eight project lead thinks the team is fine; they just need to push harder. The One business analyst thinks the project plan has flaws but does not want to seem like she is undermining the lead. The Nine developer agrees with everyone in every meeting and then goes back to his desk and does what he thinks is best anyway. The real problem: all three are angry, and none of them are saying so. The Eight is angry at the client. The One is angry at the sloppy process. The Nine is angry at being ignored. But because Body types process anger through action rather than words, the anger shows up as overwork, micromanagement, and passive resistance instead of a conversation.

If your team skews Body: Build in reflection pauses before big decisions. Create explicit space for the Nines to disagree before they go along with something they will regret. Schedule a ten-minute "what are we not saying?" check-in at the end of major meetings. And watch for the team's tendency to power through problems that actually require stopping, thinking, and feeling.

Heart Center Teams (2, 3, 4)

Heart Center teams are relationally attuned. They care about how people feel, how things look, and whether the team is connected. The shared emotional undercurrent is shame, though it wears different masks: Twos feel shame when they are not needed, Threes feel shame when they are not successful, and Fours feel shame when they are not special.

Scenario: The marketing department. Imagine a marketing department staffed mostly by Twos, Threes, and Fours. The Twos are making sure everyone feels supported. The Threes are driving toward the campaign deadline. The Fours are advocating for creative integrity. Sounds balanced until the first round of negative feedback arrives. The Twos feel unappreciated ("We did all this work and nobody cares"). The Threes feel exposed ("This makes us look incompetent"). The Fours feel unseen ("Nobody understands what we were going for"). Suddenly the room is thick with unspoken shame, and nobody is addressing the actual feedback.

Scenario: The client-facing team. A consulting team of Heart types excels at client relationships. Their proposals are beautifully crafted. Their presentations are polished. Clients feel genuinely cared for. But internally, the team is exhausted from performing. The Three team lead works seventy-hour weeks and calls it passion. The Two account manager has taken on half the admin tasks because "nobody else was going to do them." The Four strategist feels increasingly invisible because her ideas keep getting reshaped to fit what the client wants to hear rather than what they need to hear. The team looks flawless from the outside and is quietly falling apart on the inside.

Scenario: The feedback meeting that goes wrong. A Heart Center team has a quarterly review. The manager, trying to be constructive, says: "The last campaign underperformed. Let's figure out why." The Two hears: "You didn't do enough." The Three hears: "You failed." The Four hears: "Your vision was wrong." The manager meant none of those things, but each person's shame filter translated the same neutral sentence into a personal indictment. The next hour is spent managing emotions rather than solving the problem.

If your team skews Heart: Create explicit permission for direct feedback and make it safe to separate work quality from personal worth. Start feedback sessions with a grounding statement: "We are evaluating the work, not the people." Normalize imperfection. And watch for the team's tendency to prioritize how things look over how things actually are.

Head Center Teams (5, 6, 7)

Head Center teams are analytical and strategic. They think before they act, anticipate problems, and generate ideas. The shared emotional undercurrent is fear, though it manifests differently: Fives fear being overwhelmed and depleted, Sixes fear being without support or guidance, and Sevens fear being trapped in pain or limitation.

Scenario: The product team. Picture a product team with a Five lead engineer, a Six product manager, and a Seven design lead. The Five wants more data before committing to a direction. The Six wants to map out every risk scenario. The Seven wants to pivot to a more exciting approach. A month passes. The whiteboard is covered in frameworks. The Slack channel is full of "what ifs." Nothing has shipped. The shadow side: analysis paralysis. They can overthink, over-plan, and delay action while chasing certainty that never comes.

Scenario: The research department. A Head-heavy research team produces extraordinarily thorough reports. Every recommendation comes with data, caveats, and contingency plans. But the reports take twice as long as they should because the Five researcher keeps finding one more study to include, the Six project coordinator keeps adding risk scenarios to the appendix, and the Seven director keeps suggesting new angles that expand the scope. The work is excellent. The pace is glacial. Meanwhile, the Body types on the sales team are making promises to clients that the research team cannot deliver on time.

Scenario: The meeting that never ends. A Head Center team schedules a one-hour strategy session. Ninety minutes later, they are still debating the assumptions behind the assumptions. The Five has drawn a systems diagram on the whiteboard. The Six has listed twelve things that could go wrong. The Seven has proposed three alternative approaches, each more ambitious than the last. Nobody has written a single action item. The meeting ends with "let's think about this more and reconvene Thursday." Thursday's meeting goes the same way.

If your team skews Head: Set deadlines for decisions, reward action (not just analysis), and appoint someone (ideally a Body type) to call the question when the thinking has gone on long enough. Build a habit of ending every meeting with one concrete next step and a name attached to it. And watch for the team's tendency to substitute planning for doing.

Cross-Center Dynamics

Most real teams are not made up of a single center. The interesting dynamics happen when centers combine.

Body + Heart teams are powerful executors who care about people. They move fast and stay connected. The risk is that they act on emotion without adequate analysis. A team of Eights and Twos, for example, will charge into a new initiative with conviction and relational energy, but they may not have stress-tested the strategy. They need a Head perspective to say: "This feels right and looks right, but have we checked whether it is actually right?"

Heart + Head teams are thoughtful and empathetic. They understand both the human impact and the strategic implications of their decisions. The risk is paralysis of a different kind: they understand the problem so well that they cannot bring themselves to act, because every option has a downside that someone will feel. A team of Threes and Sixes will analyze the stakeholder landscape endlessly and still not launch. They need a Body perspective to say: "We have enough information. Let's move."

Body + Head teams are efficient and strategic. They think clearly and act decisively. The risk is that they leave people behind. A team of Ones and Fives will produce technically excellent work and wonder why nobody on the wider team feels invested in it. They need a Heart perspective to say: "The plan is solid, but we haven't brought people along. Who needs to feel included before we execute?"

Identifying Your Team's Dominant Center

You do not need everyone's exact type to map your team's center balance. Here are three quick diagnostic questions:

How does your team handle disagreement? If people argue openly and want to settle it now (Body). If people get quiet and process the emotional impact before responding (Heart). If people retreat to research, data, and "let me think about it" before engaging (Head).

What does your team do first when a new project arrives? If people immediately start assigning tasks and building timelines (Body). If people ask who the stakeholders are and how this will affect the team (Heart). If people ask for the background research and start mapping out risks (Head).

What does your team avoid? If your team avoids slowing down and reflecting (probably Body-dominant). If your team avoids direct, impersonal feedback (probably Heart-dominant). If your team avoids committing to action before they have certainty (probably Head-dominant).

Once you have a rough sense of your team's center balance, you can begin to intentionally compensate for the missing perspective. You do not need to hire for the missing center (though it helps). You just need to consciously include it in your process. The Missing Center Audit exercise gives you a structured way to do this.

Rebalancing in Practice

Knowing your team's center bias is the first step. Acting on it is what changes outcomes. Here are concrete moves for each imbalance:

If you are missing Body energy: End meetings with action items, not discussion points. Appoint a "first step" advocate who asks: "What is the one thing we can do before our next meeting?" Set shorter deadlines. Reward shipped work, even if imperfect.

If you are missing Heart energy: Start meetings with a two-minute check-in: "How is everyone doing, really?" Before making decisions that affect people, ask: "Who will this impact, and have we talked to them?" Create feedback rituals that explicitly separate the work from the person.

If you are missing Head energy: Before committing resources, ask: "What are we assuming, and what happens if we're wrong?" Build in a "pre-mortem" step where you imagine the project has failed and work backward to identify risks. Assign someone to play devil's advocate in planning meetings.

The goal is not to make every team perfectly balanced. It is to make your team's blind spots visible, so they stop being the thing that derails you without anyone understanding why.

Where to Go Next