Approach

My work sits in the messy middle of products — the places where logic drifts, decisions stall, or constraints shape the wrong outcomes.

How I work best

  • Clarity: I thrive in teams that value clarity over consensus and are willing to confront structural problems before aesthetic decisions.
  • Evidence: I work well with engineers who appreciate evidence and are willing to change direction when the data points somewhere new.
  • Understanding: I need time to think, map systems, and reflect. I won't sacrifice that for performative urgency.
  • Collaboration: I'm more embedded in product, engineering, and operations than in the design community. That's where the real work happens.

Operating principles

  • Clarity in messy spaces: I'm comfortable stepping into work that's unclear or has drifted over time. I map what's actually happening, surface the real constraints, and help teams see the shape of the problem so we can make grounded decisions.
  • Steadying teams under pressure: When things get noisy or uncertain, I stay calm. I help teams focus on what matters, reduce unnecessary churn, and keep decisions moving without drama.
  • Practical decision-making: I avoid big reinventions unless they're needed. I focus on the next clear step, the part that unlocks progress, and the decisions that make the product easier to use.
  • Fixing the part that matters: I don't redesign for the sake of it. I look for the part of the flow that's actually causing friction and fix that first, keeping the rest of the system intact.
  • Supporting people with grounded feedback: I give feedback that's specific, actionable, and rooted in real examples. My aim is to help people grow and make better decisions, not to perform expertise.

Tools and methods

  • Figma: Design and prototyping
  • Miro: Systems mapping, workshop facilitation, research synthesis
  • Jira/Confluence: Managing work and documentation
  • Adobe Illustrator: Vector illustration, icons
  • AI tools: Prompt engineering, prototyping with Claude, workflow integration
  • User research: Surveys, workshops, user interviews
  • User testing: Moderated and unmoderated
  • HTML/CSS: Working knowledge, plus systems understanding of Next.js, React and Tailwind