CTO at Mad Devs
The work of IT teams is done for the people who are paying to them, i.e. clients. Even if you are working on an internal product, everything has its customer and buyer.
There is a saying “He who pays the piper calls the tune”. However, there is a limit, and every request must be considered wisely. Blindly following demands of inexperienced IT stakeholders isn’t a good strategy. It might result in the ludicrous final product, which is conflicting with the quality and professional skills your company offers.
It is important to build a long-term relationship with a customer, who has the possibility and willingness to pay regularly and steadily.
A good customer will even increase the contract amount with the growth of the project. This can only be achieved if your work brings value and revenue to the customer.
Below I present a list of common principles of work communication with clients. Following them will allow you to build a successful product. These guidelines are applicable to all customer-facing roles in software development.
This means that you have to put yourself in customers’ shoes and discover the motives of their requests and goals. Motives can be obvious or hidden (see the Mom Testbook for more details).
If you feel that you don’t have enough information to get a full scope of the task — you need to ask for it. You are about to invest your time in solving these problems. You need to understand all the aspects before setting priorities. Everything has to be completely transparent. If you have received a task or a user story and spot contentious issues or gaps, you have to make sure to fill them in. Try to get the full story to be on the same page with your client.
You and your customer look differently at tasks and their solutions. The client may talk about one thing, think about another one, and expect something completely different. By using customer affinity, you will be able to speak one language with your customer and use it for creating a detailed plan for your entire team.
Successful implementation of customer affinity practice enables you to see the business concept.
Most of your clients are using your services to gain profit for their businesses. However, not always they are following their own goals. Sometimes their tasks are not business-focused and even create obstacles for making more money. For example, the client’s acquaintance advised them to add a new feature, or they are asking to create a reporting tool, which they will never use. Features with low or zero business value may take your team a bulk of time. All these issues must be raised, discussed, and pointed at. The majority of the clients are sensible people, so they will see that your arguments make sense.
2. Don’t be overly straightforward. Sometimes clients keep insisting on useless tasks. “I want it this or no other way!” In such a case, try to reveal the hidden motives of your customer by asking questions. Why the task is so necessary to implement? Most often your clients know end-users better than you, and you need to rely on their expertise.
A compromise may be to release a ‘feature MVP’ on production and receive first feedback from end-users. If the experience is negative, the customer will admit their mistake. Next time they will follow your advice. However, if the user feedback is positive, you have partly lost your credibility in the eyes of the customer, and you will have to follow their recommendations more often in the future.
Most of the companies are carefully choosing their clients. Therefore, if you have partnered with someone, you have to remember the following:
This is especially important in establishing relationships with remote clients. Here I would like to provide some useful extracts from the book “Remote. Office Not Required” by Jason Fried:
Nevertheless, you have to remember that from the moment you signed the contract you and your client are one team. You two go hand in hand to your mutual goal. That’s why establishing a strong bond with a customer should be a priority for the entire technical team. Being respectful, considerate, always open-minded, and available for a discussion is the foundation of a long-standing partnership.
Besides, it is essential to ensure that your client is feeling involved and present in the project despite the distance that might keep you apart. A trustful and strong relationship with the client is key to a great experience of working on the project.
Previously published at blog.maddevs.io.
Level up your reading game by joining Hacker Noon now!