{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"The Poirot Method: How Designers Can Investigate Ambiguous Problems","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/7ac5c4ba\"></iframe>","width":"100%","height":180,"duration":471,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/the-poirot-method-how-designers-can-investigate-ambiguous-problems.\nA product designer uses a detective’s approach to ambiguous briefs: gather evidence, question assumptions, identify motives, and define success.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            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.\nThis story was written by: @leravyrva. Learn more about this writer by checking @leravyrva's about page,\n            and for more stories, please visit hackernoon.com.\nAfter 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.","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}