👋 Hi, I’m Yumei, Product Builder

Yumei Liu — portrait

I'm a product-minded professional transitioning from engineering into product management,
backed by hands-on Senior Product Owner experience at Lenovo and a Master's in Management Analytics grounding my decisions in data.

Projects

My Values

Outcomes over output

Shipping a feature isn't the goal; solving the problem is. I measure success by the impact a decision creates, not just the work completed.

Decisions backed by data

I ground product decisions in evidence — user research, metrics, market signals — rather than opinion, and I'm honest about what the data can't yet tell me.

Clarity over comfort

I'd rather surface a gap or ask an uncomfortable question early than let ambiguity ship downstream. Precision in requirements saves rework later.

User empathy as a discipline

Every roadmap decision traces back to a real person's problem. I keep the user in view through prioritization, not just at the discovery stage.

Alignment across functions

Good products get built at the intersection of engineering, design, and business. I see stakeholder alignment as part of the job, not a distraction from it.

Growth as a practice

I treat ambiguity and new domains as things to learn from, not obstacles — the same instinct that took me from engineering to product ownership.

My Process

1

Discover the problem

Start from the problem, not the solution — talk to users, study data and market signals before jumping to features.

2

Define the opportunity

Turn discovery into a clear point of view: who the user is, what they need, and what success looks like.

3

Prioritize with a framework

Use structured frameworks (MoSCoW, RICE, Kano) to separate essential from nice-to-have, and be explicit about trade-offs.

4

Write requirements that remove ambiguity

Translate strategy into PRDs, user stories, and acceptance criteria detailed enough to cover edge cases.

5

Build in partnership, not in a silo

Stay closely partnered with engineering, design, and QA — answering questions fast and validating early.

6

Launch with metrics defined upfront

Define how success will be measured — OKRs, KPIs, or output metrics — before launch, not after.

7

Measure, learn, and iterate

Shipping isn't the finish line. Feed post-launch data back into the next round of discovery.

Let’s Talk

📧 Email: yumeiliu2017@outlook.com

💼 LinkedIn: www.linkedin.com/in/yumei-liu-51323b9a