The Myers Briggs test is a personality test that is based on categorising people into four sets of binaries. For example, introversion or extraversion is one group, and then it does this three more times to cover four different aspects of personality in total. Although it doesn’t have much authority in the world of serious psychology because it’s not repeatable (i.e. you can do the test once and it’ll class you as an ENTP, do it again and you’ll be a completely different INFJ. In fact, the only personality signifiers that hold weight in psychology due to repeatability are “the big five”) it’s still very popular. I think the reason for this popularity is that it gives us insight into different ways in which people think, allowing us to see the world in a way that would otherwise go unnoticed to us.
That’s not to say we’re not capable of seeing things from the other person’s perspective, it’s just that we tend to favour looking at things from one world view to the other if possible. However, I also think that a given situation will affect which side you choose to take within that specific time frame. For example, you might be drawn towards the extraverted side when you’ve not socialised for a while and want your fix (which has now been termed “ambiversion” – you show signs of both). I think that this is ultimately the downfall of the test and why the test isn’t repeatable.
Today I’d like to examine the 4th category of the Myers Briggs test: categorising into either ‘judging’ or ‘prospecting’. I think this category is perhaps the most obvious example of how we need be capable of reacting to the world as either a ‘judger’ or ‘prospector’, depending on the situation. If we weren’t capable of doing both, we wouldn’t be able to function in the world. Let’s just look at both categories quickly before jumping in.
Judging is the strategy of making plans, and then carrying that plan out, to achieve a goal. Prospecting is the strategy of ‘going with the flow’, being present in the current situation and reacting to it in a way that moves you towards the desired outcome. I’m definitely predominantly a ‘judger’ and have tended towards tasks that prefer this strategy throughout my life. But I’m always interested in people who prefer the “prospecting” side of things.
Daniel Kahneman won the Nobel prize in Economics for work in this area, describing his findings in the book Thinking, Fast and Slow. If anyone has read the book, the ‘prospecting’ strategy can be loosely thought of as what Kahneman described as “System 1”, and the ‘judging’ strategy can be loosely thought of as “System 2.” Let’s have a look at each strategy in a bit more detail, and see when each one is applicable.
There’s just one problem with people who structure their life predominantly on planning, and Mike Tyson summed it up with surprising eloquence.
“Everyone has a plan ’til they get punched in the mouth” – Mike Tyson
You might have the best-laid plans, but they only work in an environment that either doesn’t change, or if it does change: it won’t influence the outcome of the plan. If either of those conditions isn’t true, ‘judging’ strategy is useless. The plan will become obsolete before you even start to carry it out. In situations like sports, complex board games (like chess, where there are 8,902 different possible board positions after only 2 moves), and even everyday normal conversations – where you don’t know which way the conversation is going to go – you need a different strategy. There’s no possible way we can play enough games of chess so that we can have a plan for each situation, or have a plan for every possible conversation. So what can we do?
In Thinking, Fast And Slow, Kahneman described the strategy of heuristics to deal with a constantly changing environment. Heuristics can be seen as quick “rules of thumb” or “common sense” – basically they’re rules to follow that can be applicable to either a general situation (although the specifics may differ), or a by reacting to only certain sub-section of the environment (that will have the most impact) and then ignore the rest (which may still have an impact, but a lesser one). In real life, this is applied by trusting yourself to recognise the important factors in the current environment, and then to make a good snap decision based on having dealt successfully with a familiar situation in the past. The computer program Deep Blue used a heuristic-like strategy – by comparing a library of previous chess games to the game it was playing, finding all relevant (based on board similarity) examples in the library and picking the move that had the best outcome out of the given examples – to be the first computer to beat the chess Grand-Master, Kasparov, in 1996. The trick here is to know what aspects of the board are important: this is the spine of the algorithm that searches for relevant examples.
Another element of sports is to ingrain a specific movement until it almost becomes unconscious: an unconscious competence. This way, when the time comes, we do it automatically. There is no planning, just unconscious reaction. Writing about the philosopher, Marcus Aurelius, it was said (in the introduction to “Meditations”):
“But Marcus Aurelius knows that what the heart is full of, the man will do. ‘Such as thy thoughts and ordinary cogitations are’, he says, ‘such will thy mind be in time’. And every page of the book shows us that he knew thought was sure to issue in act. He drills his soul, as it were, in right principles, so that when the time comes, it may be guided by them. To wait until the emergency is to be too late”
Finally, one strategy to work in a prospecting-regime is just to be quick-witted. This works better for some than others (and I’m jealous of those who it works well for!)
In the work-place, there are multiple methodologies that work from a prospecting strategy. The most popular one is the software engineering methodology, Agile, which has become popular in the last 10 years. Agile has become so popular because customer requirements change frequently, but sometimes it takes a long time to write the code to create functions that satisfy those requirements. To overcome these issues, Agile methodology is an interesting hybrid between a prospecting mindset and a judging mindset. It works from a set of principles designed to get the code written as quickly as possible during periods known as ‘sprints’. During each sprint, the code structure is planned and then written based on the requirements (this is the judging bit). After each sprint, the code is compared to requirements and another small sprint is planned based on a reaction to the new environment (this is the prospecting bit).
Some tasks, however, are just too complex to be undertaken by a prospecting strategy, especially those in project engineering that take many years. Countless companies have gone bankrupt by not planning well enough in the beginning phases, only to find out half-way down the line that there was a critical element they overlooked, which means that sub-components designed by different departments aren’t compatible (one example from a countless number), causing them to scrap the whole project and start again. By the time they’re half-way finished through the second iteration: the project is years late and the company has run out of money.
Of course, we can’t plan for things that we can’t see we don’t know (unknown unknowns), but we can do many other things that may bring possible complications to the surface and thus we can plan for them accordingly. The first step of solving a problem is realising there’s a problem.
A popular engineering methodology that uses the “judging”/planning mindset is Systems Engineering: where the emphasis is placed on the beginning stages of a project, in which requirements are clearly set and then planned on how to fulfil them, with each department involved. In this way, and basing the planning on aspects that were covered in previous successful projects, unknown unknowns can be minimised through a number of different micro-strategies and mid-project problems can be mitigated.
I could write more about different ways the “judging” strategy is useful, and the different ways we can use it, but many books have already been written about it (countless systems engineering handbooks, or project management training books, for example) and, really, I think it’s the less interesting of the two. I feel that the “prospecting” mindset is usually overlooked, especially among engineers like myself. I think engineers who are used to planning don’t recognise the skill involved in being a proficient “prospector”, as a result, we tend to underestimate the skills needed in those departments: for example, technical sales, where a lot of work is done in conversation and understanding quickly how to react to different environments… which is why I find the prospecting perspective so interesting! Ultimately, though, we need to understand and be proficient at both mindsets, and then apply them accordingly to each situation.