"Why does that person never speak up in meetings?" "Why did they get upset when I gave them feedback?" "Why do they jump straight into coding without making a plan?"
If you have ever had these questions at work, MBTI might help. MBTI is not a perfect tool, but it is useful as a starting point for understanding that people have different thinking patterns and behavioral styles. This article covers how to practically apply MBTI in the workplace.
| Category | Extraversion (E) | Introversion (I) |
|---|
| Energy Source | Social interaction | Alone time |
| Meeting Style | Speaks ideas on the spot | Thinks thoroughly before speaking |
| Work Preference | Collaboration, brainstorming | Focused work, independent tasks |
| Communication | Organizes thoughts by talking | Organizes thoughts by writing |
| Easily Misunderstood As | Lacking depth | Low engagement |
| Category | Sensing (S) | Intuition (N) |
|---|
| Focus | Present, facts, details | Future, possibilities, big picture |
| Work Style | Step-by-step execution, follows manuals | Pattern recognition, creative approaches |
| Report Style | Specific numbers and facts | Vision and strategy |
| Problem Solving | Prefers proven methods | Tries new approaches |
| Easily Misunderstood As | Lacking innovation | Unrealistic |
| Category | Thinking (T) | Feeling (F) |
|---|
| Decision Making | Logic, efficiency, fairness | People, relationships, harmony |
| Feedback Style | Direct, improvement-focused | Positives first, gentle delivery |
| In Conflict | Focuses on problem solving | Addresses emotions first |
| Praise Style | Focuses on results and outcomes | Focuses on effort and process |
| Easily Misunderstood As | Cold and insensitive | Illogical |
| Category | Judging (J) | Perceiving (P) |
|---|
| Planning | Plans ahead, follows schedules | Flexible, adaptive |
| Projects | Strict deadlines, systematic | Explosive focus near deadlines |
| Decision Making | Decides quickly and acts | Gathers more info before deciding |
| Handling Change | Gets stressed | Accepts naturally |
| Easily Misunderstood As | Inflexible | Unplanned |
| Type | Nickname | IT Org Prevalence (est.) | Characteristics |
|---|
| INTJ | Architect | High | System architecture, long-term tech strategy |
| INTP | Logician | High | Algorithms, complex problem solving |
| ISTJ | Inspector | Medium | Stable operations, documentation, QA |
| ISTP | Craftsman | Medium | Debugging, DevOps, troubleshooting |
| ENTJ | Commander | Medium | Tech lead, project management |
| ENTP | Debater | Medium | New tech exploration, prototyping |
| Type | Nickname | Common Roles |
|---|
| ENFJ | Protagonist | PM, Team Lead |
| ESFJ | Consul | HR, Internal Communications |
| ESTJ | Executive | Project Manager, QA Lead |
| ENFP | Campaigner | UX Designer, Marketing |
| Type | Work Strengths | Work Weaknesses | Stress Triggers |
|---|
| INTJ | Long-term strategy, system design, independent problem solving | Team emotion management, details | Inefficiency, incompetent processes |
| INTP | Complex analysis, theoretical exploration, creative solutions | Deadline management, repetitive tasks | Illogical decisions, forced rules |
| ENTJ | Leadership, strategy execution, organizational management | Team member empathy, patience | Slow progress, no planning |
| ENTP | Innovation, idea generation, debate | Follow-through, details, routine | Repetition, rigid rules |
| Type | Work Strengths | Work Weaknesses | Stress Triggers |
|---|
| ISTJ | Accuracy, documentation, process compliance | Adapting to change, creative thinking | Uncertainty, rule-breaking |
| ISFJ | Thoroughness, team support, stable execution | Leading change, handling conflict | Sudden changes, lack of recognition |
| ESTJ | Project management, maximizing efficiency | Flexibility, understanding emotions | Inefficiency, missed deadlines |
| ESFJ | Team harmony, communication, consideration | Accepting criticism, adapting to change | Conflict, impersonal treatment |
| Type | Work Strengths | Work Weaknesses | Stress Triggers |
|---|
| INFJ | Vision casting, understanding people, writing | Conflict avoidance, perfectionism | Value conflicts, superficial work |
| INFP | Creativity, empathy, value-based work | Deadline management, confronting conflict | Injustice, personal values ignored |
| ENFJ | Team leading, motivation, sharing vision | Objective criticism, self-care | Team discord, indifference |
| ENFP | Innovation, inspiration, networking | Focus, follow-through, routine | Constraints, repetition, micromanagement |
| Type | Work Strengths | Work Weaknesses | Stress Triggers |
|---|
| ISTP | Problem diagnosis, crisis response, practical solutions | Long-term planning, emotional expression | Unnecessary rules, theoretical discussions |
| ISFP | Design sense, team harmony, flexibility | Deadline management, confronting conflict | Pressure, impersonal environment |
| ESTP | Action-oriented, negotiation, crisis management | Long-term planning, detail management | Boredom, slow progress |
| ESFP | Energy, team atmosphere, presentations | Solo focus, data analysis | Isolation, strict rules |
O Effective approach:
"This code has O(n^2) time complexity. Using a HashMap could reduce it
to O(n). Here are the benchmark results."
X Ineffective approach:
"This code seems kind of slow... Could you maybe make it
a bit faster? Pretty please~"
Key principles:
- Present objective data and logical reasoning
- Minimize emotional expressions
- Suggest specific improvement directions
- Focus on the problem, not personal attacks
O Effective approach:
"You really worked hard on this feature. The UI part is especially clean.
One suggestion -- if we strengthen the error handling,
it could be even more polished. Shall we look at it together?"
X Ineffective approach:
"There's no error handling. In production, this will cause
outages. Redo it."
Key principles:
- Acknowledge effort and strengths first
- Use "let's" and "together" language
- Frame suggestions as possibilities
- Have the conversation privately (avoid public criticism)
O Effective approach:
"The deadline for this task is March 15. Here are the priorities,
and please share progress updates at Monday standups.
The detailed requirements document is attached."
X Ineffective approach:
"I'm not sure when this needs to be done,
but it would be nice if you could just do it. Figure it out."
O Effective approach:
"The core goal of this feature is this. Feel free to choose
your approach. However, it must be completed by March 15.
If you hit any blockers, let's discuss anytime."
X Ineffective approach:
"Follow this procedure step by step, and report your progress daily.
You must proceed in the order A -> B -> C -> D."
Scenario: In a code review, a T-type bluntly points out issues and an F-type gets hurt
| Role | Approach |
|---|
| T-type | Mention positives before criticism. "Good approach. I think changing this would make it even better." |
| F-type | Separate emotions from content. "They are talking about the code, not about me." |
| Leader | Establish code review guidelines. Standardize feedback format (e.g., "I like / I wish / What if" framework) |
Scenario: During a sprint, a P-type wants to add an unplanned feature and a J-type opposes it
| Role | Approach |
|---|
| J-type | Acknowledge that not all changes are bad. Use a change request process to decide |
| P-type | Acknowledge the importance of sprint commitments. Record new ideas in the backlog for next sprint |
| Leader | Allocate buffer time within sprints (10~20%). Clarify the change management process |
Scenario: During brainstorming, E-types pour out ideas while I-types stay silent
| Role | Approach |
|---|
| E-type | Pause after speaking and give I-types time to think. "What do you think, [name]?" |
| I-type | Review the agenda beforehand and prepare opinions. Submit written feedback after the meeting if needed |
| Leader | Share agenda in advance. Ensure quiet members get speaking opportunities. Provide written feedback channels |
Scenario: In a technical decision, S-types demand specific data while N-types emphasize future vision
| Role | Approach |
|---|
| S-type | Argue with data, but also acknowledge the value of long-term perspectives |
| N-type | Support your vision with concrete steps and numbers. "If we go this direction, we expect XX% improvement in 6 months" |
| Leader | Provide a decision template that includes both data and vision |
┌─────────────────────────────────────────────────┐
│ Example Project Team Composition │
├─────────────────────────────────────────────────┤
│ │
│ [ENTJ/ESTJ] Project Lead │
│ → Direction setting, schedule mgmt, decisions │
│ │
│ [INTJ/INTP] Architect │
│ → System design, technical decisions │
│ │
│ [ISTJ/ISTP] Senior Developer │
│ → Stable implementation, code quality, debug │
│ │
│ [ENTP/ENFP] Innovation Lead │
│ → New approaches, prototyping │
│ │
│ [ISFJ/ESFJ] Team Communicator │
│ → Team harmony, stakeholder communication │
│ │
│ [INFJ/ENFJ] PM/Scrum Master │
│ → Team vision sharing, motivation, mediation │
│ │
└─────────────────────────────────────────────────┘
| Composition | Strengths | Risks |
|---|
| T-types only | Logical decisions, maximum efficiency | Cold atmosphere, high turnover |
| F-types only | Great atmosphere, high satisfaction | Avoiding hard decisions, low efficiency |
| J-types only | Systematic execution, meeting deadlines | Slow to adapt, rigidity |
| P-types only | Flexible response, creative | Missed deadlines, lack of direction |
| Balanced team | Diverse perspectives, complementary | Initial conflicts possible (management needed) |
| Pairing | Effect | Caution |
|---|
| INTJ + ENFP | Strategic thinking + creative ideas | N-overload possible, need concrete execution plans |
| ISTJ + ENTP | Stable implementation + new approaches | May frustrate each other, mutual respect needed |
| INTP + ESFJ | Deep analysis + user perspective | Communication style differences need adjustment |
| ISTP + ENFJ | Practical solutions + team perspective | Agree on goals first |
## Preparation
- Prepare light conversation starters (E-types warm up quickly)
- Allow ample speaking time
- Face-to-face/video is more effective as they prefer verbal feedback
## How to Proceed
1. Start with casual catch-up (2~3 min)
2. Catch and organize key points while they talk
3. Set action items together and confirm verbally
4. Follow up with a simple reminder message
## Preparation
- Share the agenda in advance (give them time to think)
- Prepare a list of questions beforehand
- Also provide written feedback
## How to Proceed
1. Start with "What task was most interesting last week?"
2. Ask open questions and wait patiently (don't fill the silence)
3. Focus on 1~2 topics for deep discussion
4. Accept additional feedback via Slack/email
## Key Points
- Logical and specific feedback
- Use facts and data rather than emotions
- Discuss growth paths and technical challenge opportunities
- Provide clear explanations for "why?"
## Example Conversation
Leader: "Last quarter your code review turnaround averaged 2 hours,
well below the team target of 4 hours. Next quarter, how about
focusing your capabilities on junior mentoring?"
## Key Points
- Check on relationships and well-being first
- Listen to concerns about team dynamics
- Help connect personal values to work
- Express empathy, then collaboratively find practical solutions
## Example Conversation
Leader: "How's the team atmosphere lately? Are you comfortable?
If there's anything inconvenient about your work,
please share. Let's find solutions together."
8. Limitations and Cautions of MBTI
| Criticism | Description |
|---|
| Binary classification | Divides people into E or I, but reality is a spectrum |
| Test-retest reliability | About 50% get a different type when retested after 5 weeks |
| Barnum effect | Feeling that vague, generally applicable descriptions fit you specifically |
| Context dependency | Different types may emerge at work versus at home |
| Academic standing | Psychology academia trusts Big Five (OCEAN) more |
- Hiring criteria: Never use MBTI to decide whether to hire or not
- Ability judgment: Statements like "ISFPs can't lead" are prohibited
- Labeling: Stereotyping like "Typical P, always late" is prohibited
- Forced disclosure: Never force anyone to share their MBTI if they do not want to
- Performance reviews: Incorporating MBTI into evaluations is inappropriate
1. MBTI is a "tool for understanding," not a "tool for judgment"
2. Types indicate preferences, not abilities
3. People grow and change → don't box them in by type
4. MBTI is just a conversation starter, not the whole picture
5. Use alongside other tools (DISC, StrengthsFinder, etc.)
| Tool | Advantages | Suitable Use |
|---|
| Big Five (OCEAN) | Academically validated, spectrum measurement | Individual personality understanding |
| DISC | Behavior-focused, intuitive | Team communication, sales |
| StrengthsFinder | Strengths-based approach | Role assignment, career development |
| Belbin Team Roles | Team role diagnosis | Team composition optimization |
| Enneagram | Focuses on motivations and fears | Self-understanding, growth |
MBTI is not a tool for putting people in categories -- it is a starting point for understanding different perspectives and styles. The three most important things when using MBTI at work are:
- Use it to understand, not to judge
- Respect others' preferences and adjust your own communication style
- MBTI is just a reference -- real conversations and observation matter more
Ultimately, good collaboration starts not from any specific tool, but from the effort to understand others. We hope MBTI can be a first step in that effort.