The rules that help me survive in the new team and run the system. Start

You are on the threshold of a new organization and you face the complex task of launching a new equipment, system and / or program. We skip the sales component and go directly to the study of the problem, where our project is outlined by budget, deadlines and tasks. It is important not to forget that one facet of a successful launch is the psychology of entering a project and interacting with employees. After all, any technology is controlled by a person, and it is with him that the primary contact for data collection will occur.

From the story marked "secret":

The most disastrous project with my participation was in servicing the daughter of an oil producing enterprise. The project manager on the part of the customer, who is also the chief accountant, didn’t stint on sharp remarks about his colleagues and me in his “little over 20” years. There was disgust when the abuse was addressed to their own employees, where, for example, the secretary was “bychara” due to excessive weight. My project survey interview had a functional response: “See for yourself!”. At first, I was emotionally shocked and I was looking for ways to solve this situation. Perhaps I searched for a long time, because negative fluids flew all over the room during our “communication”, and I was removed from the project with a crash at an extended meeting as an illiterate specialist.

But this is all the author's opinion, that is, it is subjective and subject to doubt. This will be the first rule that I learned for myself in the process of entering the project and getting acquainted with the company.

Do not take anyone’s word until they are confirmed by facts. Doubt to the last

')
We turn to more productive work on the project. An example would be a conversation, where an employee states that the incoming information (customer order) for him is exclusively the uploading of data from the site.

- There are exceptions? - sounded my question.

- No ... - pause. - Although, there is one special VIP-client who sends applications directly via email to Natalia Stepanovna. This is our senior manager.

For you, this is an indicator of two different site architectures. It is good if the “pause” specified above is measured in seconds, rather than a period up to commissioning, where the lack of functionality will become clear. We do not consider the trial on the subject of the wording of the technical task - it does not bring any of the parties closer to the goal. Only if not this case for 25 billion rubles .

In the process of obtaining information is required to ensure the completeness of the data. Checklist for this event:

1. All copies of used paper documents and files were transferred.
2. The testimony of witnesses. It is better to conduct a conversation with a group of employees - process performers, because the collective mind often recalls the details in which the devil lives, according to the well-known English proverb (“The devil is in the detail”).
3. Compiled sketches of processes and registry.
4. An oral repetition of all the actions of the employee, which I marked in my notebook. Like a waiter before placing an order.
5. Important. Signed employee (s) in the minutes of interviewing with an indication of a sketch of the business process, workflow, registry operations, etc. Before the signature, as a rule, the interlocutor begins to re-run his eyes on the written text in an attempt to find the lost. Signature adds responsibility.
6. Intuition tells you that nothing has been hidden from you.

Why doubt? So, among other things, it is human nature to err and not with malicious intent.

Do not be afraid to seem corrosive - this is a positive feature of any analyst (researcher)

Practical example:

- The entire issue, in addition to the program, we reflect in the magazines for production, - said the employee.

- Why do I see 3 magazines? - I ask a question.

- Well, for registration of products A in the journal 1, products B, C, D in the journal 2, the rest of the products in the journal 3.

At this point, many analysts make a mistake and make the initial wording in the terms of reference. Remember that a fivefold answer to the question "why" leads you to a true problematic.

- Why not use one magazine for all products? - I ask, seeing that the structure of all magazines is similar.

- In separate accounting it is easy for me to find the necessary order for production and other parameters.

“Why look for them?”

- If a request is received from the production director, dispatchers, masters. Or made a marriage.

- But you enter data into the program. Can they see the required information there?

- Yes.

“Then why are you doing this?”

- These are the ****** rules! They have all the information, but do not want ...

As mentioned above, the five-fold question “why?” Helps to identify cause-effect relationships. According to the information from Wikipedia " Five Why ", the Japanese entrepreneur Sakichi Toyoda came up, although purely my opinion is from the category of psychoanalysis.

Retreat. Work through any of your fears on the described technique: "I am afraid (for example, to quit) ...". Awareness of the root cause should reduce its impact on you and plan a roadmap of solutions.

At the survey stage, try to maintain a neutral relationship.

- Hello, my name is Sergey Kukanov. Currently, I am conducting a survey of your company in order to further automate business processes and launch a new system. I would like to talk with you about your responsibilities. In the course of the conversation I will take notes, request copies of the documents that will be included in the survey report and the terms of reference. Tell us a little about your work.

The reaction of the employee may be completely different. Someone productively hold a conversation, and someone will scream that he has no time (the meeting is agreed). Someone will be your friend, and someone to pour bile. It is worth taking for granted that you will not have a good relationship with everyone, but this is normal for any team. Remember that your goal is not to make friends, but to solve the task within the project and your responsibilities. Moreover, friendly relations for a project carry more risks than neutral ones. Examples:

• He will offer you many features and ideas that may not fit into the concept of the project. If you reject them, he may be hurt.
• Your friend will be looking forward to transfer all his professional experience and knowledge. But you do not need this for the project.
• “Seryozh, look! Make a green button here. More green! And to the left. "(This is not a design task). If this is not the sponsor / customer of the project, then bold ignore. If a sponsor, then you are at risk, which I described in this publication , as the wrong technology implementation.

In any respect, I recommend asking questions for your own analysis:

• Why such a position of this employee?
• Does this make it difficult to achieve a local and global result?
• What are the risks and what are the possibilities to minimize them? (add to your personal risk card)

In the next publication I will try to describe the observations that indicate the company's determination to change, as well as about the resistance of employees to the new.