The Not Always Glamorous But Seldomly Boring Journey of Digital Transformation
summary
Four years into METRO's transformation the claim is clear: rigid tech dogma slows outcomes, so the organization loosens rules and focuses on outcomes. A custom microservices webshop is live and driving sales, but reusing the same stack for an employee-facing fulfillment system proves wasteful. Teams adopt BigQuery and Data Studio for A/B testing and KPIs, introduce TechRadar and RFC process for buy‑in, push vertical teams with tradeoffs in duplication, and use Picon feedback and new hiring/compensation rules to shift culture.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:58Metronome
- 1:16What is Metro
- 2:20Our journey
- 2:46Technology
- 4:33What do you need
- 5:46Build yourself
- 7:03Verticalization
- 8:20Principles
- 9:57Agility
- 14:50Culture
- 16:24Team Tenets
- 17:17Values
- 18:16Initiatives
- 18:58Feedback
- 20:29Roles and Compensation
- 22:00Conclusion
related talks
44mTransformation Tales
26mTaking Your Digital Transformation Journey to Innovation
29mOvercoming bureaucracy to succeed at digital transformation
23mIts transformation! But, is it though?
41mSuccessful digital transformation: Outcome-driven teams, reward and metrics
27mTechnology is Easy. Culture is Hard.
34mThe Road More Traveled: Putting Transformation Back on the Rails
24mSuccessful digital transformation: Outcome-driven teams, reward and metrics