---
title: "Developing Critical Team Thinking"
url: "https://www.5whys.com/articles/developing-critical-team-thinking.md"
canonical: "https://www.5whys.com/articles/developing-critical-team-thinking.html"
published: "2013-02-25T01:08:47.005000+00:00"
updated: "2013-02-25T01:08:47.005000+00:00"
tags: ["Critical Thinking", "Meta"]
author: "Roy Osherove"
description: "How the effectiveness, novelty and self-direction of critical thinking map onto growing a self-organizing team that keeps experimenting."
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/"
---

# Developing Critical Team Thinking

Borrowing a few terms from critical thinking, this is another map, or model, of how I feel I need to guide my teams. When do I feel like I have successful gotten my team where they could have been all along?

Here is a great quote [from this PDF file](http://www.aft.org/pdfs/americaneducator/summer2007/Crit_Thinking.pdf) on critical thinking:

> From the cognitive scientist’s point of view, the mental activities that are typically called critical thinking are actually a subset of three types of thinking: reasoning, making judgments and decisions, and problem solving.
>
> I say that critical thinking is a subset of these because we think in these ways all the time, but only sometimes in a critical way. Deciding to read this article, for example, is not critical thinking. But carefully weighing the evidence it presents in order to decide whether or not to believe what it says is.
>
> Critical reasoning, decision making, and problem solving—which, for brevity’s sake, I will refer to as critical thinking—have three key features: effectiveness, novelty, and self-direction.
>
> Critical thinking is **effective** in that it avoids common pitfalls, such as seeing only one side of an issue, discounting new evidence that disconfirms your ideas, reasoning from passion rather than logic, failing to support statements with evidence, and so on.
>
> Critical thinking is **novel** in that you don’t simply remember a solution or a situation that is similar enough to guide you. For example, solving a complex but familiar physics problem by applying a multi-step algorithm isn’t critical thinking because you are really drawing on memory to solve the problem. But devising a new algorithm is critical thinking.
>
> Critical thinking is **self-directed** in that the thinker must be calling the shots: We wouldn’t give a student much credit for critical thinking if the teacher were prompting each step he took.
>
> —D.W.

the last part hit home on many levels about what it means to coach someone to learn a new skill.:

> Critical thinking is **self-directed** in that the thinker must be calling the shots: We wouldn’t give a student much credit for critical thinking if the teacher were prompting each step he took.

Learning a new skill  means that they do not need **you** there to continue doing something. that you are no longer a bottleneck.

**A self organized team is a self-directed team**, as far as critical thinking is concerned. But we want our team to not only be self directed, but also **effective**, by avoiding common pitfalls as as discounting new ideas, seeing only one side of an issue, etc. Learning to be effective is to acquire a set of new skills, of each of these pitfalls, if they occur for members of the team.

A critical thinking team uses **novel _ideas,_** not always blindly applying templates to different problems, but always experimenting, and finding new, better ways, of doing new, or even the same things. there is always something new to be learned.

As I usually say, if everyone is too comfortable, you’re not learning anything. so something _new_ has to jump into the equation in the form of a new experiment (‘what if we did no iterations for 3 months?’)

## Read next

- [Five Questions to ask yourself when getting advice about team leadership](https://www.5whys.com/articles/five-questions-to-ask-yourself-when-getting-advice-about-tea.html): Questions for testing any team leadership advice against the three team maturity stages, plus bonus questions about the author's hidden assumptions.
- [When I Want to Give Up](https://www.5whys.com/articles/when-i-want-to-give-up.html): Roy Osherove shares the gumption traps picture he keeps on his office door and how naming his feelings helps him move on when he wants to give up at work.
- [The architect as a leader, and other specialists](https://www.5whys.com/articles/the-architect-as-a-leader-and-other-specialists.html): Why an architect or any specialist on a team is a bottleneck, and should act as a coaching leader who spreads knowledge until they are no longer needed.


---

## 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/
