Silly baboons, stubborn elephants: navigating culture differences across R&D groups
summary
Claim: cross‑functional conflict usually hides stable cultural gaps — speed, tech debt, security, ambiguity and customer focus — not personality. The method maps teams on those dimensions, identify the cultural gap, then use explicit framing, personal direct communication, relationship building and negotiation; the uploader reports this approach works in practice. Practical rule: make decisions in conversation then update tracking systems and avoid Jira comments as the primary negotiation channel.
AI-written summary · about
chapters (4)
related talks
44mBridging the Gap
01h 00mBuilding a Culture of Healthy Conflict in Tech Teams
54mThe Culture Map
44mBeyond borders - navigating cultural challenges
47mWhat the f*** they are doing?
38mThe Human Element in Development
36mEffective Cross-Functional Communication
54mBuilding a Culture of Healthy Conflict in Tech Teams