Methodology

How I work

Research first, always

In a market where products compete head to head, the difference isn't just in the interface anymore, it's in how well you understand your user before you draw the first wireframe. Here's the full process, step by step.

  1. Phase 01

    Discovery

  2. 01

    Research

    I start by understanding the real problem: talking to stakeholders, reviewing existing data, and defining exactly what we need to learn before touching a screen.

    Discovery notes · mockup pending
  3. 02

    UX research

    Then I go deeper with the actual users: interviews, surveys, watching how they behave today, what frustrates them, and what language they use to describe their own problem.

    User interviews · mockup pending
  4. 03

    Benchmarking

    In parallel, I benchmark the competition and adjacent products, not to copy them, but to understand what's already solved and where the real opportunity is.

    Competitive analysis · mockup pending
  5. Phase 02

    Design

  6. 04

    Notion as source of truth

    Every finding lands in Notion, my single source of truth. I use Claude connected via MCP to synthesize interviews, benchmarking, and data into one place instead of scattered docs and screenshots.

    Notion workspace · mockup pending
  7. 05

    Low-fidelity wireframes

    With the research organized, I start sketching by hand. Low-fidelity, fast, disposable, the goal is to get the structure and flow right before investing in visuals.

    Paper sketches · mockup pending
  8. 06

    High-fidelity

    Once the flow is validated, I bring in the final visual layer: typography, color, spacing, and the details that make it feel like a real product.

    High-fidelity UI · mockup pending
  9. Phase 03

    Validation

  10. 07

    User testing

    Before shipping, I test the high-fidelity prototype with real users, sometimes through an interactive prototype generated with Claude, to see where it breaks before it's in production.

    Usability testing · mockup pending
  11. 08

    Monitoring

    Once it's live, I set up monitoring with PostHog to see how it actually performs with real usage, not just in testing, and use that data to decide what to iterate on next.

    PostHog dashboard · mockup pending

Design is still where everything gets resolved, but without this step, there's nothing solid to resolve.