Shift Your Leadership
summary
Claims that tiny interventions move culture: swapping a single metric pushes Dev and Ops into collaboration and produces DevOps; a one-policy rule at Salesforce—deliver value once a month—lets teams choose process and coincides with ~50 acquisitions since 2006; Google enforces 70% OKRs and all code reviewed, making testers write code and reducing handoffs. A 30‑second, no‑touch game exposes duality vs collaborative mindsets. These concrete hacks, metrics and policies are presented as practical levers that actually change behavior.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:44Development vs Operations
- 6:30Salesforce
- 7:15Why Care About Culture
- 7:43Game Time
- 9:48Mindsets
- 13:24Competitive vs Collaborative
- 14:20Microsoft
- 16:03CEOs
- 16:34Scrum Masters
- 17:36Two Spectrums
- 18:59Product Owners
- 20:56Scrum
- 23:07Power Style
- 25:20Google
- 28:43The Shape of Culture
- 29:14Salesforce Example
- 31:19Healthcare Example
- 31:45Traditional Culture
- 31:58Agile Leaders
- 33:26Challenges
- 36:59Is compromise realistic
related talks
40mBetter Living by Changing Less – IncrativeOps
20mMaking the Case for Change
43mEmpowerment in action
22mLeading software teams with context (visibility)
34mYou only have to change one thing to do the DevOps
30mLeadership Lessons from the Agile Manifesto
51mOrganisation Refactoring and Culture Hacking : Lessons from Software
51mTen Tips To Uplevel Your Leadership