Episode #13: From Data Science to Product Leadership with Heather Chen

Heather Chen did not treat a move into product management as an all-or-nothing leap. She tested the role, learned where her technical background helped, and deliberately built the cross-functional skills the new work required.

What you'll learn

• How to test a possible move into product before making a full transition

• Where technical experience helps a PM and where it can leave learning gaps

• How qualitative and quantitative feedback support different product questions

• Why cross-functional relationships and deliberate communication keep work moving

• How structure can help a growing team scale without creating unnecessary overhead

Test the role before changing careers

Heather started her career as a data scientist at Google. Her interest in product management grew after she joined a user study in New York and watched people interact with data models she had helped build. Seeing users choose different paths, critique the experience, and explain how the product might affect their lives made the application of the work feel immediate.

She began paying closer attention to product managers and asking them about their responsibilities. Rather than switch roles based only on observation, she proposed a 50/50 arrangement that let her work as both a data scientist and product manager. She raised her hand for a product role on a candidate-search effort, tried the work for several months, then asked to transition formally. Her manager and mentor supported the internal transfer.

Technical empathy is useful, not complete

Heather says her data science and software engineering experience helps her speak an engineer's language. She understands that modeling needs time and data, and that engineering estimates can change as unknowns surface. That experience makes it easier to recognize where a team may need more context, a reprioritized scope, or obstacles removed.

Technical fluency, however, did not cover the entire product role. Heather needed to learn more about design. As a data scientist, she had not worked as closely with designers. Product management brought her into prototyping, mockups, interaction choices, edge cases, and decisions about whether an experience should operate in real time. Those choices could have significant infrastructure implications.

The role also expanded her partnerships with legal, marketing, sales, and other functions throughout the product lifecycle. Her experience is a reminder that a strong starting skill can create leverage without eliminating the need to learn. Product managers should use their home-field expertise while noticing which voices and disciplines they do not yet understand.

Match the evidence to the question

When asked how to choose between qualitative and quantitative insight, Heather resists a universal formula. The answer depends on the feature, product, and decision. When possible, her teams use both.

On the quantitative side, the team defines what success means before launch, including a north-star metric and secondary measures. Testing with a segment of users can show whether a change performs better than what came before. This creates a clearer basis for deciding whether to expand a release.

Qualitative work helps explain the behavior behind those numbers. Teams can interview users, observe them using a product, and ask about ease of use or willingness to recommend it. Research before launch remains important, but a live environment often reveals behavior that did not appear during prototyping.

Build relationships and the right amount of process

Heather's advice is to keep conversations open across functions, not only when an immediate request appears. Regular contact helps product managers understand how others work, discover unexpected ideas, and build relationship assets before a critical need arises. Reaching out after six months of silence may still work, but established trust makes collaboration easier.

Remote work makes communication design especially important. Without informal hallway conversations, teams must decide deliberately when a meeting is needed and when asynchronous communication is enough. Too many meetings create burnout, but too little alignment can stall approvals and execution. The product manager helps select the format that fits the decision.

Heather also describes overplanning as a trait that can create pressure in personal settings but add value in growing teams. Appropriate structure reduces inconsistency and repeated overhead.

Her daily challenge reinforces that balance. Product managers move between detailed feature decisions and high-level strategy, while protecting time to think amid meetings and messages. The reward comes when a demo or launch turns weeks of shared work into something people can use and respond to.

Heather's journey shows that product leadership grows through experiments, honest gap-finding, mixed evidence, and durable partnerships. Listen to Episode 13 for the full discussion and more practical lessons from her transition into product.