About | Simon Thai, Staff Product Designer

Practicing latte art

Practicing latte art

Enjoying football

Enjoying football

Being a movie nerd

Being a movie nerd

Playing mahjong or board games

Playing mahjong or board games

Playing with photography

Hi, I'm Simon. I see patterns everywhere.

Architecture taught me to look for the pattern. Product design taught me to turn it into a system. Somewhere along the way I became the person who'd rather spend an afternoon making something reusable than redo it five times. I care about efficiency, but never at the expense of the craft. Fair warning: the pattern-spotting doesn't switch off after work. Scroll to the left and you'll see. 👀

Hi, I'm Simon. I see patterns everywhere.

Architecture taught me to look for the pattern. Product design taught me to turn it into a system. Somewhere along the way I became the person who'd rather spend an afternoon making something reusable than redo it five times. I care about efficiency, but never at the expense of the craft. Fair warning: the pattern-spotting doesn't switch off after work. Scroll to the left and you'll see. 👀

The tools I use most for systems and product work.

Scalability

I design for the next ten use cases, not just the first. I ask who else will need it and what will change, because a pattern that holds up across teams, brands, and platforms is worth more than a one-off screen.

Clarity builds trust

I communicate early, so people know what’s happening before they have to ask. I give them clear choices and just enough information to decide, so they never have to wonder whether they can trust the product. I put extra care into failure states and edge cases, because that’s where trust is won or lost.

Consistency

Consistency gets harder with every team that ships. I protect it through process as much as design: shared tokens, clear contribution rules, and review before release. When patterns behave the same everywhere, people only learn a product once.

Data drives decisions

When a team is stuck on opinions, I bring in research. A small test often settles what a week of debate can’t, and I’m clear about what the data doesn’t show.

Design principles

When I'm not working

Where I've been

My toolkit

Four principles shape how I work, whether I’m building a component or a checkout flow.