How to beat an existential crisis by becoming Cloud Native.
summary
Argues that survival means changing more than infra — it’s organizational, financial and cultural work as well as tech, because newcomers can build an entire bank in less than a year with less than 20 people and incumbents face slow erosion or sudden collapse. Recommends concrete patterns: use three horizons, separate creative core team from delivery teams, ship experiments with containers and Kubernetes, treat culture as daily practices (psychological safety, blameless inquiry), follow a CNCF over 1200 projects landscape-aware, and adopt a crisis pattern language: defensive cuts, decisive transparent leadership, and continuous adaptation.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:13Market disruptors
- 7:10Business crises types
- 8:15Slow cloud native failures
- 13:57Cloud native tools
- 20:23Jenny’s cloud native patterns
- 24:19Market collapse response
- 27:13Crisis management patterns
- 28:42Biases in crisis response
- 30:08Next steps
related talks
21mGrowing up in a cloud native org
54mCloud Native Culture
44mNine Ways To Fail at Cloud Native
37mCloud Native Technology and Cultural Context: Maximizing Business Value Across...
37mCloud Native Strategy - From Ancient Greece to Container Orchestration
28mUnleashing Innovation by Unblocking your Developers
35mTowards Cloud Native Platforms
11mKeynote: The Cloud Native Chasm