One Team, One Dream? Gaining Cross-Functional Buy-in
summary
Practical checklist for getting cross-functional buy-in: schedule one-on-ones with every member immediately to learn how people work; co-create a working agreement posted above the wall; build a simple RACI chart that clarifies who does what and who has decision authority; include Sales, Support and BD in kickoff so everyone hears user problem and KPIs; make roadmaps 30/60/90 and iterate; stop talking in meetings to let others contribute; run retros that surface personal feedback and track a weekly team happiness metric.
AI-written summary · about
chapters (17)
- 0:00Introduction and background
- 1:50Challenges in cross-functional teams
- 3:40Be curious and practice empathy
- 5:50Inspire and motivate your teams
- 6:53Build relationships early
- 8:19Create working agreements
- 9:25Practice radical candor
- 10:28Start teams together at the beginning
- 11:56Align on success metrics
- 13:18Define roles with a RACI chart
- 14:33Clarify ownership and authority
- 16:19Define shared terminology
- 17:54Collaborate on roadmaps
- 19:41Run better retrospectives
- 21:32Address team happiness
- 23:21Summary and key takeaways
- 24:08Q&A session
related talks
49mAll Aboard: Tools and Tactics for Building Team Consensus.
31mHarmonizing Across Product & Engineering (Cross Team Collab)
44mA Match Made in Heaven - Instilling Harmony Between Product and Engineering
09m"The Joys of Managing Engineering Teams"
26mAgile values and principles for non software teams
52mCross functional teams are great - but what about the business?
30mMy first 90 days, kick starting a new team for long term success
39mUsing Agile Techniques to Build a More Inclusive Team