How we built a Product Engineering culture at Great Expectations
summary
Describes how a startup-grade Product Engineerin culture actually gets built: reorganize into full-stack teams aligned to value streams, create an Epic lead engineering role that owns scoping and rollouts, rotate engineers through support and dev-rel to build user empathy, run hands-on data DNA days, default docs and channels to public, set outcome-level goals, and practice “addition by subtraction” with a ceremonial Viking funeral to remove cruft. Success signals: engineers name customers in conversation, alternate ideas ship quickly, and doomed projects are stopped early.
AI-written summary · about
chapters (17)
- 0:00Product engineering culture intro
- 1:26Traditional models fail
- 3:13Creative software engineering
- 6:01Product engineer traits
- 8:06Prerequisites for culture
- 9:30Building culture at Great Expectations
- 12:20User empathy initiatives
- 14:28Outcomes over outputs
- 15:50Team topologies alignment
- 17:54Full stack team realignment
- 18:15Legacy code Viking funeral
- 20:39Principles for your company
- 22:03How to know if it's working
- 23:48Remove low-value features
- 25:32Q&A: Tech vs user focus
- 27:40Q&A: Continuous improvement
- 29:05Q&A: One book
related talks
48mHow to Build and Maintain Engineering Teams Focused on Product through Culture and Values
29mBuilding alignment with Eng & Product
29mReaching Success Through Product Engineering
43mIncorporating Engineers into the Entire Product Lifecycle
52mSecrets of a Strong Engineering Culture
44mPlatform Engineering is All About Product
42mBuilding a Strong Engineering Culture – Stacy Devino
29mEngineering a Design Culture