Virtual customer management by Project Manager

The Project Manager often thinks that the project is postponed due to the customer's "problem". For example, the customer needs to confirm the completed part, and the customer needs to confirm the requirement analysis. Once the customer does not confirm the request, the project cannot be continued or extended.

Here we will talk about the "customer's Problem". If the customer thinks it is indeed his own problem, it is not a problem. The customer will naturally agree to the extension or payment, but most of them are customers who do not think they are their own problems. This is really a problem.

For example, if the customer needs to confirm and the customer does not confirm, the customer does not agree that the confirmation is not included in the plan, he didn't plan to reply to your questions this day. Maybe he needs a date and travel. Who knows? Many of the reasons for this problem are that our project manager did not let the customer know. This day, we should answer your question instead of an appointment, so the delay or extra payment is the price of love. The customer has the right to choose. What about him? I used thousands of bucks to change my girlfriend. It's worth it.

However, if you didn't let him put your answers into the plan in advance, and you asked him to answer questions during the appointment, the customer would become more and more disgusted, just as you were kissing your girlfriend, let's say, wait a moment and answer a questionnaire first?

 

To solve this problem, you need to regard the customer as part of the project's success and as an important part. You need to regard it as a resource, such as a pot of flowers during programming, you write a program to chat with you (it seems impossible, haha), but you really want to regard it as an element of project success, put it in the scope of your "management" (as long as you manage the facts, do not care about the name), so it is called virtual management customer.

With this consciousness, we began to set up "arrays". "arrays" are the methods to win battles. For example, to fight "The Battle of Chibi", we need Huang Gai and Zhou Yu. If there are no such two people, then you will ask the boss. If you don't give it to you, you won't fight. No, I rely on it. The boss must have a solution. There are so many Chinese talents, the boss can fix it within one week.

If your customer understands technology and management, you can use it as "zhao Yun" and beat the vanguard. If your customer is Alibaba Cloud, you cannot give it to Cao, find "zhao Yun". In short, place the customer in the battle.

Now the customer is yours. It's easy for your people to do it. Who will let the customers have a problem?

Too much nonsense. Now let's get down to the truth and solve the problem at the beginning.

1. List project plans, such as iterations. Remember to include customer feedback in the plan.

2. assign a task. Remember to distribute the task to the customer.

3. At this time, the customer will make their own plans (of course, We only care about our part, and we will not care about dating at any time)

4. The plan must be tracked.

5. Update the plan

6. Go back to the second step, for example, repetition...

I think the above method cannot definitely avoid the delay, but it can only be minimized. Customers who have their own tasks will naturally change their appointments to other days, but they are not necessarily. After all, there are two sides on the appointment. No matter how customers choose, it has no impact on us, maybe the customer chooses a date and is willing to postpone the payment and pay more, so why should we play the game for two days (CS)? Why can't I get it?