Software Engineering psychology-how does Party B face Party A's 1

In the previous articles in the software engineering psychology series, I talked about the relationship between Party A's leadership, Party A, and Party B throughout the entire software project scope, as well as the relationship between Party A and Party B as the person in charge of Party, how can we figure out the psychology of leaders and Party B to better facilitate the development of engineering projects. In the following article, we will begin to talk about how as Party B, we will try to figure out the psychology of users (Here we talk about Party A) and how to maintain a good relationship with users during the project, how can we optimize our resources to the maximum extent during the project process, protect our own interests, and cooperate happily with our users without losing or losing users? We will also talk about how to be the person in charge of Party B, how to grasp the team mentality and build a team better.

First, let's take a general look at Party B's position and problems and characteristics in the project. Let's continue to look at this figure:

Note that 3 and 4 indicate the relationship between Party A and Party B:

The meaning of 3 can be understood as: the person in charge of Party A puts pressure on Party B to obtain high-quality products within a limited time. Because the user is a god, his or her mentality is always high, if a high level of technical director is involved, it is sometimes even more difficult. Therefore, it is possible to grasp the psychological status of Party A as follows: impatience, stress on the project, laissez-faire on the progress of the project, seriousness, fairness, and justice, and so on .......
The meaning of "4" can be understood as: Party B regularly communicates with Party A's director, reports, accepts Party A's opinions, and accepts Party A's criticism, party A and the person in charge of Party A shall be more angry. Therefore, Party B often needs to have good communication with Party A's owner, maintain a good relationship, and do a good job of PR with Party A's owner.
Since Party B has the most time to communicate with Party A, there are also many issues to pay attention to, so we will talk about it in the future. We will not describe it here.

The relationship between Party B and the project's senior leadership is also very subtle. Therefore, the first few articles in this section will first explain how Party B has a good relationship with the project's senior leadership and grasp its psychology.
In, 9 and 10 indicate their relationships. First, let's look at 9:
9 indicates a very important link, that is, to fully pay attention to the relationship between Party B and Party A's senior leadership! I believe that many of my friends may have ignored this point, or they clearly know that they want to "please ".
"Party A's leadership", but the actual work is still unable to gain the trust of Party A's senior leadership, or to hit the wall. Some friends said: It's not the beginning of the project. If someone else's leaders have a good "PR", will it be okay to have them eat, drink, and play? In fact, this is a big misunderstanding, thinking that relying on the "PR" of traditional consciousness alone can have a good relationship with Party A's leadership. In fact, let's first try to figure out the psychology of Party A's leadership.

As a leader, the project initiator, proponent, or creator is at the highest level and has high expectations for the project's time, quality, and cost. If the leader is a technical engineer, the leader will be more nervous and more important. In addition, the leaders' psychological feelings are generally: they are eager to look forward to their own ideas and opinions, but generally seldom consider other factors, sometimes subjective; sometimes, when a project is in the opposite or wrong direction as expected, it is usually impatient. At this time, it is often "Angry" for no reason.

If the project has a person in charge of Party A, the leader will not have much chance to get along with Party B directly (you must know that people are leaders after all ). Therefore, we will discuss how Party B should deal with Party A's leaders in this case. The following are some suggestions for your reference only.

1. pay full attention to the first meeting with Party A's leaders
The first time is generally the most important and the start of success. Before Party B meets with Party A's leaders, it is best to prepare lessons, such as the following:
Is a meeting with the lead alone? Or a group meeting? Who are involved in the first meeting and what are their roles?
B. It is best to learn the background of Party A's leadership through various channels in advance, and inquire about the leadership positions, specific jobs, and previous participants through public or gossip.
Work, haha, it is best to collect as much information as possible, you can search all people's resumes to find the best, remember to use the network more, because you can from these complete or fragmented information, we can probably determine the style and personality of Party A's leaders. Of course, for a lot of general companies, if you are new to contact people, you may not be able to understand so many things. It doesn't matter. You can read more about the company's related materials, introduction. In short, we must know ourselves and ourselves.

