Quite often, colleagues complain about customers. Like, completely at the hands of strayed, scum! They do not want to do anything.
Of course they do not. Nobody wants. And some want to benefit their projects, but do not know how best to do it. Or they know, but they didn’t read the wrong book, so one harm from them. In general, there are different customers.
The first thing to remember: customers are actually useful (and not idiots, no).
Second: the customer is, in fact, the same resource as a programmer or designer.
Third: the main task of the project manager (we all know who
actually drives the universe
(devilish laughter) ) is to learn how to manage a customer as effectively as programmers.
')
So. The customer is, in fact, the same resource as a programmer or designer. It doesn’t matter whether it’s external or internal. The designer knows how to draw websites, the programmer knows how to make them work, and the customer understands (yes, today we will assume that he understands) what is the profit and the main meaning here. The customer also has useful resources like editors, on which, like on rabbits, you can test all interface innovations. You can also use them as a test text generator.
The main difficulty in managing the customer as a resource is that the customer in no case should know that he is a resource. Moreover, the customer must sincerely believe that the cause of all this movement, in fact, is himself. If it were not for him ... Yes, it's terrible to think what it would be!
It is in this state from the customer the most useful.
Customers (yes, almost all) suffer from a lack of attention. Do not write them long letters. The ideal letter consists of two lines. Maximum - out of three. And of these three lines (better than two) it should be clear what the problem is and what are the options for resolving it. In addition, the Ideal Letter to the Customer must answer the question “What is the problem with the choice of a decision” and “When the decision needs to be made”.
About the decisions. You, of course, know better what the customer needs. Of course, you have already thought through all the options, took into account all the risks, considered the resources, discarded the foolish ideas and set the task in development (because the deadline, as always, “yesterday” and there is no time for desalinization).
A brilliant letter to the Customer is in the same three lines (preferably two), carefully and imperceptibly leads the customer to the choice of the right solution.
About the deadline. A normal person wants to work only if this work prevents a universal catastrophe. And even a normal person will not do such a responsible job on time. And the customer is a person (no, well, really!). Therefore, if you need an edge by Friday, write a Hysterical Letter to the customer about Monday. At best, you will receive them by Wednesday (if you’ve got a good deal on Monday and Tuesday). At worst - by Friday.
About hysterical letters. A hysterical letter may consist of one word or two pages (or four and a half paragraphs, it does not matter). But this does not cancel the first rule of the fight club - the first three lines should contain a maximum of useful information. Since, as a rule, Hysterical Letters describe quite serious technical problems and require the customer to make informed decisions, the first three lines should a) make the customer understand that the galaxy is in danger b) encourage him to continue reading and making an immediate decision.
As a result of clandestine studies of many years, the reference phrase was derived, with which any hysterical letter should be started: “Colleagues, you have problems.”
If you have a very trusting relationship with the customer, the word “Problems” can be replaced with any other, more capacious word.
It is important, however, to keep the pronoun “you”. The customer does not always identify himself with the problems of his projects. Some people mistakenly believe that the problems of “programmers who do not do anything again!”.
And, yes, Hysterical Letters are most effective if used rarely. And it will turn out like in a fairy tale about a boy and wolves.
About the tasks. Do not be afraid to set tasks for the customer. He is a resource (only, shhh! Anyone!), He must comply with them. It is, after all, in his own best interest. Set tasks just as you set them for a programmer. You do not ask him: “Write me a code, my friend!”. And why do you ask the customer to tell you why in general all this is necessary?
The task should be
clear, measurable, consistent, realistic and time- bound (ehegei! Well, you are managers!).
About the language. Customers don't know a damn about technology. And they should not. When you tell them “the faddie doesn’t shout” they can’t link it to “the pictures are not displayed”. They get hysterical. They shout "It broke!". Talk to them in human language. Or say something soothing to them like “You better not know it. Everything's under control. Now everything will work. ”. It helps, really.
About age. Treat customers like children. Teach them. Share knowledge. Allow to invent names for servers.
Customers are cool. True. And it's so great when one day you hear on the phone: “The editor cannot go into the back office ... Did you have a session server again?”.