HEXACO vs. Myers-Briggs

The Map Is Not the Territory — But Some Maps Are Worse Than Others

Every engineering leader eventually reaches for a personality framework. The team is struggling to ship, a senior engineer is clashing with a new tech lead, and someone in HR slides a deck your way with a grid of four letters. You've been there. The instinct to reach for a tool is right. The tool itself is the problem.

Myers-Briggs Type Indicator has been the default for decades, not because it works, but because it spread before anyone in corporate environments was asking hard questions about psychometric validity. It's the JavaScript of personality frameworks — everywhere, load-bearing, and not quite what you'd design if you started from scratch today.

The alternative isn't to abandon measurement altogether. Personality differences are real, they compound inside engineering teams, and ignoring them doesn't make them disappear — it just means you're debugging blind. The question is which instrument actually measures what it claims to measure, and which one gives you actionable signal instead of a horoscope with better branding.

MBTI's Core Problem: Binary Categories in a Continuous World

MBTI forces every human into one of sixteen discrete types by splitting four dimensions — Introversion/Extraversion, Sensing/Intuition, Thinking/Feeling, Judging/Perceiving — into binary buckets. You are an I or an E. There is no gradient, no probability distribution, no acknowledgment that most people cluster near the middle of these axes. It's a schema that would get rejected in any serious data modeling review.

The retest reliability problem is damning and well-documented. Studies show that roughly 50% of people receive a different MBTI type when retested just five weeks later. In engineering terms, you've built a classification system with a coin-flip false-positive rate and called it a hiring tool. If your monitoring system had that error rate, you'd page someone at 2am.

What this means in practice is that you're making real decisions — team composition, conflict mediation, promotion conversations — based on labels that are statistically unstable. An engineer who tests as INTJ this quarter might test as INTP next quarter. The label changes; the person doesn't. The instrument is measuring noise and calling it signal.

The binary structure also creates a false sense of precision. When a manager says 'she's an ENFP, that's why she struggles with process,' they're not explaining anything — they're pattern-matching to a category that may not even be stable for that person. It forecloses inquiry rather than opening it. Real diagnostic tools create hypotheses; MBTI creates conclusions.

There's also a deeper architectural flaw: MBTI was built on Jungian theory developed in the early twentieth century, before modern psychometrics, before large-scale empirical validation, before anyone had the computational tools to factor-analyze personality data at scale. It's not that Jung was stupid. It's that the field moved on, and MBTI didn't follow.

What HEXACO Actually Measures — and Why the Difference Matters

HEXACO emerged from a different epistemological tradition entirely. Researchers Ashton and Lee didn't start with a theory and build a questionnaire around it. They started with lexical studies — analyzing the personality-descriptive adjectives that humans across multiple languages had evolved to describe each other — and let the factor structure emerge from the data. The model reflects how humans actually perceive and describe personality variation, not how one theorist in 1920s Zurich categorized the psyche.

The six dimensions — Honesty-Humility, Emotionality, eXtraversion, Agreeableness, Conscientiousness, and Openness to Experience — are continuous scales, not buckets. An engineer doesn't score 'high Conscientiousness' or 'low Conscientiousness' in a binary sense. They sit at a specific point on a distribution, and that point is stable across time in ways that MBTI types simply are not. You get a measurement, not a label.

The Honesty-Humility dimension is HEXACO's most distinctive contribution and arguably its most valuable for engineering leadership. It captures the degree to which someone is sincere, fair, and non-exploitative — traits that MBTI doesn't measure at all. In a team context, this dimension predicts who will sandbag estimates to protect themselves, who will take credit for collective work, and who will be straight with you when a project is off the rails. That's not a marginal improvement over MBTI. That's a fundamentally different category of insight.

Continuous measurement also means you can reason about team composition quantitatively. If you have a team where four of five engineers score in the 80th percentile for Conscientiousness and one scores in the 30th, you have a structural mismatch that will generate friction around code review standards, documentation expectations, and on-call discipline. HEXACO gives you the resolution to see that. MBTI gives you four letters that may not even be consistent month to month.

The Engineering Leadership Patterns That HEXACO Actually Explains

Consider the classic senior engineer who is technically brilliant but catastrophic in cross-functional meetings. MBTI would call them an introvert and move on. HEXACO gives you a more precise picture: high Openness, low Extraversion, and critically, low Agreeableness combined with high Honesty-Humility. That specific profile means they will tell the product manager exactly what they think with zero diplomatic softening, not because they're antisocial, but because they genuinely value directness over harmony. The intervention is completely different depending on which read you have.

