Breaking down silos to team cross functionality
summary
Argues that true cross-functionality requires system changes not title swaps: a Fortune 100 edict to rename everyone “engineer” without time to retrain creates lasting fallout, while simple practices like ride-alongs reveal customer-facing opportunities (garbage driver spotting sales leads). Claims managers who chase resource efficiency create single points of failure; recommends eliminate hero-worship of firefighting, give people time to reform identities, share system context across roles, and empower front-line staff to act on customer signals.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:07Identity and imposter syndrome
- 4:21Redefining cross-functionality
- 7:20Lessons from outside IT
- 11:09Culture and systemic constraints
- 15:11Avoiding hero-worship
- 17:32System alignment and purpose
- 20:31Customer experience failures
- 24:22Conclusion and call to action
related talks
34mDesigning an engineering team: Making room for everyone
21mGrowing engineering managers: Breaking down the monolith
17mEliminating hero culture in software engineering teams
36mThe human factor you might be missing when designing your system
21mEliminating Hero Culture on our Engineering Teams
31mImproving engineering effectiveness: A journey for the entire organization
44mA Match Made in Heaven - Instilling Harmony Between Product and Engineering
02mGenuinely multi-disciplinary teams