Skip to main content

How Do I Use Myers-Briggs To Assess My Team?

Question: How do I use Myers-Briggs to Assess My Team?

Answer: You don't.

Seriously. That's my answer. Don't do it.

Still reading?

(sigh)

Alright, if we're going to do this dance, let's get it over with.

Myers-Briggs is Junk Science

When a hypothesis is tested in a controlled experiment, proven, and those results are vetted by independent peers, you have yourself a little thing we like to call scientific evidence. Leave any of these on the table (eg. you make a hypothesis but don't run an experiment), all you have is opinion.

The missing piece in Myers-Briggs (or MBTI) is that last part: independent verification by peers. Scientists uninvolved in the hypothesis need to be able to reproduce the experiments and put their career on the line by saying, "Yeah, this other scientist I don't know anything about...they're 100% correct."

The only "verification" that Myers-Briggs has is via the Center for the Application of Psychological Type, created by (wait for it) Isabel Myers, and her mother, Catherine Briggs.

(Doing my best David Spade impersonation) It's called "Conflict of Interest". Look into it.

The Forer Effect

Humans are apt to succumb to a psychological effect dubbed "The Forer Effect" which is our tendency to rate vague, broadly generalized descriptions as highly accurate depictions of ourselves. It is a lucrative cognitive bias that keeps many a fortune teller and astrologer in business.

If you take seriously anything the Myers-Briggs spits out about your team, you are doing both yourself and them a monumental disservice.

What To Use Instead

Don't rely on unproven personality tests to categorize / pigeonhole your teammates. People require effort. Don't take the easy way out on this. Make an effort to learn about the ways humans fool themselves instead, so you are better equipped to recognize those biases and fallacies in the real world, and be prepared to tackle those problems appropriately.

Start with these two sites:
When you're done with those, sign-up for the mailing list below, and we'll go even deeper down the rabbit hole.

And P.S.: No need to harass all those Twitter folks with those magical four letters in their profiles - they won't remove them. That's the funny thing about our cognitive biases: they prevent us from recognizing them, but only people that can recognize them will admit it.

Popular posts from this blog

Sad Stories

How are you measuring the quality of your product management? Is it: How accurately you adhere to Scrum?  How close your velocity matches your SLO?  The number of bugs fixed in this sprint? None. of. this. matters. A surface level review of these metrics would seem to matter to folks desperate to boast about their Agile compliance, while failing to remember the first edict of the manifesto : Individuals and interactions over processes and tools A recent tweet reminded of this: Wow! I reported a unicode issue affecting URLs to 2 different commercial software companies. One responded in 4 days indicating it'll be fixed in a yet-to-be released new version (which requires more $$$); the other provided a working patch in less than 3 hours. — James Moberg (@gamesover) June 18, 2019 While I can't comment on what specific bottleneck is separating these two companies, I understand (all too well) the side-effect of throwing everything into a Scrum bucket. Af...

Tired: 10x Developers. Wired: 10x ENVIRONMENTS.

image: the mythological 10x developer, caught in its natural habitat. A 10x developer thread blew up on Twitter over the weekend. A startup/disrupter posted their tips on how to find the mythological 10x engineer and what massive rewards your organization will reap by having one. Unfortunately, their "tips" only amounted to the perpetuation of a very different type of engineer: one who can't mentor, can't be bothered to attend a meeting, knows only code (to the detriment of all other soft skills), and will insist on doing things the right way...aka their way. In short, it was a list of attributes that described a toxic developer. After having slung code for two decades...and am now charged with leading my own team of developers...here is the harsh truth of the matter: If you want to build a team of highly productive developers, focus on building a 10x environment . Build knowledge sharing into your process, so your team is actively invested in educa...