Cross functional teams are great - but what about the business?
summary
Outfittery reorganizes around customer lifecycle teams (onboarding, engagement) and uses hypothesis-driven A/B tests to chase conversion; one experiment shows a measurable 0.1% lift but marketing traffic shifts later produce a full 1% fluctuation that exposes cross-team coupling. Data scientists split time with teams (2 days/3 days rotation), teams share Slack channels, sprint demos and lightning “8‑minute” talks. Result: much better collaboration and fewer surprises, but higher forecasting overhead and some cross-domain projects remain unchanged.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:16Jespers story
- 0:32Something was thrown over the wall
- 5:38What is Outfit Reid
- 7:01Crossfunctional team
- 14:13Two challenges
- 16:39Three challenges
- 20:20Crossfunctional teams
- 28:03Experiment
- 29:46Anxiety
- 35:13The good
- 37:38The bad
- 40:53Product yield
- 41:58Sprint demos
- 43:09Eight minutes of fame
- 44:24Asset rotation
- 45:07Midterm planning
- 45:30retrospectives
- 46:10summary
- 48:31shared responsibilities
- 49:16final outcome
related talks
46mBalancing individual team flow with cross-team collaboration
51mHow to build cross-functional, hybrid teams that Get Stuff Done
01h 10mAgile Cross Team Collaboration How Tos
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team
27mTeam Purpose vs Company Purpose
28mOne Team, One Dream? Gaining Cross-Functional Buy-in
46mWhy Cross-Functional Teams Build Better Microservices
31mHarmonizing Across Product & Engineering (Cross Team Collab)