How to affect change without losing your job
summary
Organizational change is operational work that requires credibility, clear communication and tactical follow-through: plan an offsite for back-end ICs to surface problems, iterate locally and document a new RFC process and onboarding, then enforce it by changing tools rather than hoping adoption happens. A hiring overhaul replaces take-homes with a live onsite and trains 40 engineers, hitting recruiting goals; a code-review working group stalls because it fails to mandate tool change. Expect 6–12 months of effort and nontrivial personal cost.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:47Make good trouble
- 8:29Leadership
- 12:32Credibility
- 13:33Navigate
- 13:49What does that mean
- 14:31Communication is a superpower
- 14:42Humans love a story
- 15:33You cant win everything
- 16:54Trends towards entropy
- 17:19You are not your work
- 17:30Examples
- 17:49Why change
- 18:14Love language
- 18:44Changes I made
- 19:07Offsite
- 19:50Mentorship
- 20:04Crossfunctional
- 20:15Code review
- 20:37Postmortem
- 20:49Iteration
- 21:42Slack
- 22:08Recruiting
- 22:26Cost
- 22:39Burnout
- 23:08TLDR
related talks
54mEffecting Change—The Art Of Leading Teams
51mEffecting Change—The Art of Leading Teams
21mLeading Grassroots Organizational Change
18mCan I change my organisation?
40mMake the Change, Then Make It Work
26mApplying A Technical Brain To Organizational Design
29mChange Management for Humans
51mOrganisation Refactoring and Culture Hacking : Lessons from Software