How often does a programmer face the choice of target audience? I, frankly, I can not especially call myself a programmer, but this is connected very closely. I am a customer, and in fact a project manager. As a rule, this question arises at the moment when you design a new application. Whether it is a module for 1C, a web site or an application for the iPhone - the task is obvious. It is necessary that the user was comfortable.
As a rule, we try everything on ourselves - if it is clear to me, it is convenient for me, it means that the user will be comfortable. And in practice, we are faced with a “normal” situation where the user cannot find a button or function that is for you in an obvious place. So let's see where such misunderstandings come from?
If you look at the statistics, as a rule, programmers are people quite educated, for whom knowledge is one of the basic values. For people with such values, logic, information, accuracy is very important. And who are the main consumers of the products of programmers?
Of course it depends on the scope:
- if you write under 1C, this is obviously either an accountant or a salesperson (although managers also use it);
- if banking products, then these are clerks of banks and their leaders;
- if the game - it all also depends on the type of game;
- if you write sites - they also have target audiences.
There is always an end user image. And it is necessary to define it specifically.
A bit of history
About a year ago, I discovered one theory, which turned my perception of clients, employees, and, in general, people as such. This is the DISC theory. It was developed back in the 1930s of the last century, but it still does not lose its relevance. Its developer is
Dr. William Molton-Marston . He was one of the first to create a valid lie detector.
Marston divided all people, conditionally, of course, on those who perceive the environment as friendly and focused on people and those who perceive it as hostile and task-oriented. And then again he divided everyone, into those who perceive themselves as stronger than the environment and active, and into those who consider themselves weaker than the environment and passive.
As a result, he got four behavioral patterns. Marston gave each of them a name and with the help of observations described their characteristic patterns of behavior.
')
Dominance (
D, Dominance ) - these are people who consider themselves stronger than the environment and are active, and perceive the world as hostile. These are very active people, they can’t sit, they are always busy, they are demanding and tough. They rarely pay attention to details.
Influence (
I, Influence ) are people who consider themselves stronger than the environment and are active, and perceive the world as friendly and people-oriented. They are bright, fast, sociable and open, they are “stars”. It is important for them to be visible, approved by other people. They rarely get things done.
Stability (
S, Steadiness ) - these are people who consider themselves weaker than the environment and passive, and perceive the world as friendly and people-oriented. People of this type are very reliable, they are caring, friendly, but somewhat slow and do not make decisions quickly, they are not decisive. These are people of the process.
Compliance (
C, Compliance ) - these are people who consider themselves weaker than the environment and passive, and perceive the world as hostile and task oriented. These are people who are interested in procedures and rules, they make decisions carefully and slowly. They are critical and skeptical. It is often very smart.
This is a very short characteristic of these four types. To make it clearer, I will give a few examples. A lawyer is a profession. But she has a lot of directions.
The judge is often the type of “D” (Dominance), the type of activity requires dominance, authoritativeness, decisiveness, especially not to empathize.
A lawyer is a type of “I” (Influence): active, bright, expressive, articulate, sociable.
The legal adviser at the enterprise - often type “S” - desire for stability, quiet work, routine, ambitions are not high.
Notary - often "C" - clear rules, procedures, details and perseverance are important.
Also, the famous personalities of each type are quite indicative:
- “D” - Joseph Stalin, Donald Trump, Vladimir Putin, Viktor Yanukovych, Margaret Thatcher.
- “I” - Bill Clinton, Zhirinovsky, Richard Branson, Yulia Timoshenko, Jim Carrey.
- "S" - John Paul II, mother Teresa, Mahatma Gandhi, Princess Diana.
- “C” - Albert Einstein, Bill Gates, Al Gore, Viktor Yushchenko, Mykola Azarov.
How can this be applied to programming?
As a rule, you can imagine your end user. Create his approximate portrait.
Answer simple questions:
What is the nature of his activity (not a profession, but what exactly does he do)?
What is the pace of his work?
If he is engaged in this activity, what are his values?
How much time does he spend with your application?
Does your end user matter the process or just the end result?
The future product interface, functionality and capabilities will depend on the answers to these questions.
Features of each type in the perception of software
Each of the behavioral styles has its own characteristics of perception of information, its own values and pace of movement. Next, we will examine exactly what features of each type.
Type "D"
In the post-Soviet countries, in Russia, Ukraine, most often leaders are people of the type “D” - “strong hand” (in Germany - more often “C”, in Italy - “I”). Also very often sellers in active sales are also “D” type - “fighters”. More often, the “D” style is carried out by law enforcement officers (especially opera), sportsmen. Therefore, if your product is focused on managers or sellers, then the following should be considered.
People of this type are quick, so if you need to answer a lot of questions, fill out forms, and do detailed reports, that’s just unnerving. They would rather refuse than use such a product. If there is a simple wizard in the program, an assistant who can be clicked “on”, “on” is for them.
They do not pay attention to details. Therefore, what is IMPORTANT should be noticeable.
If the program slows down a bit, it is very annoying because of their natural impatience.
For them, the status and the result is also important. Therefore, in the description of the program should be clearly described, in a few words, what results gives the product.
Type "I"
Artists, designers, artists, stylists, show-men and musicians - most often they are people of the “I” style. Just as often, PR advocates, advertisers, and leaders of a charismatic type also belong to this behavioral style. They are often very unorganized, so reminders should be foreseen in the functional or something like that.
They also love to be in sight and everything is bright, so the design of software that is meant for people of this type should be given special attention (they probably noticed how different musical programs look like: everything is painted, on metal, it glitters). For example, for the “C” style - design, this is a minor issue, for them the most important information.
Due to the fact that the order for “I” is simply intolerable, if you can move icons, buttons, etc. in your software, make sure to prominently make a button - “Return everything as it was at the beginning”. They can just forget what and where they moved.
People of type “I” are focused on relationships, so if the program provides customer profiles, counterparties, there is and make room for photos, it will be in demand.
People of the “I” style are those who have the most completed profiles on Odnoklasniki or VKontakte with a bunch of photos and lots of friends.
Type "S"
In banking institutions, in positions of tellers, cashiers, credit managers, etc., people most often work with the prevailing type “S” (Stability). Also, secretaries, accountants, civil servants (clerical) are also most often people with this behavioral type.
They are rather plodding, but due to the fact that for type “S” indecision is one of the prevailing character traits, the software product must necessarily contain detailed hints with options for all occasions. They most often need support, because if they don’t understand something they will prefer to simply refuse to use a function or product as a whole, rather than disturbing someone. That is why the forms and contacts of support should be available at a glance.
They are very fond of stability, so if you plan to change the interface of the program in the next version, for them it can be a tragedy. They most often resist new programs (as well as all changes), but when they get used to it they are regular customers who are with you forever.
Type "C"
Experts, technologists, programmers, controllers, editors, scientists (exact sciences) are most often representatives of type “C”. Also often they are deputy directors, chief accountants, bankers (of higher rank).
For people of this type, the main value is information. These are users of expert systems, they like reports, statistics.
For them, the program interface should be concise and informative. They are irritated by various graphic elements.
Due to the fact that they are very observant and pay attention to the details, errors in the programs and texts simply enrage them. These are the users who send error reports. They are the best software beta testers.
They are also consumers of quality. They are willing to pay good money for quality products.
For people like “C” the most important thing is logic, therefore the structuredness of the information provided is very important for them.
Instead of conclusion
All of the above, these are trends. Most often you can just observe this in successful software products in a particular area. Often the reason for this success is not only that the developers fell into the desired target category with their product. And also guessed with the details and values for their target audience.
You can still write a lot about the theory of DISC, but within the framework of one article it will not fit. If this topic is interesting to Habrasoobshchestvo, it will be continued.
Possible topics:
"Theory of DISC in the construction of project teams."
“Programmer and family. Relationships in a team and family. DISC for non-lichen.