Product Designer at OOZOU, Bangkok

Nabhak "Yhai" S., a designer who ships.

I sit between clients and developers. Conversations become requirements, requirements become flows, flows become a design system, and lately, working prototypes built with AI.

Before product design I made games, graphics and digital content. Games taught me that feel is a feature, not polish. Outside client work I build small tools to remove my own daily friction, then share them.

7+years in UX and UI
16+client brands
tools I build and share
6notes written

How I work, from first meeting to launch

Four steps, the same every time, so clients always know what happens next and what they get at the end of each one.

  1. 01

    Understand

    I sit in the client meetings and ask the awkward questions early. A two-hour call becomes a one-page requirement summary with scope and a timeline estimate.

    You get: a one-page requirement and an estimate
  2. 02

    Structure

    User flows and wireframes first, so we argue about the UX while it is still cheap to change. Competitor analysis and a workshop when the direction is fuzzy.

    You get: flows and clickable wireframes
  3. 03

    Design

    UI on a design system: tokens, variants and components that scale across screens and brands. Rebranding becomes a token swap, not a redo.

    You get: final UI and a living design system
  4. 04

    Build

    Prototypes built with AI when a click-through is not enough, then a clean handoff: named layers, one final file, tickets that match the screens.

    You get: a handoff file and, sometimes, a working prototype

What I bring to a team

01UX and UI design

Flows, wireframes, final UI, prototypes. Mobile first, RTL when the market needs it.

02Design systems

Tokens, text styles, components with real variants, set up before the screens so the whole team works from one source.

03Product strategy

Requirement summaries, scope and estimates, competitor analysis, decisions written down.

04AI-powered prototyping

Working prototypes built with Claude when a click-through would hide the real question.

05Design to dev handoff

Named layers, one final file, tickets that match the screens. Developers stop asking.

06Design team mentorship

Reviews, pairing and a shared way of working so juniors ship with confidence.

07Internal tools and back-office

Dashboards and admin tools for the people who run the product, and billing portals for the admins and accountants who pay for it.

08Product review and design QA

I check the built product against the design and the user flow, then log what breaks before users find it.

09Improvement ideas for internal products

I spot where internal tools slow a team down and pitch concrete fixes, with mockups the team can react to.

Tools open on my Mac most days

  • FigmaFlows, UI, design systems, plugins
  • IllustratorIcons, logos, this avatar
  • ClaudePrototypes in code, plugin logic
  • GitHubEvery Momo tool lives here
  • MCPPlugs Claude into Figma and the browser
  • JiraSprints with the dev team
Figma VariablesAuto LayoutComponent variantsDesign tokensPrototypingVibe coding with AI

Experience: a decade of making things

  1. 2019
    Product DesignerOOZOU, Bangkok, to now
    oozou.com
  2. 2019
    UX/UI DesignerEver Medical Technology
  3. 2018
    UX/UI DesignerPapapay, to 2019
  4. 2018
    Graphic DesignerSmile Organics
  5. 2016
    Digital Content DesignerZap-interactive, to 2017
  6. 2014
    Graphic and Game DesignerPRANEAT, to 2016

Let's make something clear.

Product design, design systems, or a small tool you wish existed. Bangkok-based, remote-friendly.

It's --:-- in Bangkok.

Say hello LinkedIn GitHub