VIENJAZH
Open to a small number of thoughtful collaborations

About

I build where product decisions meet everyday operations.

VI / EN / JA / ZH

The approach is practical: understand what a team is trying to do, remove repeated coordination, then build a system strong enough for the next version of the business.

Operating perspective

Start with the loop that already exists.

I do not start with a feature list. Who needs to know what, when does a decision become state, and what breaks when the day gets busy? Those answers shape the product boundary before the interface is polished.

How I work

How I work

Start with the loop that already exists.

  1. 01Watch the operating loop.
  2. 02Name the constraint that matters most.
  3. 03Turn repeated decisions into product state.
  4. 04Build the smallest complete workflow.
  5. 05Verify behaviour in context.
  6. 06Expand only when the foundation earns it.

Principles

Keep complexity in the right place.

  • 01Make the next decision obvious.
  • 02Automate repetition before adding ceremony.
  • 03Keep tenant and permission boundaries explicit.
  • 04Show failure states instead of hiding them.
  • 05Build for the next change, not an imagined scale.

Capabilities

Start with the outcome, then choose the technology.

  • 01Product framing and discovery
  • 02Workflow and information architecture
  • 03Multi-tenant product systems
  • 04Full-stack implementation
  • 05Realtime and integration boundaries
  • 06Operational admin tools
  • 07MVP-to-platform evolution

Current focus

Build where operations can become infrastructure.

  • 01LogiVN · F&B operations
  • 02Fball.vn · club operations
  • 03Payment confirmation research
  • 04Cloudflare-first infrastructure
  • 05Tools that help small teams do more

A note

I work independently between Vietnam and Japan. Depending on the problem, a day can move from a product question to a data boundary, a screen, an edge case or a release checklist.

Start a conversation