Keep a friction log and read a sales book - product ownership with Joyce Er
· Summarized
Key takeaways
- The implementation phase of software engineering has shrunk significantly due to AI, placing more responsibility on understanding why and for whom you build.
- Cultivating ownership through rituals like daily stand-ups and dogfooding helps teams develop judgment, accountability, and a shared sense of responsibility for product quality.
- Judgment is developed through lived experience, active use of the product, and maintaining a friction log of user frustrations.
- Reading sales and business books helps engineers understand how value is communicated and prioritized, leading to better product decisions.
- Building strong relationships with dependent teams and engaging with customer conversations are vital for navigating complex dependencies and improving product outcomes.
- Unlearning old assumptions and embracing new AI capabilities require an open mindset, experimentation, and willingness to adapt quickly.
- Trust from customers and colleagues is the ultimate metric of success in product engineering, encompassing both technical quality and user satisfaction.
- In a rapidly evolving field, curiosity and active engagement with cross-team interactions are human skills that will remain essential.
Summary
Introduction and Joyce's Background
Kent C. Dodds introduces the episode focused on product engineering, speaking with Joyce Er, who has experience both as a software engineer at Microsoft on VS Code and now as a product manager at Cerebras. Joyce shares her recent transition from building tools primarily as an engineer, witnessing the evolution of AI like GitHub Copilot, to managing products where she now influences the entire end-to-end experience. She highlights her work at Cerebras, which produces massive wafer-scale chips for AI inference, showcasing her involvement in cutting-edge hardware technology.
The Shift in Software Engineering and Ownership
Joyce discusses how traditional software engineering—focused heavily on writing and designing code—has transformed, especially with AI's rise. She notes that the implementation phase now takes a smaller fraction of developer time, shifting focus toward understanding the 'why' and 'who' of what is being built. She emphasizes that on the VS Code team, engineers owned the entire feature lifecycle, fostering a culture of ownership based on trust and accountability. This ownership model is crucially more important with AI, where execution costs are lower but judgment and cohesiveness matter more.
Practicing Ownership: Rituals and Culture
Joyce describes practical ways to foster ownership within teams, such as daily stand-ups where team members present and defend their features and a practice called dogfooding, which involves using your own product daily. She explains that these rituals help team members develop judgment, sense of responsibility, and a holistic understanding of the user experience. For example, if team members won’t use the features they build, that's a warning sign. She underscores the importance of trust, shared responsibility, and personal initiative in creating a cohesive, high-quality product.
Building Judgment and Developing Opinions
Joyce argues that judgment in product engineering comes from lived experience and continuous feedback, such as maintaining a friction log—a daily list of user frustrations or inefficiencies. She advocates for reading sales and business-focused books, like 'The Qualified Sales Leader,' to understand how value is communicated and how decisions impact business success. These habits help engineers develop informed opinions about what to build, how to prioritize, and how to craft products that genuinely serve user needs.
Handling Dependencies and Relationship Building in Complex Environments
Joyce explains that in larger or more complex organizations, collaboration with dependent teams is essential. She suggests that initial alignment on goals, building good relationships, and understanding other teams’ priorities can help influence dependencies. She recommends in-person interactions, curiosity, and engaging with teams beyond immediate scope to broaden understanding of system primitives and opportunities, which she considers a human skill unlikely to be replaced by AI. These relationships enable better product decisions and smoother workflows amid dependencies.
Adapting Skills in a Rapidly Changing AI Landscape
Addressing the need to unlearn outdated assumptions, Joyce emphasizes that AI models now produce entire applications with minimal input, rendering many old priors about programming obsolete. She advises newcomers and experienced engineers alike to maintain open minds, spend time experimenting with new tools, and embrace the rapid pace of change. Joyce highlights learning from experiences like React Hooks to adapt quickly, stressing that those who are willing to unlearn and experiment will find abundant opportunities in this fast-moving landscape.
Joyce’s Final Advice and Endorsements
Joyce concludes by reinforcing that trust—both from customers and team members—is the ultimate measure of successful product engineering. She shares her personal journey of shifting from engineering to product management, emphasizing that gaining trust and aligning with user needs are foundational. She recommends maintaining a friction log as a tangible practice for developing product sense, and reading sales books to better understand business value. She invites listeners to follow her on social media for ongoing insights, affirming that curiosity and relationship-building are key human skills in this field.
Sponsors
- None explicitly mentioned in the transcript or episode description.
Show notes
If execution got cheap and you still wait for someone to tell you what to build, this episode is for you. Kent talks with Joyce Er about five years owning features on VS Code, the jump to product at Cerebras, and why trust is the metric that tells you the work is working.
They cover daily stand-ups that roast your feature in public, friction logs as taste practice, dogfooding when you cannot be the user, qualifying customers instead of taking every check, and why a sales book belongs on a product engineer's shelf.
- (00:00) - Meet Joyce Er
- (01:18) - A dinner-plate AI chip
- (02:47) - Engineering as we knew it shrunk
- (04:38) - Ownership on the VS Code team
- (07:33) - Why ownership matters more with AI
- (10:23) - Keep a friction log
- (12:18) - Judgment from lived experience
- (15:33) - Invalidate old priors
- (17:41) - VS Code's daily stand-up roast
- (20:35) - When you cannot dogfood
- (22:52) - Getting partner teams to help
- (29:30) - Curiosity and time-boxing AI
- (32:20) - Selling inference to coding tools
- (34:00) - Qualify the right customer
- (38:47) - Trust as the success metric
- (40:11) - Homework: friction log and a sales book
Joyce Er spent five years as a software engineer on VS Code at Microsoft, with a front-row seat to GitHub Copilot and the shift from typing code to owning the why. About a year before this conversation she moved into product at Cerebras, the company behind dinner-plate wafer-scale chips for ultra-fast AI inference. The views in this episode are her own.
A major theme is ownership. On VS Code, every engineer owned the end-to-end definition of what shipped, not just the implementation. That only works with trust, dogfooding, and rituals that force you to defend the experience. Joyce describes a daily stand-up where you get five minutes to walk the feature, then the team roasts padding, consistency, and whether it belongs in the product. The lighter version is a bug bash. If people inside the company will not use the feature, that is a signal.
They also talk about how you grow judgment when nobody assigns the work. Joyce's first practice is a friction log: five minutes at the end of the day listing paper cuts in any software you used. Her more controversial homework is to read a sales book - she recommends The Qualified Sales Leader - so you understand how business value actually closes, especially when the product is not a credit-card checkout. Trust, she says, is the end-to-end metric: if customers and teammates trust you, you are doing the job.
Homework: keep a daily friction log, and read a book about sales.
Homework
- Spend five minutes at the end of each day writing a friction log of paper cuts in software you used.
- Read a sales book - Joyce recommends The Qualified Sales Leader - and notice how value gets sold at your company.
- Use those notes the next time you decide what is worth building.
Resources
- Joyce Er on X
- Joyce on GitHub
- Joyce on LinkedIn
- Cerebras
- Visual Studio Code
- The Qualified Sales Leader by John McMahon
Guest: Joyce Er
Host: Kent C. Dodds
- Website: kentcdodds.com
- 𝕏: @kentcdodds
- GitHub: @kentcdodds
- YouTube: kentcdodds-plus
- Podcast: epicproduct.engineer
The views expressed by Joyce Er are her own and do not necessarily represent those of her employer.
Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account