Chelsea Qian Huang

I'm a product strategist and designer who has spent 16 years turning intricate systems — billing, revenue recognition, marketplace operations, cybersecurity — into products that people can actually use.

My speciality is the hard B2B problem: multi-stakeholder workflows, ambiguous briefs, and the kind of complexity that requires both design craft and systems thinking in equal measure.

What makes my perspective unusual is the foundation beneath it. An engineering degree in systems control means I don't just see the interface — I trace back to the logic, the constraints, the upstream decisions that made the interface what it is. A master's in HCI adds the human layer: behaviour, cognition, the gap between what users say and what they do. Sixteen years of applying both across industries as different as cybersecurity and commercial real estate rounds it into something hard to replicate.

In 2024 I took a deliberate step back — not from design, but from the familiar path. A year of reading, bouldering, building with GenAI, and sharpening new lenses on behavioral psychology and investment strategy. I founded Lugugul as a container for independent work and applied experimentation — and discovered that the problems I find most interesting rarely fit neatly inside a single role.

Now I'm looking for the next place where that combination of depth matters.

16 Years Across

Financial Ops — billing, revenue recognition, order management
Commercial Real Estate — marketplace & operations
Cybersecurity — code signing, PKI, certificate lifecycle
Enterprise SaaS — sales ops, CPQ, quote-to-cash
Manufacturing, IoT & industrial workflow
Developer & employee experience
Production printing & hardware-software
Consumer — lifestyle, education, dating

Education

MS HCI / Design

Indiana University

BS EE & Systems Control

Beihang University

Two degrees that rarely sit in the same person — one trains the eye for human behaviour and interface, the other builds the instinct for systems, control logic, and engineering constraints. Together they're the reason I read a product problem at multiple levels simultaneously.