Leading the Two-System Organisation
How Daniel Kahneman’s Thinking Styles Define Transformation Success
If you have ever presented a logical, data-driven transformation strategy (System 2) only to be met with inexplicable anxiety and resistance (System 1), you have walked into the cognitive minefield mapped by Nobel laureate Daniel Kahneman.
Organisational transformation is often designed as a rational engineering problem. However, Kahneman’s research reveals that human cognition - and therefore organisational behaviour - is dominated by automatic, intuitive, and bias-prone processing. Leading change requires moving beyond the illusion of the rational actor and engaging with how people actually think.
Here is how Kahneman’s “Thinking Styles” apply to transformation.
1. The Two Systems: Why Strategy Does Not Equal Execution
Kahneman describes the brain as operating via two systems. System 1 is fast, automatic, emotional, and always on. It handles 98% of our thinking. System 2 is slow, deliberate, analytical, and “lazy”-it requires significant energy and engages only when necessary.
Leaders design transformations using System 2 (spreadsheets, roadmaps, org charts). However, employees experience the change via System 1 (fear, habit, social intuition). When cognitive load increases - as it always does during change - System 2 depletes, and people revert to System 1 habits. So here’s the thing: You cannot “explain” a transformation into existence. You must design for cognitive load.
This aligns with Sidney Dekker’s concept of Local Rationality. When people resist a new process, it isn’t because they are irrational; it is because, given their time pressure and cognitive load (System 1 constraints), their current behaviour makes sense to them. See the previous article link below.
2.WYSIATI: The Illusion of Understanding
Kahneman’s concept of WYSIATI (What You See Is All There Is) explains that the mind constructs the best possible story from available information, completely ignoring what it doesn’t know. This leads to dangerous overconfidence; confidence is determined by the coherence of the story, not the quality of the evidence. (See also the Dunning-Kruger effect.)
Executives sit in a boardroom, look at a partial dataset, and construct a coherent (but wrong) narrative about why the transformation is failing and how to fix it. They assume their “view from the balcony” is the whole truth. Extending Dekker, leaders must actively hunt for disconfirming evidence.
Dave Snowden’s Cynefin Framework addresses this by warning against “premature categorization”. In complex domains, you cannot rely on the “coherent story” (WYSIATI). Instead, you must use Probe-Sense-Respond tests to discover what is actually happening. We will discuss Cynefin in a future article.
3. Loss Aversion: Why the “Burning Platform” Often Backfires**
Kahneman’s Prospect Theory identifies Loss Aversion: losses loom larger than gains, roughly by a ratio of 2:1. So, losing £100 feels twice as bad as gaining £100 feels good. Change communications usually focus on future benefits (gains). However, employees immediately feel the threat to their current status, expertise, or comfort (losses) - Safety. Even if the net outcome is positive, the psychological weight of the loss triggers resistance. You cannot simply outweigh the loss with promises of future profit. You must address the loss directly.
This supports Ronald Heifetz’s principles of Adaptive Leadership: “Identify and Name the Losses.” Heifetz argues that people don’t resist change; they resist loss. Leaders must acknowledge what is being left behind to help people navigate the transition. We will discuss Heifetz in a future article.
4. The Planning Fallacy: The Optimism of Roadmaps
Humans systematically underestimate the time, costs, and risks of future actions while overestimating benefits. This is the Planning Fallacy. It persists even when we have data from previous failed projects, because we take the “inside view” (focusing on our specific case) rather than the “outside view” (looking at the statistical baseline of similar cases). We’ve all seen it before: the 3-year transformation roadmap is almost guaranteed to be wrong. It assumes a linear progression that reality just punches in the face...
As the Lean community has been preaching for decades…Stop delivering in large batches! In addition to probe-sense-respond and shipping change in small pieces, shift to Reference Class Forecasting - looking at how long similar projects actually took and iterating. We will have a lot to say about this basic principle in future.
This lean idea resonates with Eric Ries’s Lean Startup approach. Because we cannot predict the future (due to the planning fallacy), we must use the Build-Measure-Learn loop to iterate our way to the truth. It also reinforces Goldratt’s warning that local efficiencies (keeping people busy) do not equal global throughput; strict plans often create “muda” (waste).
5. The Peak-End Rule: Designing the Change Experience
Kahneman distinguishes between the “experiencing self” and the “remembering self.” The remembering self judges an experience not by the total sum of feelings, but by the Peak-End Rule: the most intense moment (peak) and how it finished (end). Duration is largely ignored.
Think back to the last big transformation you went through and how you felt at the end. Leaders often let a project drag on to a whimpering, inconclusive finish. Thank goodness, that’s finished! If the “end” is weak or the “peak” was a moment of high stress, the entire transformation will be remembered as a failure, regardless of the actual outcome.
We need to manage the narrative arc. Tell the story. Orchestrate regular small “short-term wins” to create positive peaks, as suggested by John Kotter, and ensure distinct, celebratory endings for project phases to encode positive memories. Story telling will be itself a key narrative arc in this series.
6. Expert Intuition: When to Trust Yourself
As leaders, we often rely on intuition. Kahneman (collaborating with Gary Klein) found that Expert Intuition is only valid in “high-validity environments” where there is immediate, clear feedback (like firefighting or chess). Therefore, in business strategy terms feedback is delayed by months or years and executive intuition is often statistically unreliable. Do not trust “gut feel” for long-term strategy. Trust process over confidence.
W. Edwards Deming argued that “Experience alone teaches nothing... Prediction requires theory”. Without a system to validate our intuition (like the scientific method or PDCA cycles), we are just guessing. I will bring the many threads relating to probing, sensing, building and learning together as we get into future articles.
It may all seem rather diffuse at the moment, but I promise it will all start to come together!
(An Organisational Prompt is something you can do now….)
Organisational Prompt
The previous prompt asked about weak signals.
Identify the perceived LOSSES you need to address due to transformation and what you can do to shift people to System 2 thinking - evidence of local improvements - due to the transformation?
The big idea here is that we love to live in system 1 and feel the reassuring glow of positive feedback. We need to activate system 2 and try to tease out what our teams are not allowing themselves to see.
Further Reading
Daniel Kahneman: Summary of his work on Prospect Theory.
Ronald Heifetz: Resources on Adaptive Leadership.
Disclaimer
I write about the industry and its approach in general. None of the opinions or examples in my articles necessarily relate to present or past employers. I draw on conversations with many practitioners and all views are my own.