Team Purpose vs Company Purpose
summary
A 15–20 person cross‑functional team at Zalando reorganizes around one customer problem (shopping that feels natural), uses knowledge graphs and ontologies to surface style and event‑based results, and enforces visible constraints plus outcome‑based goals. The team spends one quarter becoming data literate, builds one‑page initiatives (why/what/how), demos findings continuously, and moves from managerial decisions to collective solutioning. Result: an autonomous team that aligns experiments to measurable impact and fixes concrete failures like missing search results for style or event queries.
AI-written summary · about
chapters (13)
- 0:00Introduction with examples
- 2:47Team purpose at Zalando
- 3:29Why everyone must contribute
- 5:18Three principles for teams
- 7:04Principle one: Shared direction
- 9:39Principle two: Constraints
- 12:29Principle three: Data literacy
- 15:00Three supporting processes
- 15:42Process one: Outcome goals
- 17:07Process two: Initiative format
- 19:19Process three: Demo insights
- 20:20Summary and impact
- 21:02Q&A begins
related talks
47mHow to create more business impact with flexible teams
34mAutonomous Teams in Technology Organisations
52mCross functional teams are great - but what about the business?
47mKeynote: Where Teams Choose Autonomy, Accountability and Scaling a Platform
38mFrom Monolith to Microservices at Zalando
44mInsights on How Team Topologies Drive Organizational Success
23mAish Dahal at StaffPlus London 2023
18mIs That Actually Improving the Team? — An Organizational Experiment Starting from 'What Is a Team?'