DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Enterprise AI Trend Report: Gain insights on ethical AI, MLOps, generative AI, large language models, and much more.

2024 Cloud survey: Share your insights on microservices, containers, K8s, CI/CD, and DevOps (+ enter a $750 raffle!) for our Trend Reports.

PostgreSQL: Learn about the open-source RDBMS' advanced capabilities, core components, common commands and functions, and general DBA tasks.

AI Automation Essentials. Check out the latest Refcard on all things AI automation, including model training, data security, and more.

Related

  • Maximizing Developer Efficiency and Productivity in 2024: A Personal Toolkit
  • Elevate Your Terminal Game: Hacks for a Productive Workspace
  • Code Review That Matters: Tips and Best Practices
  • SSD vs. HDD: How the Choice of Storage Affects Developer Workflows

Trending

  • C4 PlantUML: Effortless Software Documentation
  • Code Complexity in Practice
  • The Impact of Biometric Authentication on User Privacy and the Role of Blockchain in Preserving Secure Data
  • Spring Boot 3.2: Replace Your RestTemplate With RestClient
  1. DZone
  2. Culture and Methodologies
  3. Career Development
  4. Techniques to KYC for Solution Design

Techniques to KYC for Solution Design

This article presents best practices and techniques in order to understand your customer well for coming up with a solution.

By 
Lokesh Raj user avatar
Lokesh Raj
·
Apr. 27, 23 · Opinion
Like (1)
Save
Tweet
Share
3.1K Views

Join the DZone community and get the full member experience.

Join For Free

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.

Productivity career

Published at DZone with permission of Lokesh Raj. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Maximizing Developer Efficiency and Productivity in 2024: A Personal Toolkit
  • Elevate Your Terminal Game: Hacks for a Productive Workspace
  • Code Review That Matters: Tips and Best Practices
  • SSD vs. HDD: How the Choice of Storage Affects Developer Workflows

Partner Resources


Comments

ABOUT US

  • About DZone
  • Send feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends: