Skip to content
Artwork for Programming Tech Brief By HackerNoon
Programming Tech Brief By HackerNoon · Thursday · 7 min

The Poirot Method: How Designers Can Investigate Ambiguous Problems

This story was originally published on HackerNoon at: https://hackernoon.com/the-poirot-method-how-designers-can-investigate-ambiguous-problems. A product designer uses a detective’s approach to ambiguous briefs: gather evidence, question assumptions, identify motives, and define success. Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #ux-research, #product-discovery, #ux-problem-framing, #assumption-mapping, #ux-success-criteria, #evidence-based-design, #hypothesis-validation, #the-poirot-method, and more. This story was written by: @leravyrva. Learn more about this writer by checking @leravyrva's about page, and for more stories, please visit hackernoon.com. After an overwhelming early-career experience, the author learned to approach unclear product requests as investigations: collect evidence, understand business motivations, challenge assumptions, and agree on what success means.

0:00-7:51

transcript

No transcript — this publisher did not publish one.

show notes

This story was originally published on HackerNoon at: https://hackernoon.com/the-poirot-method-how-designers-can-investigate-ambiguous-problems.
A product designer uses a detective’s approach to ambiguous briefs: gather evidence, question assumptions, identify motives, and define success.
Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #ux-research, #product-discovery, #ux-problem-framing, #assumption-mapping, #ux-success-criteria, #evidence-based-design, #hypothesis-validation, #the-poirot-method, and more.

This story was written by: @leravyrva. Learn more about this writer by checking @leravyrva's about page, and for more stories, please visit hackernoon.com.

After an overwhelming early-career experience, the author learned to approach unclear product requests as investigations: collect evidence, understand business motivations, challenge assumptions, and agree on what success means.

links13