Reading about the Enneagram is useful. Practicing it with the people you work with is transformative. These five exercises take the theory off the page and into the room where it matters, not as personality trivia, but as a shared language for how your team actually functions.
Each exercise below includes a concrete scenario, facilitation steps, common pitfalls, and a debrief section so you can run it with confidence, even if you are new to the Enneagram yourself.
These exercises work best when the team has shared context. Consider reading How Each Type Shows Up at Work together first.
Practice This
The Type-Sharing Exercise
The scenario. Picture a product team of eight people sitting around a conference table. Their manager, Derek, has just introduced the Enneagram at a previous meeting, and today he is asking each person to share one thing about how they work best and one thing about how they show up under stress. A Five named Priya says, "I do my best work when I have time to think before meetings. When I'm stressed, I go quiet and people assume I'm checked out, but I'm actually overwhelmed." Across the table, an Eight named Tomas says, "I need people to be direct with me. When I'm stressed, I get louder and more controlling, and I know that's hard for some of you." The room shifts. People are nodding. A Two named Keisha admits, "When I'm stressed, I start doing everyone else's work and then resent them for not noticing." Laughter, but also recognition. In fifteen minutes, this team has shared more honest information about how they function than they did in the previous six months of working together.
How to facilitate it. Allocate two minutes per person. Open with a simple prompt: "When I'm at my best at work, I need ___. When I'm stressed, I tend to ___." Make clear that knowing your exact type is not required. Anyone can answer those two questions honestly. Go around the table in order so nobody has to volunteer. The facilitator should go first to model vulnerability. After each person shares, the only response is a brief "thank you." No debates about typing. No "I think you're actually a..." responses. The goal is understanding, not accuracy.
Common pitfalls. The biggest risk is turning the exercise into a typing party, where people start diagnosing each other instead of listening. If someone says "I think I'm a Seven," resist the urge to quiz them. Another pitfall is people sharing too little because the room does not feel safe. If you sense guardedness, acknowledge it directly: "This might feel awkward. That's normal. You only need to share what feels comfortable." Finally, watch for the person who uses humor to deflect. A quick joke is fine, but if someone turns their entire share into a comedy routine, gently redirect: "That's funny, and also, what's the real answer?"
Debrief. After everyone has shared, ask the group: "What surprised you? What did you hear that changes how you want to work with someone?" Keep the debrief to five minutes. The value is not in analyzing what was said. It is in letting the information settle into the team's awareness. Close by asking each person to write down one thing they want to remember from someone else's share.
The Center Check-In
The scenario. A nonprofit leadership team is deciding whether to accept a major grant that comes with strings attached. The executive director, Vanessa, pauses before the vote and says, "Let's run this through the three centers before we decide." She writes three questions on the whiteboard: "What does our gut tell us?" (Body). "How will this affect people and relationships?" (Heart). "What are the risks and unknowns we haven't addressed?" (Head). The Body response comes quickly: "Our gut says take it. We need the money." The Heart response adds complexity: "If the donor's values conflict with ours, our staff will feel compromised. Two program directors have already expressed concern." The Head response reveals a gap: "We haven't read the fine print on the reporting requirements. It could consume 20% of a program manager's time." Without the three-center check, they would have taken the money and discovered the problems later.
How to facilitate it. Before a big decision, pause the discussion and write three questions on a whiteboard or shared document. Frame them in plain language: "What does our instinct say?" (Body). "How will this affect people?" (Heart). "What haven't we thought through?" (Head). Give the group two minutes of silent reflection, then go around the table for each question. Write the answers where everyone can see them. Even if your team does not have all three centers represented, this framework ensures you are considering action, feeling, and analysis. The missing perspective is almost always the one that would have prevented the next problem.
Common pitfalls. Teams often rush the Heart question because it feels "soft" compared to strategy and action. Push back on that instinct. Relational consequences are real consequences, and ignoring them creates problems that no amount of analysis can solve. Another pitfall is one center dominating the conversation. If your team is Head-heavy, the "risks and unknowns" answer will be detailed while the "gut instinct" answer gets a shrug. Name the imbalance: "We've spent ten minutes on analysis. Let's give the same attention to the gut check."
Debrief. After the decision, look back at the three answers. Which center's perspective most influenced the outcome? Which was easiest to ignore? Over time, tracking this pattern reveals your team's center bias more clearly than any personality assessment.
The Conflict Protocol
The scenario. Two designers, Marcus (an Eight) and Lena (a Four), are locked in a standoff over a product redesign. Marcus wants to ship a simpler version quickly. Lena wants to get the visual language right before anything goes live. Their manager, Aisha, asks each of them to answer three questions privately in writing before any further discussion: "What am I feeling right now?" "What do I actually need?" "What story am I telling myself about the other person?"
Marcus writes: "I'm frustrated. I need to feel like we're making progress. I'm telling myself that Lena cares more about aesthetics than about the users who are waiting for this fix." Lena writes: "I feel dismissed. I need to know that quality matters to this team. I'm telling myself that Marcus doesn't respect my expertise and just wants to check a box."
When they read each other's answers, the temperature drops immediately. Marcus did not know Lena felt dismissed. Lena did not know Marcus was anxious about user impact. The actual disagreement (scope and timeline) is still there, but the personal layer has been named and set aside. They reach a compromise in fifteen minutes.
How to facilitate it. When tension arises between two people, introduce the three questions and ask each person to write their answers privately. Give them five to ten minutes. Then ask each person to share their answers. The facilitator's job is to protect the process: no interrupting, no rebuttals, no defending. After both people have shared, ask: "Now that you've heard each other, what feels different?" Most conflicts dissolve, or at least transform, when people hear each other's honest answers. The story question is especially powerful: "I was telling myself you didn't respect my expertise" hits very differently from "You never listen to me."
Common pitfalls. Some people will resist writing. They will want to just talk it out. Insist on the writing step, because it forces reflection that verbal processing skips. Another pitfall is one person weaponizing their answers: "My story about you is that you're incompetent." If someone uses the exercise to attack, pause and reframe: "The goal is to share your experience, not to evaluate the other person." Watch for the person who writes what they think they should feel rather than what they actually feel. Encourage honesty by normalizing imperfect answers: "There are no wrong feelings here."
Debrief. After the conflict conversation, ask both people separately (not together) what they learned. Did the exercise change their understanding of the other person? Would they use this process again? Over time, teams that use this protocol regularly find that conflicts are shorter and less personal, because people learn to check their stories before they harden into grudges.
The Burnout Radar
The scenario. A consulting firm runs a monthly "energy check" every first Monday. Each person submits an anonymous number from 1 to 10 and one sentence about what would help. The numbers get plotted on a simple chart over time. In March, the team average is 7.2. By May, it has dropped to 5.1. No single person flagged a crisis, but the trend is unmistakable. The managing partner, Gloria, digs into the anonymous suggestions and finds a pattern: "Fewer late-night client calls" appears three times. "Clearer project handoffs" appears twice. She restructures the client call schedule and creates a handoff template. By July, the average is back to 6.8. The burnout was real, but it was structural, not personal. Without the radar, it would have surfaced as two resignations instead of a process fix.
How to facilitate it. Once a month, each team member privately rates their energy on a 1 to 10 scale and shares one thing that would help. No justification needed. No performance-review consequences. You can use a simple anonymous form or a shared spreadsheet where only the manager sees individual responses. Track the numbers over time. A steady decline from 7 to 5 to 3 is a signal that something structural needs to change, not just a person who needs a vacation. The one-sentence suggestion is the actionable part: it tells you what to do, not just that something is wrong.
Common pitfalls. The most common mistake is collecting the data and doing nothing with it. If you ask people to rate their energy and then nothing changes, you have taught them that honesty is pointless. Commit to acting on at least one suggestion per month, and tell the team what you changed and why. Another pitfall is managers treating low numbers as a personal failing: "Why are you at a 4? What's wrong with you?" The question is not "what's wrong with you." The question is "what's wrong with the conditions."
Debrief. Share the team's average (not individual scores) at the end of each quarter. Celebrate improvements. Name the interventions that worked. This builds trust in the system and makes people more honest in future rounds.
The Missing Center Audit
The scenario. A data science team of six people maps their center distribution during a quarterly planning meeting. The result: four Head types (two Fives, a Six, and a Seven), one Body type (a One), and no Heart types at all. Their manager, Raj, looks at the map and recognizes a pattern he could not name before. The team's technical work is brilliant, but they keep building features nobody asked for because they never check in with the users emotionally. They analyze what users do but rarely ask how users feel. Raj designates the Seven, who is the most socially energetic, as the "Heart advocate" for the quarter. Her job in key meetings is to ask two questions: "How will this affect the people using it?" and "Who haven't we talked to yet?" Within two months, the team's feature adoption rate improves because they are finally building for human beings, not data patterns.
How to facilitate it. Once a quarter, map your team by center. You do not need exact types. Just note whether each person tends to lead with Body (action, instinct), Heart (relationships, image), or Head (analysis, strategy). You can do this collaboratively or have people self-identify. Look at the balance. If a center is underrepresented, designate someone (rotating) to "hold" that perspective in key meetings. A Head-heavy team appoints a Heart advocate who asks: "How will this affect morale? Who haven't we consulted?" A Heart-heavy team appoints a Body advocate who asks: "What's the first concrete step? When do we start?" A Body-heavy team appoints a Head advocate who asks: "Have we thought through the risks? What data are we missing?"
Common pitfalls. Teams sometimes treat the audit as a labeling exercise and stop there. Knowing your center balance is useless unless you act on it. The advocate role must be real, not ceremonial. Give the advocate explicit permission to interrupt discussions and redirect attention to the missing center's perspective. Another pitfall is people feeling reduced to their center. Remind the team that center is a tendency, not a cage. A Five can hold the Heart perspective thoughtfully. A Two can ask the hard analytical questions. The audit reveals the team's default pattern, not each person's limit.
Debrief. At the end of each quarter, review how the advocate role went. Did the missing perspective change any decisions? What was hardest about holding a center that is not your default? Rotate the role so the same person does not carry it indefinitely. Over time, the team internalizes the three-center check and the formal advocate role becomes less necessary.
Where to Go Next
- Explore the type pages to understand each person's core motivations more deeply
- Read about team dynamics by center to understand why these exercises matter
- See growth practices for individual development that supports team health
- Learn about relationships to apply these insights beyond the workplace
- Back to the Workplace hub