3

Techniques to KYC for Solution Design

 1 year ago
source link: https://dzone.com/articles/techniques-to-kyc-for-solution-design
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Know Your Customer for Designing a Solution

To provide any solution to your customer, it is important to understand the customer very well. This article covers some of the best practices and techniques for understanding your customer better to come up with a solution for the pain points of your customer.

1. Understand Your Customer's Business

Try to understand the type of business, strategy, history of the customer, and company’s vision and, going one step ahead, understand their customers as well. It will help you to derive the solution that is better for their ecosystem.

2. Type of Business or Segment

It is very important to understand the type of business or segment. It will help you define a solution in compliance with their segment. It would help you to define the USP of the customer. What is important to the market segment?

  • Cost-sensitive market
  • Time to market is more important than the cost or vice versa
  • Easy of use is more important due to the end customer software literacy
  • Scalability and Robustness are important to their end customer base

3. Understand the Customer’s Competitor

Before coming up with any solution, it is very important to understand the customer’s competitor and their offering in the solution. If you design software that overcomes the shortfalls of your customer competitor will be your USP to the customer

4. Customer News 

It is important to analyze the viewpoint of the customer’s end users. You can get a lot of information by going through the news of the customer. The news such as:

  • New customer acquisition 
  • Type of customers/business in their portfolio
  • Customer performance news
  • Any past incidents like platform outages, security threats, etc.

All this data will help while designing a solution for your customer. You can uncover information like future integrations, and analyzing their platform outages will give us information on their quality for the current systems (both software and infrastructure). 

5. Customer Relationship With Your Company

The customer might be already doing business with your company but with different business units. The type of relationship with your company could be financial, different products, etc. Your peer’s past experience with the customer would tell you a lot about their priorities, expectations, etc. It could also help to understand the challenges of working with the customer so that you can plan and overcome them through your solutions.

To collect all this information, there are some best practices to be followed. I have listed some of them:

1. Meeting With the Customer

The most important skill for collecting information from your customer is listening skill. Here is a checklist to follow 

  • Encourage the customer to the detailed conversations. 
  • Don’t interrupt often
  • Ask open-ended questions. For ex: 

Do you have any problem with your existing software? Instead of this frame question like: What are the pain points with your existing system/process/software?

  • Instead of just listening to what they want, better we find out what is the problem they are trying to solve. If we understand the real problem, we can come up with a better strategy and solution than the customer asks.

2. Ask Why

Asking why always open up a lot of information. Toyota Motor Corporation describes the same as the five whys technique. It is not about simply asking for every response from a customer. Rather plan those five why’s to the subject. Here is an example from the Wiki link.

An example of a problem is: the vehicle will not start. 

  1. Why? – The battery is dead.
  2. Why? – The alternator is not functioning.
  3. Why? – The alternator belt has broken.
  4. Why? – The alternator belt was well beyond its useful service life and not replaced.
  5. Why? – The vehicle was not maintained according to the recommended service schedule. (A root cause)

3. Capturing the Notes

It is important to capture the notes of the conversation through a whiteboard or some techniques like a domain model diagram. Walking through them would ascertain your understanding of the customer’s pain points.

4. Next Steps

Before closing your conversation, it is highly critical to define the next steps so that the expectations are set. What the customer should expect from us and when we are planning to do that. 

I hope these techniques will help to collect the most important information from the customer and come up with the best solution for the customer's pain points.


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK