What the customer really wants

by Jun 1, 2023

You need to listen to what the customer wants.

But you also need to read between the lines, to find the real solution.

How to read between the lines?

1️⃣ customer talks in viable solutions that he can think of, instead of the real problem or need.

2️⃣ customer talks about optimizing has part of the process, but never about the process itself.

3️⃣ customer talks from the perspective of his knowledge of current tech. Often there is more possible than he knows.

4️⃣ customer tries to automate, but not taking advantage of the benefits. Copying a paper form to a PDF is digitalization, but that isn’t the automation that you want.

5️⃣ question everything. use the 5-whys technique to get a deeper understanding of the problem or need.

How do you read between the lines?

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

SpecFlow: Great concept, flawed execution.

SpecFlow: Great concept, flawed execution. SpecFlow, a BDD framework designed to make writing scenarios a breeze for requirement analysts. The problem: It falls short of its promise. ❌ The reality? Analysts rarely, if ever, write the specs themselves. Instead,...

read more

What if…? Production has a Staging slot.

What if...? Production has a Staging slot. Staging or QA environment needs to be the same or as close to production as it can be. Preferably, you want to restore a recent backup 💾 from Production as Staging and then deploy your changes 🔄. Kudos 👏 if you've fully...

read more

UUID v7 coming in .NET 9

UUID v7 coming in .NET 9 For those that didn't know, you can create Guids in different ways (algorithms). System.Guid supports UUID v4 out-of-the-box, the most used version. UUID v7 is now added, which creates Guids based on the current time. This means Guids can be...

read more