The Architect and the Mastermind

Like so many other programmers, I possess an insatiable desire to build something useful. The sole purpose of any system is to be the focus of my criticism, and suggestions for improvement are a necessary outlet. Any application I build, after finished, is undeniably worthless, and must be completely refined, streamlined, and re-built. This cycle is maddening, but it is the core of my temperament as an Architect (INTP) according to Dr. David Keirsey.

The Keirsey Temperament is similar to the Myers-Briggs Type Indicator, as it helps to classify an individuals personality traits. Temperament according to Keirsey.com, is defined as follows:

Put another way, our brain is a sort of computer which has temperament for its hardware and character for its software. The hardware is the physical base from which character emerges, placing an identifiable fingerprint on each individual’s attitudes and actions. This underlying consistency can be observed from a very early age — some features earlier than others — long before individual experience or social context (one’s particular software) has had time or occasion to imprint the person. Thus temperament is the inborn form of human nature; character, the emergent form, which develops through the interaction of temperament and environment.

The two temperaments that make up the smallest percentage of the population (5-10%), the Architect and the Mastermind (INTJ), also make up a large percentage of programmers. Although the latter figures are unsubstantiated, programming is an often suggested career path for the INTJ or INTP. Many Web development firms are staffed with individuals who possess qualities analogous to these temperaments. However, distinguishing the difference between the two, or mistaking one for the other can be extremely detrimental to an organization.

An excerpt of the Architect definition from Keirsey.com:

Of the four aspects of strategic analysis and definition, it is the structural engineering role — architechtonics — that reaches the highest development in these Rationals, and it is for this reason they are aptly called the “Architects.” Their major interest is in figuring out structure, build, configuration — the spatiality of things.

The inclination toward constantly constructing, is what makes it difficult for companies to retain a large number of Architects. Performing repetitive tasks, or being assigned a workload with fixed parameters is likely to push the INTP toward another assignment at a different company. Rigid, closed systems, are also an abhorrence to an Architect, as there is no room for improvement. Innovation, as opposed to implementation, is the call sign of an Architect, and feeding that motivator is important.

Most Architects can thrive in very limited chaos. This situation can provide the opportunity to help design a system that benefits the good of whatever might be the cause at the time. Yet, chaos can also become a distraction, preventing an Architect from concentrating on a greater Utopian aspiration. If there is no measure of success, or there is no prospect for perfection, then there is a high likelihood an Architect will become frustrated.

This is unlike the Mastermind, and it is the one personality trait that distinguishes the two temperaments. An excerpt of the Mastermind definition from Keirsey.com:

It is in their abilities that Masterminds differ from the other Rationals, while in most of their attitudes they are just like the others. However there is one attitude that sets them apart from other Rationals: they tend to be much more self-confident than the rest, having, for obscure reasons, developed a very strong will. They are rather rare, comprising no more than, say, one percent of the population. Being very judicious, decisions come naturally to them; indeed, they can hardly rest until they have things settled, decided, and set. They are the people who are able to formulate coherent and comprehensive contingency plans, hence contingency organizers or “entailers.”

Masterminds are more capable of being self-sustained at companies for longer durations, so long as they are allowed to come to some conclusions about the work, and environment. It is not the act of creation, but the predisposition toward making decisions about a system that drives a Mastermind. A Mastermind can remain satisfied so long as input is freely received and solicited, and occasional steps are taken toward implementation of ideas. This is a minor variation from the Architect, but understanding the difference can drastically affect the retention rates among programmers.

Of course, like any personality “quiz”, there is an ethical responsibility not to draw immediate conclusions based upon an individual’s temperament. Numerous extenuating circumstances can affect a programmer’s satisfaction, including something a simple as the drive to work, or salary and benefits. Although, when developing professional and personal growth plans, it is helpful to understand the difference between an Architect and a Mastermind. Fulfillment at work can be more easily achieved by recognizing and satisfying the needs associated with each temperament.

Read more about the Architect.

Read more about the Mastermind.

• Posted by Brian
• November 9th, 2007