See an article about software implementation very good ~

Software implementation can be said to be a decisive link in the main line of software Product services, the success of software cannot be separated from implementation. What is the implementation of success? I think it is to let users really use, so that users are satisfied, the success of users is also the success of software companies. It's just that software can really be used, but it's not as easy as it might seem. For the unsuccessful implementation of the situation, through a number of reports and my study to jinnan this is often happening, and the proportion is very high.

In view of the importance and difficulty of implementation of the above, we are no longer simple installation and commissioning, user training, initialization, commissioning support and so on. Because, the implementation process will encounter a variety of problems, different customers may encounter different problems. Our software like daughter-in-law to see in-laws, in-laws are always very picky, always say you this bad that bad. But in spite of the picky in-laws, but we still see! Does the saying say "ugly wife also see in-laws"? Besides, we are not so ugly. This is going to be about how to see the process. In fact, for a software, the initial problem is such a breed. At the beginning of the market, the good attractive things to the customer to instill, if in the presentation of one or two of bugs, I believe that the sales staff can always calmly before the customer has not yet responded to the day. Sales staff always promise a good function, performance and quality, triggering a great customer interest, all smooth, the manager will soon be able to sign the purchase and service contract, so, for software companies, the most important thing seems to have been almost. Then, the software company sends the implementation personnel to the customer on-site installation and demonstration, please note, this time is the product most vulnerable time. Implementation personnel to the whole set of products to customers, and finally, ugly daughter-in-law to uncover the veil let in-laws see. At this time, the problem is so many, the moment is very frustrating. So, even if the problem is many, we need one to solve it. This requires that our technical staff must have the following qualities to cope with, so that customer satisfaction.

First, the implementation of personnel should have basic network diagnosis and analysis of the problem of the ability, at least to make a more accurate judgment of the problem. Because there are a lot of unexpected problems that you may encounter during installation. For example, server and network environments are more demanding than expected, conflicts with other applications, and even anti-virus software. For problems with insufficient machine configuration, you can make a list and submit it to the owner of the client to decide.

Secondly, we should have a corresponding solution to different problems. Sometimes the speed of our client software is really embarrassing, sometimes user login will take a long time, resulting in customer's first impression of software is slow. Even a low-level error such as a timeout will pop up. For such a problem, should start from two aspects, should pay attention to the customer hardware environment factor, explain to the customer. should also determine whether the software products have related problems, of course, this we understand in the mind, do not let the customer know, we should feedback back to the company to improve.

In addition, to learn and customer leadership contacts, leadership is leadership, and ordinary staff is different. First of all, the leader does not have the patience to see the specific features of our software, but he needs to hear or see a very general display, then we should be good. Perhaps we are often unable to answer certain questions of leadership. For such a problem, we must first understand the real intention of the leadership, which is also an important source of software requirements. The use of software for the leadership is nothing but to strengthen management, do not use the software, the leadership of a lot of data may not know, when the employee's work data into the software to come, the leadership should be a great help. Other countermeasures include letting low-level employees say yes to our software, and obviously the leaders are more willing to trust their own unit of judgment. In addition, our other answer can be that the software will be gradually improved after use.

Only learn and customer leadership contacts not yet, the most important also and customer staff get along well, the front also mentioned the leadership more willing to believe their own judgment. Starting from the installation, some users may not cooperate. In the training class, most of the staff who are likely to come to the meeting will boycott the software. The reason is very simple, the use of software, increase their workload, China is a man of the society, management is vague imprecise, the staff are strictly managed to make them can not get used to. And people are inherently inert. Therefore, it is conceivable that users will point out a lot of their business is different, the software may not be able to solve things, all these, to prove that the software is not available. In this case, we only try to show some of the features of the software, tell him what the function can do for him, what effect, and that function can help him solve what problems. Here you do not need to be nervous, certainly do not quarrel with the customer, not a clear, here we can use the rare Lake Tu. In fact, some users just grumble, and perhaps they know that the leader will force them to use.

Finally, and most importantly, we want to have project progress, priority level, quality concept and service awareness. We should start with the following aspects:

