Step by step approach to create meaningful impact
summary
ImmoScout case study showing a stepwise method to turn feature teams into product teams at a 20M‑user company with 700 employees and 250 engineers. Concrete moves: OKRs every four months, create an MVP validated with the customer within deadline by involving engineers early, and assign a tech feature champion to bridge discovery and delivery. Results include failing fast (avoiding wasted spend), month‑by‑month velocity gains, more ownership and measurable trust with management.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:30Warmup task
- 2:36Why we decided to give this talk
- 3:35Underlying beliefs
- 5:30Emoscout background
- 7:15Emoscout best practices
- 9:01Examples of pain points
- 9:28Poll
- 10:34Root cause
- 12:18The first dilemma
- 14:44What did we do
- 17:14Learnings
- 18:52Dilemma
- 19:04Whats not working
- 20:46Whats discovery
- 21:21Whats waterfall
- 22:04Surprise collaboration
- 24:57Summary
- 26:13Ownership
- 28:36Solutions
- 31:53Conclusion
- 33:03Recap
- 35:37QA
related talks
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team
58mProject Management for Engineers
23mFrom Vision to Impact: Leading Zero to One Projects in the Workplace
30mDelivering Features VS Delivering Impact
44mTeams That Propel People Forward
44mCreating ValueFirst Product Organisations
22mOptimizing Product Development: Balancing Speed, Quality, and Process
20mMaking the Case for Change