C. It is important to discuss with the leaders what they plan to introduce to them for the first time. It is recommended that you attach great importance to it, list the outlines, and let the senior executives of Party B Review and comment on what to say and what not to say. Generally, the first meeting will give the leaders an overview of Party B's views on the project and the work plan of the entire project. Here, we should note that we should not rush to express our determination to the leaders. Sometimes, when Party B meets for the first time, it is eager to express Party B's strength to the leaders so that they can trust their teams, this will often cause unnecessary troubles in the future. Therefore, when we meet for the first time, we should carefully remember the expectations of the leaders while introducing them to the leaders, know how the leaders think, and have opinions and requirements on the project, at this time, the leaders face the technical implementers rather than the technical directors of Party A. At this time, they are most likely to have the most original requirements, opinions, and aspirations of the leaders. At the same time, if Party B estimates the difficulties it may encounter in the future project, it is a good time to truthfully respond to Party A's leadership at this time,
Leaders often receive positive responses.
Finally, we need to understand how leaders participate in the Project Plan and how they can participate in the schedule. For example, it is important for everyone to agree on the meeting cycle and contact methods for leaders present.

2. After the first meeting with Party A's leaders, we should study the key points of the meeting immediately. For example, we should report the relevant information to the leaders, and we should be able to preliminarily find out the details of Party.
The characteristics of a leader are the way in which the person handles the affairs. you can know what to pay attention to when dealing with the leader and adopt appropriate strategies. For example
During the conversation, we can see that the expectations of the leaders can be compared with the preliminary expectations of the Project to see whether there are any discrepancies. We can also determine how much the leaders attach importance to the project, for example, if a leader often has a meeting with Party B, the importance will be high;
In any case, we should prepare a detailed plan for communicating with the leaders. For example, we should ask a special person to report to the leaders at an interval. If the other leaders are very busy, at least email, phone, QQ, and other methods should be used to send the notes or other reports of each meeting to the other party's leaders. For example, if you want to plan a meeting, it is very skillful to ask Party B's leadership to come out together and "communicate with Party A for entertainment" and "PR" activities with Party A's leaders.
Only by the characteristics of the other party can we do a good job in public relations. public relations activities are too intensive, too few or too bad, which is not conducive to maintaining a good relationship between the two sides.
There is also a misunderstanding that many may think that regular communication and reports with Party A's leaders should be handled by Party B's technical personnel (such as CTO). In fact, this is not necessarily true, it is best for Party B to send dedicated Marketing personnel, such as sales personnel and pre-sales representatives, to any meeting with Party B's leaders in the early stage of the project.
One of the advantages of Party B's leadership is that it allows people who have the skills in marketing activities to better communicate with Party B's leaders and do a good job in PR, at the same time, it can make up for some shortcomings of technical personnel in some occasions, and also serve as a third-party supervision function, because sometimes technical personnel are not necessarily so professional in communication and are not careful, it will be wrong. Of course, each time the sales and technical personnel meet Party A's leaders, they must do their homework with the same caliber.

3. Establish friend relations with Party A's leaders
In addition to regularly reporting the project progress to the leaders, we also need to seize the opportunity to learn about Party A's interests and needs in some "PR occasions", and keep them updated,
It makes the other Party feel that, as a strategic partner, you can not only help Party A, but also serve as a friend of the other party. You can bring various types of transactions to Party A for a long time, at this time, Party B's leaders, sales personnel, project managers, and even programmers who implement the project must join hands. There are often many project managers and programmers who misunderstand that communicating with leaders is a matter of our CEOs and the market. They have little to do with themselves and sometimes cannot put down their shelve to face them, in fact, this is not appropriate. Because it is often in "Public Relations", technical personnel are also the best time to understand Party A's team, including understanding Party A's leadership, Party A's grassroots, and so on. Sometimes, it can be used in public relations.
, You can politely express your difficulties, help your needs, and point out some different actual demands of Party.

Well, write it here first and discuss what Party B will do next time.