Aligning Goals & Processes between Engineering & Product
summary
Teams organize as epods (engineer product ops) and run recurring design sprints / concept sprints to co-own problems, not solutions, feeding quarterly plans with monthly or biweekly check-ins and retrospectives. Roadmaps consolidate product and technical work into one consolidated backlog; big technical projects get first‑class road‑map entries. MVPs leave “breadcrumbs” for later owners. Expect to budget roughly 25–33% for tech investment at scale, or allocate an OKR or 10–20% of time earlier.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:26Introductions
- 2:19Who are the panelists
- 5:23Transitioning from Engineering to Product
- 7:46Design Sprints
- 10:11Building Trust
- 14:24Product Roadmap
- 19:16Tech Debt
- 25:53Understanding Tech Debt
- 28:19Handling Brilliant Jerks
related talks
29mBuilding alignment with Eng & Product
29mReaching Success Through Product Engineering
09mBuilding High-Trust Teams to Supercharge Product Development
24mScaling a Product Vision Through World-Class Team and Culture
31mHarmonizing Across Product & Engineering (Cross Team Collab)
48mBuilding a Product and Engineering Relationship that Works
10mDrive product gaps as an engineering leader
58mProject Management for Engineers