FAQs

I operate at a Principal Product Designer IC level. I own ambiguity-heavy problem spaces that span product strategy, system architecture, and execution. I partner directly with Directors, VPs, and the CEO, and my decisions influence roadmap bets, resourcing, and whether initiatives move from exploration into funded, shipped work across multiple teams and platforms. My scope is defined by consequence and ownership, not just by title.

I specialize in pre-roadmap, contested problem spaces where direction is unclear, constraints are evolving, and conviction does not yet exist. I’m typically brought in before a solution is agreed upon to define what the product should be, why it matters, and which paths are worth betting on. These are moments where the organization risks moving quickly in the wrong direction, and the work is less about execution and more about establishing clarity, tradeoffs, and belief.

My work has driven measurable outcomes across both new businesses and existing platforms. I’ve built a standalone AI-first product from the ground up, taking it from zero to a validated, legally approved, fully spun-out application with category-level implications. In parallel, I’ve improved core metrics at Hinge, Meta, and GoDaddy by designing systems and features that increased adoption quality, engagement depth, and user trust. In multiple cases, design clarity was the deciding factor that moved initiatives from stalled exploration into funded, shipped work with real business impact.

I create leverage by changing how teams can operate without me. I build decision frameworks, system primitives, and shared artifacts that make quality and tradeoffs explicit. I’ve also built live AI prototyping systems and internal tooling that allowed designers, product managers, and engineers to test real ideas in real product conditions instead of debating hypotheticals. These systems persist beyond individual projects, enabling faster, higher-quality decisions across teams and over time.

Yes. When alignment is missing, I make ambiguity concrete by pairing early prototyping with clear vision and purposeful storytelling. I don’t just show what’s possible, I frame why it matters, what tradeoffs are being made, and what future the team is actually committing to. I anchor discussion in observable user and system behavior rather than opinion, then use narrative to connect those signals into a coherent direction leaders and teams can rally around. I’ve repeatedly seen abstract debate turn into forward motion once people can both experience the problem and understand the story it’s telling. Momentum follows when uncertainty becomes legible and the path forward feels intentional enough to commit to.

Yes. The clearest example is building Overtone end to end, from first principles through discovery, system design, validation, legal review, launch, and spinout. Beyond that, across my career I’ve owned everything from individual features to full products, which gives me a clear understanding of what it takes at each level of scope. I’ve led work from early framing through execution and iteration, navigating legal, policy, and technical constraints along the way. My ownership doesn’t stop at shipping. It extends into learning from real usage and evolving the system based on what actually happens, not what was assumed during planning.

I raise the bar by making quality explicit and repeatable. I mentor designers using real work and real decisions, not abstract advice, and I help teams connect design choices to product and business outcomes. I also create and improve critique environments so feedback is sharper, more actionable, and grounded in shared standards rather than taste. Designers I work with leave with stronger judgment, clearer expectations for quality, and more confidence operating in ambiguity.

My craft is grounded in interaction depth, system coherence, and execution quality. My training at Pratt gave me an intuitive sense of taste and composition that’s difficult to teach, and I pair that with rigorous systems thinking. I design systems, rules, and primitives so decisions scale well and still feel considered in each instance. I’m comfortable operating from concept to pixel, across complex flows, edge cases, and real production constraints, and I ship what I design.

This feels like a natural transition point. The class of problems I'm here to solve, turning ambiguity into clear, shippable systems and proving that AI could be applied responsibly in real products, has moved from contested to established. At the same time, the market has shifted. The kinds of AI-first, systems-level product questions I specialize in are no longer exploratory, they’re now core to how companies differentiate and build trust. That combination makes now the right moment to move upstream again, where new product directions still need to be defined.