---
title: "Elastic Leadership Team Survival Vs. Team Chaos Vs. Cynefin"
url: "https://www.5whys.com/articles/elastic-leadership-team-survival-vs-team-chaos-vs-cynefin.md"
canonical: "https://www.5whys.com/articles/elastic-leadership-team-survival-vs-team-chaos-vs-cynefin.html"
published: "2012-07-30T14:16:05.833000+00:00"
updated: "2012-08-09T17:26:01.047000+00:00"
tags: ["Meta"]
author: "Roy Osherove"
description: "Why the first phase of Elastic Leadership was renamed from chaos to survival to avoid clashing with Cynefin, and how the three team phases are defined."
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# Elastic Leadership Team Survival Vs. Team Chaos Vs. Cynefin

I've decided that the word '**chaos**' isn't a good match to describe the phase where a team has no time to learn. Instead, the word 'survival' is going to be used from now on. There are several reasons for this: 1) The word 'chaos' is already used in the context of another decision framework called '[Cynefin](http://en.wikipedia.org/wiki/Cynefin)'.   Cynefin is a powerful framework that uses scientific arguments to describe various states teams and systems are in. 'chaos', in the context of Cynefin, is a state where given an action in the system, the results will be totally random.  In that sense, 'chaos' in the elastic leadership framework as I present in this blog, means something else. 'chaos' (or 'survival' from now on), is a state where decisive action is needed, and a specific set of results is expected.  My notion of elastic leadership does not deal with a state where there is no telling what action needs to be taken. It divides the world of states into 'survival' (no time to learn), 'learning', and 'self organizing'.  In terms of Cynefin, I only deal with complex and complicated systems. Though I'm not sure where 'software team' as a system lies between these two notions. 2) The word 'Chaos' was initially chosen out of necessity. I had no better word to describe this phase. After  discussing the Cynefin framework ideas with Dave Snowden via email, the word 'survival' came to me, and I think it much better described the phase I believe most software teams are, unfortunately, in. There for, a team can have three phases:

- **Survival phase** (where most teams I see are in) -- in which team has no time to learn -- requires a more command and control type of leadership to create that learning time from nothing.
- **Learning phase**  -- where a team has time to learn and is using it -- requires coach like leader, with bursts of control when things will take too long to learn the hard way (choosing no source control, for example)
- **Self Organization Phase** -- Where teams can solve their own problems -- requires more of a facilitator type of leader, that does not tell people what to do, but simply provides constraints and end goals. The team will get there on its own.

A team can move between all three phases in a matter of days, really.  The leader should detect this phase change, and change their leadership type accordingly.

## Read next

- [On time, with quality - why is this mostly failing?](https://www.5whys.com/articles/on-time-with-quality-why-is-this-mostly-failing.html): Why teams fail to ship on time with quality while stuck in chaos, and why team leaders must remove commitments to make time to learn and practice.
- [Signs you might be in survival mode](https://www.5whys.com/articles/signs-you-might-be-in-survival-mode.html): A list of early warning signs that a software team is in survival mode, such as constant urgency, missing context, no time to reduce risk and long stress.
- [Elastic Leadership in Devops Survival Mode](https://www.5whys.com/articles/elastic-leadership-in-devops-survival-mode.html): A look at a DevOps Guys post in which command and control ended production fires and freed time to learn, read as Elastic Leadership in survival mode.

## Topic

- [Survival Mode](https://www.5whys.com/topics/survival-mode)


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/
