How to build the project team of CIO under the financial crisis

Now most enterprises are shrouded in the background of the financial crisis, for the Enterprise Informatization project implementation, but also put forward a new requirement, is how many good province of the Informatization project to get up. Many business leaders watched and waited. They hope that through the http://www.aliyun.com/zixun/aggregation/14354.html "> Information management software to enterprises to inject a glimmer of vitality." The author thinks, the Enterprise Informatization Project implementation has no shortcut, but, a good project team can let the Informationization project be quicker and more province's on-line.

A lot of people have talked about how to build the Information project team. I would like to focus today on the lack of a lot of project team "cooperation" problem. To play the project team advantage, it must have a core element of "cooperation". The author has set up a number of information management teams for different information projects, and believes that the team should really play its advantages, "cooperation" is essential.

Project team building should pay attention to "cooperation", mainly to consider the following aspects of the content.

One is: information sharing and communication.

The fundamental purpose of our CIO in building a project team for an information project is to eliminate the inherent estrangement between departments. People with experience in business management will have similar feelings. There is a kind of inexplicable individualism between the various departments of the enterprise, or "local protectionism". Even if their internal contradictions in how the interest, when someone to the department to give advice, whether well-intentioned or malicious, their muzzle will be consistent with the external, will temporarily put aside personal gains and losses. It is this attitude that leads to the inability to share information between departments and to communicate opinions.

Some information project team, seemingly agreeable, but secretly is "see others joke" mentality. If some people know that the solution proposed by a certain department does not work, however, as long as the impact on their own, will not be proposed. On the one hand do not want to offend, on the other hand also want to see others jokes. So the lack of communication of the project team, its existence will not promote the progress of the project, but also a drag on the hind legs.

So, when the CIO is assembled in the project team, the key is how to achieve information sharing and communication among team members. To this end, the author has taken the following measures, the effect is not bad.

First, the relevant personnel face-to-face communication, and not as a mouthpiece. I used to ask for an opinion of the time, is their own departments to confirm. The result is very poor. If the sales department said that the customer credit limit adjustment is the marketing department is responsible; then the author ran to the marketing department, the marketing department said that the business staff to apply, they carry out the feasibility analysis, and then have the Financial controller audit; The author ran to the sales department, the business staff said this is a written process, and now the actual practice is the marketing department developed And then the author went to the marketing department to confirm. So running around, a few days passed, still unable to reach a unified view. Later, the author changed the strategy, so that the heads of various departments to do down, close the door, they themselves to discuss a workable way out. They reached a unified opinion in less than one hours. Visible, so that there is not understand the business of the CIO as a mouthpiece, to confirm the relevant needs, that efficiency is how slow. Since then, the general problem, the author will let the relevant responsible person to communicate face-to-face.

Second, we should pay attention to the sharing of information. In fact, the Department of Management, Business control have a great commonality. I used to implement the ERP project, the sales department after repeated discussions, research confirmed the order price changes flow. After the process is confirmed, the author will share the process on the network. After the purchasing department saw it, it felt that the control process was good. According to their control methods, combined with the situation of their own departments, quickly developed a purchase price changes in the management process. Later, they all admitted that most of the "plagiarism" sales department management process. Otherwise, they will not "late hair", in a short period of time to complete the process of collation and development. It can be seen that if the sales department does not share the process, other departments are likely to do some repetitive work. At the same time, the sharing of information, other departments can also make some well-meaning views, so that the process more perfect. Therefore, this information sharing work, the CIO should be responsible for the completion. such as providing a platform for information sharing.

In addition, in the information sharing, we should also consider the information of the reusable use. For processes, let each department adopt word or professional process tools such as viso software, etc. So, for some useful information, other departments can use it directly. thereby improving the sharing value of information.

Of course, in order to promote the sharing of useful information, for the department or staff to make a share, but also to give certain rewards. Only then will they willingly share the information.

The second is: the project team as a virtual department to manage.

In order to improve the cooperation of the project team, the author's second tactic is to manage each member of the project team as a department, rather than as a representative of each department. Specifically, to achieve the following points.

The first is the overall assessment of the project team, rather than individual assessment. As the author was responsible for the implementation of the CRM project, a project team was formed. In order to improve the cooperation of the project team, the author canceled the previous method of assessment by department. But the project team for the assessment of the unit. A task is done and the whole team has a reward. If anything is wrong, I'm sorry, but all project team members are subject to punishment. This is called "Ishid, showered." This proverb is a derogatory term, but it has a new meaning here. In order to ascend to heaven, the chicken Dog will urge his master to complete the task, and see what the master has done is not perfect place, will also actively put forward their opinions. Instead of an indifferent attitude, stood watching the lively side. This is the way in which the fate of the team members is combined with other members to improve the cooperation of the project team.

Second, the use of information management tools to make the project team members of the work of transparency. In the project team management, I like to use a small software. This software function is mainly to track the work progress of employees. The author of each employee needs to complete the task in the software record and publicity. The employee completes each task and updates the software in a timely manner. In so doing, it is immaterial to form a new Department of representatives from various departments. They will keep track of each other's work, and other employees are at a glance at the work schedule and can arrange their work reasonably according to the work schedule. In a word, this can eliminate the estrangement between them and make it easier for them to cooperate with each other better in work.

Third: Don't let experience become a time bomb of employee cooperation.

In project team management, often hear employees say "this you do not understand, do not talk, do not pretend to know". It is true that the staff of the various departments work together, and some work professionally and fairly. So when some employees hear different opinions, they say so. However, our CIO should actively avoid this situation because it will affect the cooperation of the project team members. If you encounter problems you do not understand, do not ask, do not want to, then the information communication will not be discussed.

I have spent three years to find a solution to this problem, and have consulted a lot of management gurus. There is also some experience in this regard. Although it is not possible to solve the problem in a absolute way, it also has a role to play in the work.

First, for professional issues, can be appropriately narrowed down the scope of the discussion. When discussing payment terms, there is no need for the production or warehouse managers to attend. This problem is more professional, they do not have much use to participate, only will Manto, the opinion is difficult to unify. And let the direct responsible person sit together to discuss, can get more rational plan, and, also need not spend how much time. Therefore, the author suggested that for some more professional needs confirmation, as long as the need to find some directly related to the responsible person. Instead of opening an enlarged meeting.

Second, the importance of experience, but can not be subject to his limitations. When our CIO is in charge of informatization projects, there are always two classics in front of us. One is the industry standard solution, the second is the enterprise's current operating mode. As the head of the project, you need to weigh the two, which way you work. If the project owner was intimidated by the "empiricism" of the old employees, even if the information software was online, it would be difficult to make substantial improvements. The author believes that CIOs should guide the project team members and learn to compare the two working modes. Or you can synthesize it, get a new solution, or choose one of these ways of working. Instead of using "experience" to scare people.

The management of Information Project team is a new subject that our CIO encounters. To improve the role of the project team, the author believes that the CIO must play the whole body backwards, improve team members cooperation. The three recommendations above may help in this regard.