Situation Normal, Everything Must Change
summary
Argues that strategy requires visual, position-and-movement maps not buzzword lists, and gives a concrete mapping method: start with anchor user need, trace the value chain to get position, then add movement by plotting component evolution (genesis → utility). Cites a 2005 build of a serverless PaaS that grew fast but was cancelled by its parent, an Ubuntu push from ~2% to mass cloud use, and Cloud Foundry later valued at $2.8B; uses a 160-company study showing high situational awareness correlates with market-cap gain.
AI-written summary · about
chapters (23)
- 0:00Intro
- 4:50Landscape
- 6:38Chess
- 8:49Thermopyle
- 10:52Chess vs Alchemy
- 12:17Strategy documents
- 13:15Business level abstractions
- 15:24Strategy vs execution
- 17:05How come we are successful
- 18:51Maps vs Diagrams
- 20:24How to create a map
- 21:57Diffusion of innovation
- 25:02Predicting innovation
- 27:24Causation
- 28:07Creating a Map
- 30:27Doctrine
- 37:56Strategy Cycle
- 38:19First Platform as a Service
- 39:10Cloud Foundry
- 40:08Ubuntu Super
- 40:49Summary
- 41:07Understand your environment
- 41:56Question
related talks
47mSituation Normal, Everything Must Change
29mSituation Normal, Everything Must Change
21mCrossing the River by Feeling the Stones
11mSimon Wardley (Leading Edge Forum) Interview - OSCON 2014
58mFrom here to there and back again
13mSimon Wardley at SpringOne Platform 2017
13m"Introduction to Value Chain Mapping"
01h 02mFrom here to there and back again