Consequences of Thinking, Fast and Slow – Blog Series

Thinking, Fast and SlowHave you read the book Thinking, Fast and Slow? Getting asked that occasionally I did little more that watch a video of it from AsapSCIENCE), so that I could nod vaguely as the person who asked me talked about it. Picking it up more than a couple of years after its release I made my way through it all, pausing frequently. Pausing because it’s information dense and I needed to process what I was reading. And as I processed, it made me think about what it means for how I teach and coach people.

Instead of explaining the book, I’m writing up what I think the consequences are of the different heuristics and biases for aspects like: user interviews and research, classroom setup and teaching, outcomes of software releases, organizational change, planning and estimation, shared understanding and more. While I could attempt to overwhelm you with all the information in one blog post, I’d like to turn this into a series. I am hoping that doing it this way will invite more conversation, rather than stuffing them all into one enormous post that you’ll scan and mostly ignore.

Have you read the book? What do you think about it? What consequences have you detected for the way you behave, or for those around you?

If you haven’t read the book and wonder if you should, there are many reviews of the book, and I can suggest How to Dispel Your Illusions by Freeman Dyson. If you don’t have that kind of time but want to nod along in a knowing way, here’s the video I mentioned:

This entry was posted in #agile explained and tagged , , . Bookmark the permalink.

7 Responses to Consequences of Thinking, Fast and Slow – Blog Series

  1. Phil Kirkham says:

    I’m halfway through the book ( yeh, I’m taking it slow) so will be really interested in following this series and reading what lessons and thoughts you have taken from it.

    • aaron says:

      Thanks, Phil
      I took it pretty slow, too and this is allowing me to go through it again. Recall those lightbulb moments and gain a deeper understanding. Hope you enjoy!
      Sincerely,
      Aaron

  2. This is indeed a great book, and I also wrote a series of posts based on it:

    http://effectivesoftwaredesign.com/tag/psychology/

    I will appreciate to start a discussion on the effects of cognitive biases on software development!

    • Aaron Sanders says:

      Thanks for your comment, Hayim.

      I looked briefly at your series and see I have a lot more reading to do. 🙂 This is such a deep subject with so many implications and perhaps it’s a reference bias, but it sure has me thinking! I look forward to reading your series in depth, seeing how it might affect what I would want to write. It also encourages me to comment on your writing and hopefully further the conversation.

      Kindly,
      Aaron

  3. Jean Tabaka says:

    I love the video Aaron! Yes, I remember reading about everyone of those examples in the book and then going, “DOH!” I love Kahneman’s writing style, so openly witty. He clearly loves his subject and has great fun both with his experiments and with his writing. I think I want to be him when I grow up. Yes, the book is dense, but you and I agree: it is well worth it! And, I can’t wait to get a bunch of Agilists together with their System 1 brains acting as if they are System 2 brains :-))). New mantra: “Biases Happen” 🙂

    • Aaron Sanders says:

      Yes they do, Jean. Yes. They do. 🙂 It has me in a state of meta-cognition and more aware of my own biases. Not that I can change them. 😛 I’m thinking for the next one I want to write about what came up for me for how his work affects how I think about teaching.