Using the Enneagram With a Team: Motivation, Stress, and Working Agreements
Short answer
On a team, the Enneagram can help people name what they need to do their best work: clarity, recognition, autonomy, time to think, or room to explore. It works best as an optional conversation that ends in practical working agreements. It should never be used to assign roles or judge people, and psychological safety matters more than type.
What the Enneagram adds to teamwork
Teams usually talk about tasks, deadlines, and skills. They rarely talk about why people react so differently to the same plan. A sudden change in priorities might excite one person, worry another, and annoy a third. Enneagram tradition offers one way to make those reactions discussable by linking them to motives: a need for order, connection, achievement, meaning, competence, security, freedom, control, or peace.
The value is not in labeling people. It is in prompting each person to describe what helps them contribute, and then turning that into shared habits.
Start with psychological safety
Before any personality conversation, a team needs enough trust that people can speak honestly without fear of embarrassment or punishment. Research by Edmondson (1999), studying 51 work teams in a manufacturing company, found that this shared belief, called team psychological safety, was associated with more learning behavior, such as asking for help and discussing errors, which in turn was associated with team performance.
In practice, that means a type session should never be the first time a team talks openly, and it should never feel like an evaluation.
What each center may need from a team
| Center | Types | Often values | May need from the team |
|---|---|---|---|
| Gut | 8, 9, 1 | Autonomy, fairness, and a stable way of working | Clear ownership, fair process, and room to push back |
| Heart | 2, 3, 4 | Recognition, connection, and meaningful work | Acknowledgment, honest feedback, and a sense of purpose |
| Head | 5, 6, 7 | Information, security, and possibilities | Context, early notice of change, and room to explore |
Common team frictions and how to discuss them
Speed versus thoroughness
Some people want to decide quickly and adjust later; others want to understand the risks first. In tradition, Threes, Sevens, and Eights may lean toward speed, while Ones, Fives, and Sixes may lean toward thoroughness. A useful agreement is to label decisions as reversible or not, and to slow down only for the second kind.
Direct versus diplomatic feedback
Some people want feedback blunt and immediate; others need it private and framed with care. Eights may prefer bluntness, while Twos, Fours, and Nines may need more care. The team can agree on a default and allow each person to state their preference.
Structure versus flexibility
Some people feel safer with clear processes; others feel boxed in. Ones and Sixes may value structure, while Sevens and some Fours may resist it. A team can define a few must-follow processes and leave the rest open.
Visible credit versus quiet contribution
Some people are motivated by recognition; others find public praise uncomfortable. A short check on how each person likes to be recognized can prevent awkwardness and resentment.
A simple team exercise
- Each person privately reflects on what helps them do their best work and what gets in the way. Type is optional.
- In pairs, people share only what they choose.
- As a group, list the needs that came up without attaching names or types.
- Agree on three working agreements, such as how decisions are flagged, how feedback is given, and how changes are announced.
- Review those agreements in a month and adjust.
Running a one-hour session
If your team wants to try a structured conversation, a simple format works better than a long workshop.
- Ten minutes: set ground rules. Participation is voluntary, nothing shared leaves the room, and type is optional.
- Fifteen minutes: individual reflection on three prompts: what energizes me, what drains me, and what I do under pressure.
- Fifteen minutes: pairs share whatever they choose, then each pair names one theme without attributing it to a person.
- Fifteen minutes: the group drafts two or three working agreements based on the themes.
- Five minutes: pick a date to review the agreements.
Remote and hybrid teams
Distance amplifies differences in motivation. People who need context may feel left out of hallway decisions; people who need recognition may feel invisible on a screen; people who need quiet time may welcome remote work but drift out of touch. A few habits help across types: write decisions down where everyone can see them, announce changes before they take effect, make it normal to ask for a quick call, and give credit in public channels when the person is comfortable with it.
When type talk turns into teasing
Jokes like classic Seven or there goes the One again can feel friendly, but they often stick to a person and narrow how others see them. If you lead a team, model curiosity instead: ask what was going on for you there rather than naming a type. If teasing continues, it is fair to set a norm that the team talks about needs and habits, not labels.
Pitfalls
- Assuming a person's type from their behavior and treating it as fact.
- Making type part of performance discussions.
- Using types to explain away conflict instead of addressing it.
- Leaving out people who do not want to share or who reject the framework.
- Forgetting that skills, workload, and resources often matter more than personality.
Reflection for team members
Frequently asked questions
Should a team share Enneagram results?
Only if each person chooses to. Results belong to the individual, and opting out should carry no consequences.
Can type help assign roles?
No. Roles should depend on skills, interests, and development goals. Assigning by type risks stereotyping and unfairness.
What if a team member dislikes the Enneagram?
Respect that. Focus on shared working agreements, which anyone can contribute to without using type language.
Is there research on Enneagram teams?
Very little. Research on psychological safety, such as Edmondson (1999), is more established and applies regardless of type.
How often should a team revisit this?
Revisit working agreements every month or two, especially after changes in membership or workload.
Sources
- Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. doi:10.2307/2666999
- Hook, J. N., Hall, T. W., Davis, D. E., Van Tongeren, D. R., & Conner, M. (2021). The Enneagram: A systematic review of the literature and directions for future research. Journal of Clinical Psychology, 77(4), 865-883. doi:10.1002/jclp.23097