Start with the signal. Name the uncertainty.

Analytics, customer asks, strategy, and founder vision are not interchangeable. I separate evidence from assumptions, define the behavior that needs to change, and make the riskiest unknown visible before a team commits to a feature.

Map what happens before, during, and after.

I design across actors, permissions, states, dependencies, failure, and recovery. Then I create materially different product directions and expose their trade-offs before interface decisions harden into architecture.

Turn ambiguity into a buildable decision.

I create enough structure for product, engineering, data, operations, and leadership to make the same decision. Scope is explicit. Rejected alternatives stay legible. Handoff describes behavior and consequences, not only pixels.

Shipping starts the evidence cycle.

I stay with the work through implementation QA, instrumentation, and outcome review. What we learn becomes the next signal, so the organization gets better at choosing, not just producing.