Or consider the tech lead who can't delegate. In MBTI terms, maybe they're a 'J' type with strong judging preferences. In HEXACO terms, you're looking at extreme Conscientiousness paired with low trust in others' Conscientiousness — a profile that predicts micromanagement under pressure as reliably as a load test predicts latency degradation. You can coach around that specifically. You can structure their team to give them visibility without requiring control. You can't do that with a four-letter type.

The Emotionality dimension is particularly underappreciated in engineering contexts. High Emotionality predicts anxiety under ambiguity, strong empathy responses, and a tendency to seek reassurance during incidents. Low Emotionality predicts emotional detachment that can read as either calm under pressure or alarming indifference to team morale, depending on context. Neither is better. Both have load-bearing roles on a high-functioning team. HEXACO lets you see the distribution; MBTI doesn't have the resolution to map it.

Teams with mismatched Openness profiles generate a specific and recognizable friction pattern: the high-Openness engineers want to explore new architectures, new languages, new paradigms constantly, while low-Openness engineers want stability, predictability, and the comfort of well-understood systems. Both are right about something important. The CTO who understands this isn't mediating a personality conflict — they're managing a portfolio of cognitive risk tolerances. That's a different and more powerful frame.

Why Leaders Keep Reaching for MBTI Anyway

The persistence of MBTI in engineering organizations isn't irrational — it's path-dependent. It has thirty years of institutional momentum, a massive certification industry, and the enormous advantage of being familiar. When you're already managing a roadmap, a budget, and three competing architectural decisions, 'familiar' has real value. Switching costs are real even when the incumbent tool is inferior.

There's also a psychological comfort in discrete types. 'She's an INTJ' is a complete sentence. It feels like an explanation. Continuous dimensions require more cognitive work — you have to hold a profile in mind, reason about interactions between dimensions, and resist the urge to collapse nuance into a label. That's harder, especially under the time pressure that engineering leaders operate under constantly.

The team-building workshop industry has also shaped expectations. MBTI retreats are a known format with known outputs: everyone gets a type, the facilitator explains the types, people laugh about their results, and the team goes home feeling like they understand each other better. Whether they actually do is a different question. HEXACO doesn't have that cultural infrastructure yet, which means adopting it requires more intentionality — but that intentionality is exactly what separates leaders who build durable teams from leaders who keep debugging the same interpersonal failures.

The real cost of MBTI isn't the licensing fee or the workshop time. It's the decisions made on bad information. It's the engineer who got passed over for a tech lead role because their 'type' suggested they weren't leadership material. It's the team that never got restructured because the manager thought the conflict was just 'an INTJ-ENFP thing' rather than a measurable mismatch in Honesty-Humility and Agreeableness that had a structural solution.

Use the Map That Reflects the Actual Terrain

LU Teams is built on HEXACO precisely because the alternative isn't good enough for the decisions engineering leaders are actually making. When a CTO is deciding whether to put two senior engineers on the same feature team, or whether a new VP of Engineering will mesh with an existing staff-level culture, or why a previously high-performing squad started missing sprints after a reorg — those questions require a measurement instrument that is empirically validated, temporally stable, and dimensionally complete. HEXACO meets that bar. MBTI doesn't.

The platform translates HEXACO profiles into team-level friction predictions before the friction happens. That's the operational value of continuous measurement: you can model interactions, identify structural risks, and make compositional decisions proactively rather than reactively. You're not waiting for the post-mortem to figure out that two engineers had fundamentally incompatible approaches to risk and ownership. You see it in the profile before you finalize the team.

The Honesty-Humility dimension alone — the one MBTI doesn't touch — predicts a category of team dysfunction that costs engineering organizations months of velocity and enormous amounts of leadership bandwidth. Knowing where your engineers sit on that scale isn't a soft HR concern. It's a hard engineering management input, the same way knowing your system's latency percentiles is a hard infrastructure input. You wouldn't run production without observability. You shouldn't run teams without it either.

The goal was never to turn personality science into astrology with better slides. The goal is to give engineering leaders the same rigor in understanding their human systems that they already apply to their technical systems. HEXACO is the instrument that makes that possible. Everything else is a less accurate map of the same territory — and in engineering, the accuracy of your map determines whether you ship or whether you spend another quarter debugging something that was always a people problem wearing a technical costume.