Why this matters

Too often, the boundaries between UX researcher, UX designer, and UI designer get blurred. This creates gaps: missing research, wireframes that are too abstract, or final visuals that don’t reflect user needs. As a result, developers lose time interpreting, and product owners lose clarity on what’s really being built.

After 15+ years of working on complex products, I’ve learned that separating UX from UI is not always the most effective way to work. My approach is to integrate both – from research to high-fidelity design – so that the whole team can move faster with fewer mistakes.

Classic role division

• UX Researcher – investigates user needs through interviews, testing, and data. They deliver insights and evidence, but don’t necessarily design.
• UX Designer – translates research and business goals into Information Architecture (IA), flows, and structures. Often uses low-fidelity wireframes to validate ideas.
• UI Designer – creates the final visual language: typography, colors, layouts, components. They make sure the product looks consistent and is easy to implement.
• Developer – brings all of this into reality by coding, testing, and shipping the product.

This division works well in large organizations, but it can also create silos and inefficiencies.

My integrated approach

• I combine UX and UI into a single workflow.
• I run research activities (interviews, quick tests, audits) to inform design decisions.
• I use wireframes only in early workshops or alignment sessions.
• For delivery, I go straight to high-fidelity prototypes based on a design system, because:
  • Wireframes are too generic – they often hide UX mistakes that only surface when visuals are applied.
  • Double iterations (low-fi → high-fi) cost time and create room for misinterpretation.
  • High-fidelity prototypes are a single source of truth: devs see both logic and visuals, POs see the product direction, and stakeholders see business alignment.

Benefits for the team

• Faster handoff – fewer documents, one clear prototype.
• Less rework – no UX errors hidden behind placeholders.
• Clarity for devs – what they see is exactly what they build.
• Confidence for product owners and architects – every design decision is visible and tied to system standards.

Metaphors that make it clear

• Building analogy
  • UX researcher studies the future residents.
  • UX designer plans the floor plan and flows.
  • UI designer defines the look and materials.
  • Developer builds the house.
  • Me → I deliver a 3D visualization – not just a flat blueprint – so builders and investors know exactly what to expect.
• Car analogy
  • UX researcher studies what drivers need.
  • UX designer defines ergonomics and layout.
  • UI designer designs the dashboard and controls.
  • Developer assembles the car.
  • Me → I provide a realistic 3D model – not just a sketch – so production can start with full clarity.