The Point of View (POV) is a focused problem statement that distills the findings from the Empathize phase into a single sentence. The structure reads: [User] needs [need] because [insight]. This sentence defines which problem the team will solve — not the solution itself. A good POV is specific enough to provide direction and broad enough to allow for different solution paths.
An example: after user observations, a team formulates the POV “Maria, a project manager with eight meetings a day, needs an instantly graspable project status, because she has at most three minutes for updates between appointments.” This sentence is actionable: it rules out comprehensive dashboard solutions and opens the space for minimalist formats. A poorly formulated POV like “Maria needs a better tool” would be too unspecific to meaningfully guide ideation.
The POV comes from the Design Thinking process at the Stanford d.school and forms the bridge between understanding and generating ideas. The most common pitfall: teams formulate the POV as a disguised solution rather than an open problem statement.
Apply methods, don't just know them. View trainings and workshops
