Skip to content
Oren Shahar

About

Curious about people. Rigorous about outcomes.

I'm Oren, a product designer who works where user needs, business goals and technical constraints meet. The best design work rarely starts in a design tool. It starts with a good question.

Focus
Product design and UX research
Works best
Embedded with product and engineering
Your portrait

My story

Why I do this work.

What draws me to product design is a simple question: why do people struggle with things that should be easy? Before I design anything, I want to understand the person on the other side of the screen, the moment they're in, and what they're actually trying to get done.

Along the way I've learned that great products come from great decisions, not great deliverables. So I spend as much energy on framing problems, aligning teams and defining success as I do on interaction details and visual craft.

I do my best work embedded with product managers and engineers: sharing work early, inviting critique and treating every launch as an experiment. I'm comfortable leading through ambiguity, and just as comfortable being wrong, as long as we find out quickly.

Principles

What I believe about good product design.

  1. Fall in love with the problem

    Solutions are cheap. A deeply understood problem is what makes a solution good.

  2. Evidence beats opinion

    Research, data and real behavior settle debates faster than seniority or taste.

  3. Make trade-offs visible

    Every decision gives something up. Naming what, and why, builds trust across the team.

  4. Simple is harder, and worth it

    The best experience usually has fewer steps, fewer choices and fewer surprises.

  5. Outcomes over outputs

    A shipped feature is a hypothesis. Success is the change it creates for users and the business.

  6. Design is a team sport

    The best ideas come from working closely with product, engineering, research and the people we design for.

Process

How a project runs, from ambiguity to impact.

Every project is different, but the shape stays consistent. It keeps the team aligned, makes progress visible and ties the design work to the result it was meant to deliver.

  1. Frame

    Align on the problem, the audience, the constraints and the metric that defines success.

    What the team gets: Problem statement · Success metrics · Plan

  2. Discover

    Talk to users, dig into the data and map the current experience to find where it breaks down.

    What the team gets: Research insights · Journey maps · Opportunities

  3. Explore

    Go wide on ideas, then narrow down with prototypes, critique and quick tests with real users.

    What the team gets: Concepts · Prototypes · Test findings

  4. Deliver

    Commit to a direction, document the reasoning and partner closely with engineering through the build.

    What the team gets: Final designs · Specs · Decision records

  5. Measure

    Track the outcome after launch, share what we learned and feed it into what comes next.

    What the team gets: Impact review · Iteration backlog

Capabilities

What I bring to a team.

Product strategy

  • Problem framing
  • Opportunity sizing
  • Success metrics
  • Roadmap input
  • Prioritization

UX research

  • User interviews
  • Usability testing
  • Surveys
  • Journey mapping
  • Behavioral analytics
  • Synthesis

Design craft

  • Interaction design
  • Information architecture
  • Prototyping
  • Visual design
  • Design systems
  • Accessibility

Collaboration

  • Workshop facilitation
  • Stakeholder alignment
  • Design critique
  • Mentoring
  • Cross-functional delivery

Experience

Where I've done the work.

Next step

Have a product problem worth solving?

I'm always up for a conversation about product challenges, design roles and better ways of working. Tell me what you're building.

Get in touch