Menu
Contact
Menu
Menu
Menu
Contact
Chris Pak
Profession
Product Designer & Design Leader
Location
Asia / us hours
Chris Pak
Profession
Product Designer & Design Leader
Location
Asia / us hours
BUILD YOUR NEXT PRODUCT
WITH ME.
THIRTY MINUTES, WE'LL WORK OUT WHETHER I'M THE RIGHT PERSON FOR IT.
2
Slots
Available
FAQ
Quick
Answers.
Everything you should know before we start designing and building.
01
01
What do you actually do?
I design products and the experiences inside them. Research, information architecture, interaction design, and interface, from ambiguous problem through to a finished product. I don't stop at design: directing AI development, I build and ship production applications, deployed and running, not just prototypes.
Alongside that I define what good looks like: UX metrics, Northstar definitions, and measurement frameworks that let a team tell whether the design worked.
02
02
Do you work on websites, or products?
03
03
You build in code too?
04
04
How long does an engagement take?
05
05
What if I don't know what I need yet?
06
06
How do we start?
01
01
What do you actually do?
I design products and the experiences inside them. Research, information architecture, interaction design, and interface, from ambiguous problem through to a finished product. I don't stop at design: directing AI development, I build and ship production applications, deployed and running, not just prototypes.
Alongside that I define what good looks like: UX metrics, Northstar definitions, and measurement frameworks that let a team tell whether the design worked.
02
02
Do you work on websites, or products?
Products. Apps, platforms, internal tools, and the features inside them. If you need a marketing site, I'm probably not the right fit and I'll tell you so on the intro call.
03
03
You build in code too?
Yes, and further than most designers go. Directing AI development, I take a product from design through to a deployed, production application: real backend, database, authentication, running on infrastructure the client owns. I own the outcome end to end instead of handing a spec to a separate team.
The part that matters is how the build is held together. Every change runs through an automated test suite before it can ship, integration tests against a real database and browser tests across engines, and the release is blocked if any of them fail. Code standards are enforced automatically, releases are versioned and changelogged, and database changes are dry-run before they touch live data. And before a product goes to real users at scale, I bring in experienced engineering review, including an independent security pass. Directing the build fast is the easy part. Running it with that discipline is the part I've actually set up.
04
04
How long does an engagement take?
A discovery sprint runs two weeks. A full design and ship engagement typically runs six to twelve weeks, depending on scope. Retainers run monthly with a three month minimum.
Before we start, you get a written scope with a fixed price, a timeline, and what's explicitly out of scope.
05
05
What if I don't know what I need yet?
That's common and it's what the discovery sprint is for. Most teams come to me knowing something isn't working, not knowing exactly what. Figuring out the right problem to solve is the first half of the job.
06
06
How do we start?
A thirty minute call. We talk about what you're building and where it's stuck. If I'm the right person, I'll send a proposal with scope, price, and timeline. If I'm not, I'll say so.