Research That Earns Its Place in the Backlog

When I joined BlackSwan as the solo designer, the fastest way to lose a PM's trust would have been to treat research as a detour. So I framed it the way a product manager thinks: as risk reduction on the roadmap. BlackSwan serves two very different people — analysts running day-to-day reviews and investigators digging into flagged entities — and conflating them is how you ship a feature that satisfies no one. My research separated those jobs early. I learned that analysts live in triage volume and need speed and confidence, while investigators need depth, context, and the ability to follow relationships across entities. That distinction became the backbone of how we prioritized the five core surfaces. The clearest payoff was the Risk Engine. Talking to the admins who actually tune module weights, geographic rules, and PEP/sanctions thresholds revealed that nested configuration forms were hiding the consequences of every change. That insight reframed the whole problem from "build a settings screen" to "build an auditable decision system." Research didn't slow the roadmap — it kept us from building the wrong thing twice. For a PM, that is the entire point.