Manuals / Design Thinking / Chapter 3

A · Understand · beginner · ~30 min · Chapter 3 of 9

Define: point of view

Turn research into a POV: user + need + insight. A good problem statement focuses the team; a bad one is a solution in disguise.

Path progress
33%

Step 1 of 1

POV + HMW

[User] needs [need] because [insight]. Then: How Might We …?

POV + HMWDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →POV + HMWdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Example

POV: On-call engineers need a faster way to find the last known-good config
because they waste critical minutes grepping Slack during incidents.

HMW: How might we surface last-known-good config at the moment of triage?

Do this now

Write 1 POV and 5 HMW questions. Vote the top 2 HMWs.

Was this step clear?
Chapter learning outcomes
  • POV statements
  • HMWs
  • Problem vs solution

Clear these before you leave