First, the comprehensive planning, step implementation, focus on breakthrough, benefit priority. At the beginning of implementation, should stand in the customer's position, for information-based construction, to assist the overall planning, in order to avoid the implementation process of detours. Consider the product as the most suitable application solution for your customers. Under the premise of the overall planning, it is possible to plan for the step-up implementation. The value of stepping into the implementation is reasonable distribution, when you run, if each lap as a milestone, then the psychological burden will be reduced, the implementation of the work at this point is similar. Set milestones for each step as you step through the planning process, which breaks down the problem and achieves more sense of accomplishment. One step at a time success, the success of the previous step, can be timely leadership of the nod, and encouraged the implementation of the next step. Key breakthroughs are also one of the essentials of software implementation. If you understand and take into account the current customer's problems, seize the focus of implementation, then the likelihood of successful software implementation will be greatly increased.

Second, work Management: Planning, recording, discussion and summary. We should develop this kind of work habit, that is, plan beforehand, record in process, summarize afterwards. This point I am using the total notebook computer feel, in fact, Ding always do everything is a text plan can be found, this way of working can make people not panic, not absent-minded. Everything is pre-set, not pre-waste. In advance, careful planning and preparation should be made to understand the client, prepare for the worst, take into account the most likely risks in the implementation, design the implementation priorities, and so on. In the early contact, that should take into account the direction of the management of the other side, such as understanding the leadership of management ideas and tendencies, mainly to solve the problem, the customer's internal resistance, the quality of direct users, and so on, so that the ground habitant, to achieve better results. On the other hand, to their own software products also need to know, which also includes the advantages for competitors, product weaknesses and so on.

In the work process should do a good job record, the problems encountered in time to fill in the problem report, and customer exchange documents, plans, etc. should be unified management. In addition, if you have a record of the entire work process, it should be very easy to summarize after the implementation is completed. What is more successful, where does not do enough, what is the reason, how to improve and avoid in the future, and so on.

Third, to deal with the user's relationship, user satisfaction, the success of software implementation is just within reach. This is not much to say, also mentioned in the front.

We should look at our products in a correct way. There may be a lot of people who say that this product is very abusive, even so, we must also show a great love for their products. If even you feel that the product is not good, users will naturally feel that the product is very bad. The quality of software products should be excellent, but there are some problems that have not been solved well. If you're having problems, you don't have to be nervous, you can sort the issues first, and then consider a variety of strategies to solve, such as some issues that can be improved in the next release, and so on, regardless of how it should be agreed with the user that the software is only a part of the customer's problem, and it is impossible to cure all ills.

Make use of all available resources, such as networks, companies, and colleagues. In the case of resistance, support can be provided to the company for assistance. Customer's reasonable request, to timely pay the company changes, this is to promote our software to further improve one of the most effective way. For example: Our health care has not been improved this year to make him more humane, in the market to occupy a clear advantage in sales, his improvement from there, that is, from the customer's needs.

The sixth to third Point Software, seven points management, more than data, this is I recently seen from the online ERP implementation of the famous principles. The main idea is to protect the good data and ensure its correctness. This is also an important principle for the initialization of any implementation. In the initial time, that is, the user design good data backup and recovery means to prevent any accidental occurrence.

Seven, the user after training will have some basic operations, but the real use of time, will certainly encounter problems. This is where we have already put the user on the horse, and we can still see he can control the whole horse, then we will give him a ride, that is, we could also help him do more things, perhaps in the training content, there are other software features. In this way, we demonstrate that our service is of high quality. In addition, the importance of "lifting the horse, giving a ride" is also to promote the formal operation of the software. Many users will not be accustomed to using software to handle work transactions. After all, it's not easy to change habits. On the one hand we can through the other side of the leader to channel, on the other hand can also be listed first, a solution, like to untie a lot of knots. While the user is in use, we look for problems and make improvements. In the implementation of the Cili I realized this point, appropriate timely processing part of the demand, can make the implementation of the smooth progress, and in the negotiations with the other side of the easy display of sincerity, to achieve a reasonable favorable section. Otherwise it will be stuck in a certain part and can not go on smoothly, the final Cili is very satisfied, and thus brought the Luxi of another new project.

In short, the user acceptance through, for our implementation personnel, should celebrate for themselves. The acceptance report is our answer. At the same time, do not forget to summarize, software implementation, always gains, there is a worry about the same, this is the same as our life, is not it. Finally, I give the following sentence to all the implementation personnel, you can think so, you can do this, and do:
To be able to fight, war can win!

See an article about software implementation very good ~