User Manual — Emily K Chen

I am a product maker who's built and scaled products across the fintech verticals, from financial advice software to investment and payments infrastructure. Started in Financial Services analyst roles before moving into product, and haven't looked back. I work best at the intersection of go-to-market, tech, and strategy, turning big ideas into outcomes that deliver for users and the business.

Passionate about product management, good design and my indoor plants. Active in product meetups to lift and foster the product community.

What I am good at

Navigating ambiguity across product, engineering, commercial and compliance, and getting teams aligned.
End-to-end journey design (Day 0 to 365). I think in systems, not features, and pattern-match across platforms and ecosystems.
Sharp framing. I can compress a messy problem into a one-line decision and tell you what we're actually trading off.
Bringing craft sensibility to functional calls. How something feels matters as much as whether it works. My default archetype is architect. Lego is my outlet and it shapes how I think about products.

What I struggle with

I run hot on vague problem statements. I'll push back sharper than I intend, call it out and I'll adjust.
I default to architect-mode on things the team just needs a clear next step on, over-engineering the thinking when a clear call is all that's needed. Call me out when this is happening.
Switching between people-manager and maker mode. Some days I'm better at one than the other.
I prefer time to fully consider ideas before responding.

How to work with me

Lead with your recommendation. Bring me a proposal and your reasoning, not an open question. I'll probably ask questions, that's curiosity not mistrust.
Show me the thoughts and evidence behind "the thing." Know your problem, the focus questions, and why it matters.
Two speeds for decisions:
- Type 1 (irreversible or costly to undo): give me a heads-up, okay async in Slack or a call.
- Type 2 (reversible): just decide. Tell me what you did. Keep moving.
If I've gone quiet on something time-sensitive, ping me directly with what you need by when. I'd rather have a deadline than guess.
I prefer candid, non-passive-aggressive communication paired with structure and context.
My best working pattern is a chaotic balance. Meetings in the morning, deep work in the afternoon. Energy is low at night. I keep regular lunch and dinner breaks, please don't book over them.
Slack > Google Meet > face-to-face (coffee and good-looking food can convince me out of the office). Not great with email.

What I believe

Speed is a superpower, and shipping fast beats the best strategy. I create a bias toward shipping, small teams move faster, and AI-native teams will move 10x faster than those not willing to change. The loop I keep coming back to: listen, build, ship, tell the customer, then repeat, forever.

What drives me

I am energised by building at the intersection of tech, AI and great product design. I am particularly interested in creating orchestration layers and platform capabilities that benefit many products and customers, while making onboarding for individuals and businesses feel effortless. The most exciting opportunity right now is using AI and proactive insights to keep humans in the loop for higher value decisions, rather than repetitive operational work. I care as much about craft and product taste as I do outcomes.

How I work with AI

AI is part of how I work, yours and mine. Drafts, synthesis, first-cut analysis: assume it's AI-assisted. I care about the bar, not the process.

Don't ship AI slop.
Treat AI as a sparring partner, not a ghostwriter.
Tell me when it's done the heavy lifting so we can talk about whether the framing is right.
I don't use AI for feedback conversations, hard people calls, or anything that needs a human.

A note on feedback

Feedback is a gift, both ways. If you see something, a blind spot, a better path, a habit not serving the team, please say something. Real-time is better than waiting for a review cycle.