Know your customer better than your code - product engineering with Lucas Wargha
Show notes
Kent talks with Lucas Wargha, engineering manager at FamilySearch, about turning software engineers into product engineers: understanding mission and business outcomes, talking to real users across cultures, and stopping the assembly line of JIRA handoffs.
They cover customer personas at global scale, the Gmail password-loading story as product-engineering thinking, owning epics end-to-end, creators vs consumers, and a hopeful take on historic days in our industry.
- (00:00) - Introduction to Product Engineering
- (02:12) - FamilySearch and product outcomes
- (07:36) - Customer personas at global scale
- (12:07) - Know your customer better than your code
- (15:01) - Product engineer vs product manager
- (17:33) - Turning engineers into product engineers
- (22:38) - The Gmail password-loading story
- (27:01) - Stopping the JIRA assembly line
- (31:19) - Prioritizing customer needs
- (42:28) - Homework: talk to three users
Lucas leads engineers building FamilySearch Memories - tools for photos, audio, and stories that help people connect with family beyond names and dates. He describes a shift away from engineers as expensive task-takers toward people who understand company vision, product outcomes, and why a rewrite or maintenance project is worth doing.
A thread through the episode is customer literacy: mapping personas, interviewing users in Brazil and discovering translation nuances you would never see in analytics alone, and balancing qualitative insight with data when the customer base is literally global. Lucas and Kent compare product engineers and product managers, why role sprawl happened, and what changes when engineers own milestones across web and mobile instead of finishing isolated stories.
They also talk about practical culture moves - engineers delivering food like DoorDash did, using your own product, the Gmail team preloading after you type your email, and why fulfillment comes from creating value for people rather than optimizing reducers. Lucas closes with homework grounded in his motto: know your customer better than your code, and talk to three users before you implement your next story.
Homework
- Know your customer better than you know your code - measure whether you get as passionate about product outcomes as you do about architecture debates.
- Take the first story on your board (or next assigned work) and talk to three different potential users across personas before you implement it.
- Resist finishing the story in isolation - what you learn from those conversations should change what you build.
Resources
Guest: Lucas Wargha
Host: Kent C. Dodds
Chapters
Loading chapters …