I spent years in design roles that never quite fit. I could execute—wireframes, user flows, feature specs—but I kept pulling upstream toward the questions that mattered more: What problem are we actually solving? What are we not saying about the tradeoffs? What happens if we're wrong?
Eventually I stopped trying to make design work and became a researcher. At Amazon, I spent four years working on healthcare benefits for 1.5M employees—systems where ambiguity has consequences because people make irreversible decisions based on what we surface. I ran research that stopped a leadership-backed marketplace concept in its tracks, reframed benefits enrollment from usability to decision confidence, and showed that AI adoption wasn't constrained by capability but by the absence of accountability structures. The work shaped backend architecture, reprioritized roadmaps, and forced teams to defend their assumptions with evidence instead of conviction.
I write about how decisions get made under uncertainty, what research is for when it's not just validation, and what happens when systems encode values we haven't examined. I'm also building BetCheck—a tool that tests whether product assumptions are actually defensible or just well-packaged intuition.
An in progress diagnostic tool for decision confidence to help PMs evaluate if their product bets are defensible
Essays on decision-making, research strategy, and system design
Case studies on shaping product direction under uncertainty