Hacking Human Systems
summary
Argues that failures usually come from human systems not tech and defines concrete levers: identify measurable stocks (pain, backlog, known risks), map feedback loops, and change interconnections like reporting or rules to shift behavior. Labels many change boards as change control is risk management theater, shows using chaos monkey to raise rebuild pain and drive automation, and treats immutable infrastructure as a constraint that forces consistent automation rather than a philosophical ideal. Gives examples like Heartbleed and audit cycles.
AI-written summary · about
chapters (25)
- 0:00Intro
- 2:08Agenda
- 3:09About Sentro
- 3:31Docker
- 3:46Systems
- 5:24Components of Systems
- 6:51Emotions
- 8:01Feedback loops
- 9:43Change control system
- 12:08Risk management theater
- 12:49Security audit
- 13:42Audit anxiety
- 14:25System flow
- 15:45Heartbleed
- 16:35Hacking Systems
- 18:09Configuration Management
- 19:23Pain of Failure
- 20:23Chaos Monkey
- 21:10Manipulation
- 22:01Immutable Infrastructure
- 22:39Automate Everything
- 24:08Your Human Systems
- 25:05I got ahead of myself
- 25:21What are systems
- 26:18Interview
related talks
19mHacking Management
28mChange Management for Humans
33mHuman System Design Testing
34mTaking Human Performance Seriously in Software
40mCulture Hacking
01h 25mA Systemic Approach to Organisation Design & Change Management
40mPersonnel Chaos Engineering and Building a Resilient Organizational Structure
40mMirror, Mirror on the Wall, Human Behavior Reveals it All