Four people on one project shared the same personality vocabulary. We split the work in an afternoon without a status meeting. Six weeks later the same four people could not agree on whether to cut a feature, and the vocabulary helped not at all.
That is not a contradiction. It is the exact limit of what a label does.
The three jobs
A personality label does three things well, and all three are social.
It names something a person was already living. The first time someone hears a precise description of a habit they have never had words for, the relief is genuine and it is worth something.
It excuses. "That is just how I am wired" ends a disagreement faster than any argument anyone could construct. This is useful in moderation and corrosive when it becomes the default explanation for every cost the team absorbs.
It coordinates. This is the one engineering teams quietly depend on. Shared words let people divide work, predict who will want a written spec, and know who will push back on an estimate.
Now look at what is missing. None of those three is a decision. A label never says what to do on Thursday.
Why collecting more of them does not help
I have run this as an informal exercise with a few teams: ask everyone how many personality assessments they have taken. Most people are at three or more. Then ask which of those results changed a decision they can date. Almost nobody can name one.
The usual conclusion is "wrong framework, try another one". But the shape of the problem is not a shortage of information about yourself. It is a surplus of vocabulary sitting next to a deficit of decisions. Words about a person can accumulate without limit while their behaviour stays exactly where it was.
There is a second effect worth knowing about if your team uses assessments in hiring or onboarding. By the fifth questionnaire a person has learned the genre. They know which answers sound reflective and which sound unreliable. The form is not adapting to them; they are adapting to it. So a result that "converges" with earlier ones may be measuring test-taking fluency, not a stable trait. Specificity feels like accuracy, and a sentence can be extremely precise about the wrong question.
A twenty-minute audit, adapted for a team retro
Run these against any framework result your team is currently using, including ones you like.
1. Which decision did this change, and can you put a month on it? Not a good conversation, not a shared understanding. A handoff, a scope cut, a limit someone stated once and held. If nothing surfaces with a date, it has been information the team enjoyed rather than information the team used.
2. If this turned out to be wrong, what would we do differently this month? Answer before defending the framework. Given thirty seconds to defend, any team can defend any model. Asked to name a change first, most come up empty. A belief that changes no action is a costume. Costumes are fine as long as everyone knows they are wearing one.
3. Which label do we reach for when explaining a failure? This is the informative one. Labels do their longest service in post-hoc explanation, sitting between what went wrong and what gets tried next. In retros it shows up as "that is just how that team is". The label is doing real work there, and the work is usually protection.
Most groups end up with one item carrying a date and four pieces of furniture. Keep the one. Retiring the rest costs nothing.
What to ask of a framework instead
A useful output is not a portrait. It is a single over-extended scale, the conditions that push it too far, the conditions that absorb it, and the version of it colleagues can already see without learning any vocabulary. That is a checkable unit. You can revisit it next month and see whether it moved.
Narrative Personality Reading: instead of assigning you a type, it reads your personality as a manuscript you can revise, using nine core colors and nine friction points. It is the framework I work on, so the audit applies to it too. If it becomes one more label a team quotes in a retro without changing a decision, it has failed in exactly the same way.
The honest limit
This is not a clinical instrument, and it will not rank the assessments you have already taken or rule on whether their results were accurate. If you have a clinical or a hiring-compliance question, neither a test nor an audit answers it; that is a different conversation with different professionals.
The practical version is small: before adopting another framework, ask which decision the last one changed and when. One dated decision is worth more than a folder of accurate descriptions.
Longer version of the argument: https://echolio.vip/blog/read?slug=five-personality-tests-and-nothing-changed
Top comments (0)