What People Need

The clinic from the previous article now knows it wants fewer missed appointments. That is a good start, but it is still not enough to begin building.

The next question is simple: who are we helping, and what exactly do they need?

Why This Matters

If you do not understand the need, you can easily build the wrong thing. Good software starts with a clear view of the people using it and the outcome they want.

When you understand the need well, you can make better choices about features, layout, timing, and trade-offs.

Core Idea

People do not usually ask for software directly. They ask for a result.

That result might be less waiting, fewer mistakes, a simpler process, or a way to finish a task without help.

Comparison

Asking about features	Asking about needs
“Do you want a button here?”	“What are you trying to do?”
“Should this be faster?”	“What is slow today?”
“Do you need more options?”	“What gets in the way?”
“Should we add a report?”	“What information are you missing?”

Worked Example

A clinic patient may want to book a visit quickly, reschedule easily, and get a reminder. A receptionist may want to avoid duplicate bookings and reduce phone calls. A manager may want fewer missed appointments and better reporting.

The patient wants convenience. The receptionist wants accuracy. The manager wants visibility. The same system has to support all three.

If you only design for one side, the software may become awkward for the others. Good product thinking means understanding the shared goal and the different needs behind it.

What To Ask

To understand a need, ask:

What are you trying to do?
What is slow or frustrating today?
What would a better result look like?
What gets in the way?
What would stop this from working for you?

These questions help you move from a vague idea to a specific problem.

Common Mistakes

Assuming everyone wants the same thing.
Asking only about features instead of goals.
Ignoring limits such as time, skill, or access.
Treating a guess as if it were a fact.
Forgetting that different people use the same system in different ways.
Turning a need into a solution too early.

These mistakes usually happen when the team is eager to build before they fully understand the situation.

Checklist

Do you know who will use the software?
Can you describe what they are trying to do?
Do you know what makes the task difficult today?
Have you identified different user needs?
Have you separated goals from solutions?
Have you checked for limits or constraints?
Can you explain the need in simple words?

Small Exercise

Pick one user and answer these questions:

What are they trying to achieve?
What makes it hard today?
What would a good result look like?
What should the software avoid doing?

If you cannot answer these clearly, the need is not well understood yet.

Summary and Next Step

Good software matches real needs. The more clearly you understand the people, their goals, and their limits, the better your decisions will be later.

If the need is vague, the software will be vague too.

Next, learn what success should look like.

What Success Looks Like