How to (not) f**k up any organisation with your CMS
summary
Metro and Breuninger standardize and reuse UI via a headless CMS and shared web modules as a service, add machine learning to personalize anonymous sessions, and measure real results: revenue +12%, customers +11%, AOV +6%, templates CTR +13% and sales +8%. Implementation relies on country-local content with global components, OKRs to force outcome-focused alignment, and explicit work to rebuild trust between managers and teams. Main failures are organizational—misplaced output metrics and duplicated components—fixed by outcome key results and centralizing component ownership.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:15Customer happiness matters
- 3:22B2B vs B2C differences
- 6:55Product management pillars
- 9:00Standardization in large orgs
- 11:50User journeys with CMS
- 13:17Measuring personalization impact
- 15:43Start personalization now
- 18:54Customer segmentation & A/B testing
- 22:04OKRs for org challenges
- 24:52Output vs outcome in OKRs
- 27:02Summary & call to action
related talks
49mKeynote: Best Practices – UI, API and Server-side
19mRevolutionize Efficiency: Mastering Platform Integration
25mUnlocking API Potential: The Power of Developer Portals
55mExtending Headless CMS APIs and Backend Services with Groovy
20mRevolutionizing API Management: Insights from an Architect
12mDriving technical excellence from the top: A case study in uplevelling
25mBreak up Monoliths and lay them to REST!
38mAPI Mastery: from the Design to Development