Translating Needs into Design Requirements
By now, your team has framed the problem, explored possibilities with How Might We questions, and written a needs statement. So what comes next?
The next step is one small but important refinement. A point-of-view statement takes what you already know about your community partner and their need and adds the deeper insight that helps bring the challenge into sharper focus. That insight helps reveal the practical requirements any good solution will need to meet.
Where you are in the process
At this point in the Define phase, you are moving toward a fuller synthesis of what you have learned.
• Problem statement → names the challenge clearly
• How Might We question → opens up possible directions
• Needs statement → identifies what your community partner needs in order to make progress
• Point-of-view statement → adds a key insight from your community partner’s perspective
What a point-of-view statement is
A point-of-view statement is a clear, actionable phrase that combines the community partner, the need, and a key insight from your empathy research.
That insight helps explain the challenge as your community partner experiences it. It adds depth to the needs statement and gives your team a more focused design lens.
Returning to Maria
Let’s return to Maria.
Here is the needs statement we developed in the last post:
Maria needs a way to obtain affordable fresh groceries near home after work because her current options do not fit the time and budget pressures she faces each evening.
That is already a strong statement. It names the community partner, the need, and why the need matters.
So what does a point-of-view statement add?
Finding the insight
The insight is not just another fact. It is a deeper understanding of what makes the situation hard, meaningful, or revealing to your community partner.
That insight comes from your empathy research. You draw it out of what you learned from Maria’s experience.
In Maria’s case, the insight might sound something like this:
• the short evening window between work and family responsibilities leaves her too little time to act on her desire to feed her family healthy meals
• her challenge is not just food access in general, but the mismatch between healthy intentions and real-life constraints
A point-of-view statement builds on what was already present in the empathy data and the needs statement. It brings that deeper understanding into clearer focus.
Writing the POV statement
Here is a helpful way to draft a point-of-view statement:
[Community partner] needs a way to [need] because [insight].
You may notice that this looks very close to the needs statement format. That is okay. In practice, the two are often very close, and some design thinkers treat them almost interchangeably.
In this series, we are making a small distinction: the point-of-view statement adds the deeper insight that helps frame the challenge more sharply.
For Maria, a POV statement might sound like this:
Maria needs a reliable way to get affordable fresh groceries after work because the short evening window between work and family responsibilities leaves her with too little time and too few nearby options to act on her desire to feed her family healthy meals.
Now compare that with the earlier needs statement:
Maria needs a way to obtain affordable fresh groceries near home after work because her current options do not fit the time and budget pressures she faces each evening.
Both statements are useful. The difference is that the POV statement brings in a richer understanding of Maria’s lived situation. It gives the team not only the need, but also a clearer sense of how to frame the challenge for design.
What the insight reveals
Once the team sees the situation more clearly, it can identify the practical requirements any realistic solution must meet.
In Maria’s case, the insight suggests that any workable solution must:
• fit into a very short evening window
• be close to home or work
• stay within a tight budget
• compete with the speed and convenience of fast food
You uncover these design requirements from re-examining your empathy data.
This is an important distinction. The POV statement helps the team understand the situation more deeply.
Why this matters
A point-of-view statement shows the team the requirments what any good solution must fulfill.
It helps the team frame the right challenge for ideation. It keeps attention on the real person, the real need, and the real situation. It also lowers the risk of drifting toward shallow or generic solutions.
That matters because teams sometimes solve the wrong problem. They respond to the surface issue without fully understanding what is driving it. A stronger point of view helps prevent that and makes their ideas more realistic and useful.
Common mistake to avoid
One common mistake is to treat the point-of-view statement as a completely different tool from the needs statement.
It grows out of the needs statement. The main difference is that it adds the deeper insight that helps the team frame the challenge more thoughtfully.
Another mistake is to confuse the POV statement with the design requirements that come from it. The POV gives the insight. The requirements are what that insight implies for design.
Try this now
1. Write your current needs statement.
2. Look back at your empathy data.
3. Ask what deeper insight helps explain why this need matters.
4. Revise the statement so it includes the community partner, the need, and that insight.
5. Then ask what practical requirements any solution must meet because of that insight.
Takeaway
The point-of-view statement does not replace the needs statement. It builds on it.
It takes what you already know about your community partner and their needs and brings it into a sharper, more revealing frame. That insight shows your team the practical requirements a strong solution must satisfy.
This makes the next step, Ideation, more focused, more human-centered, and more likely to produce ideas that actually fit the situation.
*********************************************************************
If you’re interested in more about the design thinking process, check out my book Design Thinking: A Guide to Innovation.
I generated the image of the design team with ChatGPT.