Quick answer: Enneagram workplace friction means tracing triggers, rather than assigning labels
This article uses Enneagram motivation hypotheses to frame self-observation questions about feedback, deadlines, misaligned OKRs/KPIs, and pressure on boundaries. Fictional scenarios illustrate communication strategies that can be observed in each example; the type–TKI pairings are not validated mappings or evidence that a type causes a behavior. It does not determine who has a problem or predict performance, promotion, or job fit. A safer approach is to record “trigger → what I want to protect → the conflict strategy I used → a different communication experiment to try next time.”
Take three steps: first, write down the specific situation without saying “I am this personality type.” Second, treat motivations as questions to check: am I protecting standards, relationships, value, security, freedom, control, or peace? Third, use the Thomas–Kilmann Conflict Mode Instrument (TKI) strategies of competing, collaborating, compromising, avoiding, and accommodating to observe whether you repeatedly use the same ineffective behavior under pressure.
What the Enneagram means in the workplace
Workplace use of the Enneagram is a non-diagnostic self-observation framework. The Enneagram tradition offers language for reflecting on motivations around feedback, meetings, deadlines, and role boundaries. It does not establish the cause of a particular workplace behavior. It cannot serve as a tool for hiring, performance assessment, promotion, psychological diagnosis, or career fit. Its appropriate use is to break vague internal friction into observable behavioral clues.
In plain language, the Enneagram is not a reason to say in a retrospective, “He is assertive because he is Type 8.” It can prompt questions about recurring behavior in a particular situation: immediately looking for flaws in a retrospective, explaining yourself defensively when asked about progress, holding back delivery after requirements change, or seeking excessive verbal confirmation when a manager's request is unclear.
If you do not yet have a type result, you can take the Enneagram personality test, then return to compare workplace situations. The result is a starting point for observation, not a verdict on your identity.
Core motivations: What you are protecting, rather than who you are
Within Enneagram theory, core motivations describe concerns a person might be protecting. They are interpretations to investigate, not needs established by a type score. At work, possible clues include small actions: chasing revisions, remaining silent, shifting blame, gathering more evidence, taking control, coordinating endlessly, repeatedly seeking confirmation, avoiding conflict, or suddenly posting a long explanation in a group chat.
For the wider motivation framework, start with the Enneagram overview. Before applying a result at work, read about Enneagram results and their limits.
The fictional situations below explore these possibilities: ambitious OKRs with limited resources; middle managers who must report upward while pushing deadlines downward; graduates afraid that asking questions will make them look unprofessional; people changing careers at thirty who fear exposing gaps in their skills; and retrospectives that appear factual but judge responsibility in every sentence.
Instead of asking “What number am I?”, ask:
What am I most afraid will get out of control in this situation? How am I protecting myself? Does that protective behavior make the task clearer, or make collaboration more strained?
Table 1: Fictional workplace scenarios: Motivation hypotheses, observable TKI modes, and small actions
The Enneagram workplace friction map puts type hypotheses, core motivations, Thomas–Kilmann conflict strategies (TKI), and actual work behaviors in one table. These pairings are fictional discussion examples, rather than research-established mappings from Enneagram types to TKI modes or TKI test results. One person can use all five conflict modes. Its purpose is not to classify colleagues, but to help you examine a possible recurring pattern during feedback, meetings, boundary disputes, and deadlines.
| Type hypothesis | Need to explore | Example friction | Example TKI mode | Observed action | Safer experiment |
|---|---|---|---|---|---|
| Type 1 | Protect standards, avoid mistakes, and maintain understandable order | Correcting every quality gap in a retrospective can make others defensive | Possible competing if the person prioritizes their own quality demands at the expense of others’ concerns. The number of edits alone is insufficient. | Marking more than a dozen problems in a PRD, contract, code review, or deliverable without identifying priorities | Separate feedback into “must fix before launch / improve next release / personal preference” before speaking |
| Type 2 | Protect relationships, feel needed, and avoid appearing uncaring | Taking on too many urgent requests and privately keeping score | Possible accommodating if the person yields their own concerns to meet the other person’s needs. Later resentment does not establish the mode. | Saying “Don't worry, I'll do it,” then hinting in a weekly report at extensive invisible work | State boundaries before helping: “I can handle A through B, but cannot take over C long term” |
| Type 3 | Protect value, results, and visible performance | Overpackaging progress when OKRs/KPIs are misaligned, fearing disclosure of obstacles | Presenting progress selectively does not establish a TKI mode; check whose concerns are addressed and how trade-offs are made | Reporting highlights before completing a project, while describing risks as “in progress” | Report four categories: “completed / obstacles / decisions needed / next milestone” |
| Type 4 | Protect authenticity, personal meaning, and distinctive expression | Strong resistance to standardized processes, assembly-line content, and meaningless meetings | The quoted judgment alone does not establish a mode; check whether the person withdraws from the disagreement or pursues a preferred outcome at others' expense. | Saying “This has no soul” in a requirements meeting without offering an actionable alternative | Suggest one practical change first, then explain the real problem it solves |
| Type 5 | Protect thinking space, information control, and energy boundaries | Becoming silent or delaying delivery when pulled into last-minute meetings or asked for instant conclusions | Possible avoiding if the disagreement is left unaddressed; necessary research alone does not establish avoidance. | Not responding to unstructured changes in business metrics while researching privately, leading a counterpart to assume non-cooperation | Give a 60% version: “I can confirm A now; I need two hours to reach a conclusion on B” |
| Type 6 | Protect security, responsibility boundaries, and trustworthy evidence | Excessive confirmation when leaders repeatedly change direction or responsibilities are unclear | Agreeing initially, then asking for clear responsibility conditions: these actions alone do not establish a TKI mode | Seeking excessive verbal confirmation from executives, deadlocking interface refactoring because nobody dares proceed | Separate questions into “requires written confirmation / can verify while working / acceptable risk” |
| Type 7 | Protect possibilities and freedom, and escape boredom | Turning to new ideas when projects reach completion and repetitive execution | Possible avoiding if proposing new work sidesteps the disagreement about existing commitments; changing tasks alone does not establish a mode. | Proposing three new growth experiments before closing old project bugs, diluting team attention | Before starting each idea, define the minimum action needed to finish the current version |
| Type 8 | Protect control, autonomy, and directness | Intense impatience with indirect communication, blame-shifting, and slow decisions | Competing if the person pursues their preferred decision at others' expense; intensity alone does not establish the mode. | Making decisions, interrupting explanations, and demanding immediate responsibility assignments in meetings, discouraging junior members from raising risks | Ask “Who has final decision authority?” before stating your limits and negotiable points |
| Type 9 | Protect peace, stability, and a low-conflict environment | Remaining silent under forceful demands or competing pressures, then expressing opposition through delay | Accommodating if genuine concerns are yielded to meet others' concerns; avoiding if the disagreement itself is left unaddressed. | Agreeing in a retrospective but not actively advancing execution until risks become reality | Write down one disagreement you must express before the meeting, and state it in the first 10 minutes |
Usage rule: Choose a row that resembles what actually happened, rather than choosing a strategy from a type label. The same person may use a different mode in another situation. Instead of “Our whole team is Type 6,” try: “When asked for an update without warning, I left the message unanswered and didn’t say when I would respond, avoiding the discussion for now. Next time, I will give a 60% usable answer and agree on when to fill the gaps.”
Communication conflict: Bring TKI and principled negotiation into daily collaboration
Communication conflict arises when people see their goals, needs or boundaries as incompatible. TKI names five strategies: competing, collaborating, compromising, avoiding, and accommodating. Harvard principled negotiation emphasizes separating people from problems, focusing on interests instead of positions, creating options, and using objective criteria. Here, motivation hypotheses prompt questions to check against specific words, actions, and circumstances. A type label does not establish which mode someone used or what caused the behavior.
Choose a mode by the conflict, not the type number
The TKI authors' overview distinguishes concern for your own needs from concern for the other person's needs. Its five modes describe different ways of handling those concerns:
| Mode | What happens to the two concerns? | Original example: a disputed release |
|---|---|---|
| Competing | You pursue your concern at the other's expense | An authorized lead stops a release with a confirmed serious defect despite a request to ship today. |
| Accommodating | You yield your concern to meet the other's | You accept a colleague's workable presentation preference when your alternative is unimportant to you. |
| Avoiding | Neither concern is pursued in this discussion | You postpone the dispute until the missing evidence is available, naming when and with whom to resume. |
| Compromising | Each concern is partly met through concessions | Both sides accept a narrower first release and a later date for the remainder. Neither receives the original plan in full. |
| Collaborating | You investigate a way to satisfy both concerns | You investigate whether the needed function can be delivered on time without the defective component, preserving the required standard and the actual deadline. |
These are teaching examples, not TKI results or predictions about Enneagram groups. Collaboration is an attempt, not proof that a solution exists. If removing the defective component also removes the required function, that option does not meet both concerns. Compromise is different: the parties knowingly accept partial satisfaction. A serious safety or mandatory requirement cannot simply be traded away to split the difference.
Neither forceful action nor postponement is automatically wrong. Ask what must be protected now, who can decide, what evidence is missing and whether there is time for joint problem-solving. A pause without a return arrangement may leave the issue unattended. A prolonged discussion can also be unsuitable when an authorized person must contain an immediate problem. No mode guarantees agreement.
Worked example: one more check before release
This is an original fictional conversation, not a report of a client or participant outcome. Sam asks to recheck a customer handover; Jordan wants to send it before the agreed deadline.
Jordan: “You keep asking for another review. What specifically could stop the customer using this?”
Sam: “The handover says the customer can download the file. We have only checked it with our own account.”
Jordan: “Then the open question is access, not whether we trust the whole document. Who can check the customer's permitted access before the deadline?”
They ask the responsible account owner to verify the condition. Suppose the customer does lack access. That is a real obstacle requiring a correction; describing Sam as anxious or perfectionistic would not remove it. If the check instead confirms that access works, Sam's original concern has an answer. A new request to review every sentence needs its own reason rather than inheriting the access issue's urgency.
Sam's repeated checking might reflect a concern about standards, fear of blame, an assigned responsibility, or knowledge of a genuine defect. The behavior alone cannot identify the motive. Ask, “What evidence would let you proceed?” If the relevant condition is met but the concern persists, explore what remains rather than announcing a type explanation.
Jordan: “Access is now confirmed. You also want to change the wording. Is it preventing the agreed use, or is it a preference we can discuss afterward?”
Sam: “The wording is usable. I'd prefer a different layout, but it needn't delay sending.”
In this fictional branch, Sam accommodates a low-stakes preference after the essential condition is met. Jordan still checks that the authorized customer receives the correct file and can use it. A calmer conversation, a sent email and successful customer access are separate observations. If access remains unresolved, keep the obstacle visible and obtain a realistic delivery decision; do not record the release as complete just because the discussion ended.
Feedback: “Don't be so sensitive” does not resolve negative feedback
A feedback-and-defensiveness cycle can develop when a problem is heard as personal rejection and the response leaves the task unresolved. The Enneagram can prompt you to ask whether you are protecting standards, value, relationships, security, or control.
An actionable structure:
- State the facts: which page, paragraph, or metric falls short;
- State the impact: launch, customers, costs, compliance, or collaboration;
- State the request: what changes now, who confirms it, and when it will be completed.
Say less of: “You're doing it again.”
Say more of: “We are discussing the deliverable's facts, not judging you personally. Let's first agree on the three changes that must be made.”
Meetings: Retrospectives easily turn problems into judgments about people
In a retrospective, unclear roles or concern about responsibility may be relevant explanations for blame-shifting; neither can be inferred from a type. Some rush to prove it was not their fault; others rush to prove they warned everyone; others suppress key problems to preserve harmony. The most useful step is to distinguish facts, explanations, and responsibility, rather than ask about type numbers.
Use three columns:
| Retrospective material | How to write it | What to avoid |
|---|---|---|
| Facts | Requirements changed on June 12, adding 3 interface fields | Product changed requirements at the last minute again |
| Impact | Backend integration was delayed by 2 days, reducing the testing window | Engineering slowed down the project |
| Next step | Changes must enter the requirements freeze list; unfrozen requirements cannot enter development | Everyone should be more careful next time |
Boundaries: Make an unspoken limit discussable
Boundary defense is a self-protective response to persistent intrusion into workload, responsibilities, emotional labor, or response time. It may appear as cold treatment, passive aggression, delay, sudden outbursts, or outward agreement accompanied by private judgments.
A safer boundary statement:
“I can help with the first version, but cannot take on this module long term. If I am to remain responsible, we need to reprioritize and specify which of my current tasks it replaces.”
This states a capacity limit and asks for a decision. It cannot guarantee agreement or remove the resource gap.
Continue the boundary conversation when the first answer is no
In this original fictional example, Casey has agreed to finish a client summary by Friday. A colleague asks Casey to take over a second report as well. Casey wants to help and initially says yes, then realizes both cannot be completed in the available time.
Casey: “I agreed too quickly. I can finish the summary by Friday, or do the second report then and move the summary to Monday. I cannot promise both. Which outcome is needed most, and who can approve changing the existing commitment?”
Colleague: “Both are important. Please just fit them in.”
Casey: “Their importance isn't in dispute. The available time is. We need the person responsible for these commitments to choose a later date, reduce the agreed work, or assign someone with capacity. Until that is decided, I can continue the summary, but the second report has no confirmed delivery arrangement.”
Casey names the earlier overcommitment without deciding that the colleague is exploitative or that Casey is a particular type. Wanting appreciation, avoiding disagreement, misunderstanding the task and underestimating its length are different possible explanations. A clear correction is useful under any of them.
Suppose the responsible manager chooses a shorter second report, assigns its remaining sections to someone who explicitly accepts them, and preserves the first deadline. Casey confirms the sections, dates and recipients in writing. At the next agreed review, the team checks what was actually delivered and what help was still needed. This branch illustrates a negotiated trade-off, not a proven improvement in personality or team performance.
If nobody can take the remaining sections, there is no complete arrangement yet. A colleague's willingness to help does not establish capacity, and a message naming a new owner does not establish acceptance. Report the unresolved portion and ask for a feasible decision rather than silently restoring the impossible promise. When direct disagreement may lead to retaliation, use suitable confidential support or established workplace channels; this script is not a requirement to confront someone regardless of safety.
Deadlines: Check your response before calling it a pattern
Under a deadline, look for what you actually do rather than inferring a stress response from your type: taking over a task, staying late, repeatedly seeking confirmation, missing agreed check-ins, or proposing a new direction during final checks. Ask what mattered to you separately and check the task facts before deciding what needs action.
When a project enters its final 72 hours, ask:
- What do I most want to protect now: standards, relationships, value, security, freedom, control, or peace?
- Which TKI strategy am I using: competing, collaborating, compromising, avoiding, or accommodating?
- Does this strategy make the project clearer, or simply make me feel more comfortable?
Table 2: Stress responses and communication experiments checklist
This checklist connects physical sensations, cognitive friction, and the next experiment. It does not diagnose psychological states or prove a particular type. It asks one small question: can this friction become a more ethical, lower-risk behavioral experiment?
| Signal | What you might feel | Conclusion to avoid rushing into | Principled negotiation boundary | One next action |
|---|---|---|---|---|
| Repeated fault-finding | Something will go wrong unless I identify every problem | I am difficult / they are unprofessional | Separate people from the problem | Sort issues into “must fix / can wait / personal preference” |
| Excessive agreement | Refusing will damage relationships or make me look uncooperative | I can only endure this / they are deliberately exploiting me | Focus on real interests: delivery, boundaries, priorities | State “I can take A, but not B unless priorities change” |
| Defensive reporting | Obstacles will be seen as incompetence | I must prove I have kept making progress | Use objective criteria: goals, metrics, risks | Replace self-packaging with “completed / risks / decisions needed” |
| Emotional withdrawal | Explaining more is pointless; I might as well give up | This team is not worth it / I am unsuited to work | Raise the problem before judging people | Write down one specific fact, then decide whether to communicate |
| Information hoarding | I cannot speak before understanding everything | I must prepare to 100% | Create multiple options | Provide a 60% conclusion first, marking variables still to confirm |
| Repeated confirmation | I will be blamed if the direction changes | The manager cannot be trusted / the project will collapse | Replace verbal reassurance with verifiable criteria | Identify the questions that genuinely need written confirmation; agree which decisions can proceed without it. |
| Escaping completion | This project is boring; better start a new direction | I cannot execute / this project has no value | Address the current problem before generating options | Define a minimum completion standard and meet it before starting something new |
| Forceful advancement | Others are too slow; I must take over | Only I am reliable | Clarify decision authority and responsibility boundaries | Confirm the owner first, then state limits and negotiable points |
| Silent delay | Speaking up will spoil the atmosphere | My opinion does not matter | Reframe positions as interests | Write one risk you must raise before the meeting and state it within the first 10 minutes |
Chinese workplace situations: Four common friction chains
The four fictional examples use “trigger—response—interaction—task consequence” to organize observations. They illustrate possible situations, not findings about Chinese workers or people of a specified age. Consider resources and role expectations alongside any motivation hypothesis.
1. Misaligned OKRs/KPIs: Ambitious goals, limited resources
Suppose a goal says “quarterly growth of 80%” while staffing, budgets, and authority remain unchanged. In this fictional example, possible responses include: competing for visible achievements, repeatedly confirming direction, quietly lowering standards, or disguising blame-shifting as “coordination.”
Observation question: Am I solving the goal problem, or protecting myself from blame?
2. Hidden opposition between graduates and middle managers
In this example, a new graduate worries that asking a question will look unprofessional, while a manager keeps requesting progress without checking the missing information. The graduate leaves a required question unasked and delivery stalls. This is one possible chain, not a general account of graduates or managers. A missing instruction may explain the delay without a personality explanation.
Observation question: Have I disguised “missing information” as an “attitude problem”?
3. Mutual blame-shifting in retrospectives
Suppose a retrospective contains conflicting recollections about who accepted a change. Establish the request, response and decision first. Standards, value, security or peace are possible concerns to ask about, not proven motives. Resolving the disagreement requires facts and an agreed account of responsibility.
Observation question: Does this statement add facts, or add defensiveness?
4. Psychological safety boundaries when changing careers at thirty
Consider a fictional career changer around thirty who interprets a correction as evidence that starting again was a mistake. Ask what the task required and whether training was available. Someone of any age may need that clarification; age and a type label do not establish the interpretation or its cause.
Observation question: Am I learning a new task, or proving that I am still valuable?
A 7-day observation checklist: Record workplace friction without judging personality
This optional seven-day structure organizes behavior observations; it does not verify a type or prove that an exercise works. Adjust the period to naturally occurring events. No suitable opportunity is an observation, not a failure: do not manufacture conflict to fill the table.
| Day | Recording task | What to write |
|---|---|---|
| Day 1 | Trigger | Who said what? Which action immediately made me tense, angry, eager to explain, or eager to withdraw? |
| Day 2 | Core protection | What do I most want to preserve: standards, relationships, value, space, security, freedom, control, or peace? |
| Day 3 | Conflict strategy | Am I competing, collaborating, compromising, avoiding, or accommodating? |
| Day 4 | Cost | What became clearer or harder for the task, relationship, or boundary? What stayed unchanged? |
| Day 5 | Alternative wording | How can I be more specific and less defensive next time? |
| Day 6 | Small experiment | Try the alternative wording once in a low-risk situation. |
| Day 7 | Retrospective | What actually happened? Was a decision reached and carried out? What other explanation remains possible? |
For a completed observation, separate action from interpretation. A fictional record might say: “I corrected my earlier promise, the manager reduced the second report, and the summary arrived on Friday. I still do not know whether wanting approval caused my first answer. A request that looked brief may have misled me.” In the unresolved branch, write “priority not decided; second report unassigned,” rather than counting polite conversation as a successful handover. Keep the actual cost and any contrary observation, including occasions when you accepted extra work that really did fit.
What the Enneagram can and cannot tell you
Workplace Enneagram interpretation can only provide language for observation: core motivations, stress triggers, communication tendencies, boundary patterns, and wording to try. It cannot tell you “which job suits you,” prove “who has stronger leadership ability,” screen job candidates, or predict performance, promotion, income, resignation, or career success.
A safer approach:
- For yourself: identify default defensive behaviors under pressure;
- For colleagues: use fewer labels and ask about concrete situations;
- For teams: establish shared language for feedback, boundaries, and responsibility;
- For management: do not use types to allocate opportunities or eliminate people.
You can use this toolkit without taking another test. If you already have results, keep them as questions for reflection while checking the actual situation. Use the Enneagram results guide when the difficulty is interpreting the profile itself.
Frequently asked questions
Can the Enneagram explain workplace friction?
It can prompt reflection. It cannot determine the cause of a particular incident. Workplace friction may also arise from unclear goals, insufficient resources, ineffective management, ambiguous roles, misaligned incentives, and organizational culture. The Enneagram is better suited to examining what you want to protect under pressure and which communication behaviors you repeat.
Can the Enneagram determine which job suits me?
No. It cannot assess job fit, performance, promotion, income, or career success. A safer approach is to turn results into questions: Which environments trigger me? What feedback can I accept? Am I willing to perform this role's core tasks over the long term?
Why does the same Enneagram type behave differently in different companies?
A shared type label does not establish shared behavior. Check actual expectations, resources, relationships and decision authority in each setting. Someone may delay one task because information is missing and another because they are reluctant to disagree; the same visible delay does not settle its cause.
How should I consider Enneagram results alongside stress responses?
Start with more than the type name. Put results into a real situation: What triggered me? What do I most want to protect? Did I compete, avoid, accommodate, compromise, or collaborate? Did that response clarify the task or strain relationships?
Can the Enneagram be used for team management or hiring?
It is not recommended for hiring screening, elimination, performance judgments, promotion judgments, or proof of job fit. Teams may use it as voluntary language for reflecting on communication, but should not force employees into types or use types to justify management penalties or allocation of opportunities.
Reference and example boundaries
- A TKI co-author’s introduction to the five conflict modes: https://kilmanndiagnostics.com/a-brief-overview-tki/
- Enneagram Institute: how the system works. This is a source for the tradition's interpretation of types and motivations, not evidence that a type explains a particular person's behavior.
- Hook and colleagues (2021), systematic review. The published abstract reports mixed reliability and validity evidence across 104 independent samples. It does not validate FermatMind's questionnaires, the type–mode pairings or this article's original exercises.
The TKI overview supports the names and situational use of the five conflict modes, rather than validating mappings from Enneagram types to those modes. The seven-day schedule, 60% version, and table scenarios are adjustable practice examples, rather than measurement standards or guarantees of results.
