© 2025 James Hardie – Course Correction Consulting Ltd. The EASE Framework™ is a proprietary model developed by James Hardie to support the creation of psychologically safe, empowered, and strategically aligned teams. All rights reserved.
.svg)
.svg)
Cynefin separates situations into four main domains, with disorder in the middle. A situation begins with some Disorder, which means you have not yet worked out which domain applies so take a moment and define the problem or its componet parts: chaotic, complex, complicated or clear?
Most leadership mistakes begin with bad diagnosis. The Cynefin framework helps you out of Disorder (something disruptive has occurred) to distinguish between clear, complicated, complex, and chaotic situations or elements within. Momentarily, with disorder at the centre, you are not yet sure which is which. Clear problems already have a process. Complicated problems need expertise. Complex problems will need experimentation and are uncertain. Chaotic problems may need rapid stabilising action where you can. Keith Grint’s work adds a second layer by showing that different problems also require different forms of authority. Tame problems suit management, wicked problems require leadership, and critical problems need command. The practical lesson is simple: sort first, then solve. That is how you LEAD with EASE.
Leaders make better decisions when they diagnose the type of problem first, then match their response to the situation rather than forcing every issue through the same style.
Definition: The Cynefin framework is a sense making framework that helps leaders decide in context by distinguishing different domains of action. (The Cynefin Co)
Data point: Keith Grint argues that tame problems make up about 75% of professional life, which is a useful reminder not to label everything as complex or chaotic.
Read or follow on LinkedIn
It is “What kind of problem are we dealing with?”
That distinction matters because organisations often make things worse by treating every issue as though it were the same. A founder sees delays, conflict, customer complaints, or confusion and feels pressure to act fast. However, speed without diagnosis is often just expensive movement. The Cynefin framework was developed to help leaders understand their challenges and make decisions in context, not to make complexity sound intellectual. Its real value is practical. It helps you recognise what kind of situation you are in, so you can respond in a proportionate way.
Cynefin separates situations into four main domains, with disorder in the middle. A situation begins with some Disorder, which means you have not yet worked out which domain applies so take a moment. In the Clear domain, cause and effect are sufficiently obvious that routine practice, standard operating procedures, checklists, and repeatable processes work well. In the Complicated domain, the answer probably exists, but it requires analysis or expert judgement. In the Complex domain, the answer cannot be known in advance with confidence, so leaders must probe, learn, and adapt. In Chaos, some immediate action is often needed to create enough stability for thinking to resume. However, beware of the reality of Chaos or not, some people like to induce the sense of this to justify their command in a crisis, some thing may be clear, complicated or complex, even in Chaos.
"Poor diagnosis of the ‘Disorder’ we face might increase uncertainty and anxiety. In a flying emergency the first thing we did was ‘Warn the Crew’ while simultaneously establishing or maintaining a safe fight configuration. Then diagnosis began, confirming our senses with each other. This might lead to a few immediate and crisis averting actions from memory, but most actions were done systematically with reference to a process. “Take some time to do it right first time, or do it again, if you even get the chance.”" Author
That matters because disorder is not just confusion. Dave Snowden describes disorder as a state in which people often assume they already know how to act before they have properly assessed the nature of the situation. That false confidence is dangerous. The team may be arguing about solutions when the real problem is that different people are treating the same issue as different kinds of problem.
In growing businesses, the most common error is not laziness. It is a misclassification of the issues.
A routine issue gets treated as strategy. An expert issue gets handed to a committee debate. A genuinely adaptive issue gets crushed by premature process. A crisis gets over-discussed while the damage spreads. This is why some teams feel permanently overwhelmed. They are not always facing impossible problems. They are facing a mix of neglected clear issues, under-analysed complicated issues, and one or two genuinely complex tensions that have become tangled together. That is what disorder looks like in practice.
This is also why “chaos” should be used carefully. In Cynefin, chaos is a real domain, but in organisational life many situations that feel chaotic are actually evidence that easier items were not cleared earlier. If everything feels like a fire, you may not be in chaos. You may be living with accumulated disorder.
Cynefin helps you understand the terrain. Keith Grint helps you understand the leadership response.
Grint distinguishes between tame, wicked, and critical problems. Tame problems can usually be addressed with existing knowledge, expertise, and process. Critical problems require decisive command because the cost of delay is too high. Wicked problems are different. They do not have one agreed definition, do not have neat solutions, and often require the collective to engage with uncertainty and trade offs rather than wait for a technical fix. Grint links these problem types to different modes of authority: management for tame problems, command for critical problems, and leadership for wicked problems.
That sits neatly alongside Cynefin. Clear and much of complicated resemble tame territory. Chaos maps most closely to critical situations. Complex challenges often look like wicked problems, where no single expert can settle the matter and the leader’s job is to mobilise learning, judgement, and collaboration.
Grint’s answer to wicked problems is especially valuable for founders. He argues that wicked problems often need clumsy solutions, not elegant ones. Elegant solutions are internally coherent and tidy. Clumsy solutions are more pragmatic. They pull together what is available, combine perspectives, accept trade offs, and work iteratively in the real world. They are less satisfying to the ego, but often more effective in practice.
That is a useful corrective because leaders are often seduced by the idea that every serious problem must have a decisive masterstroke. In reality, issues like culture, delegation, AI adoption, cross-functional friction, retention, and founder dependency are rarely solved by one brilliant move. They are usually improved through a series of bounded experiments, clearer roles, better conversations, and more honest feedback loops. That is clumsy in the best sense.
A practical way to use the framework is to sort your live issues into four buckets.
Ask which problems are already understood and simply need consistency. These are often things like handoffs, meeting hygiene, approval thresholds, reporting cadence, onboarding steps, or service standards. Do not over-intellectualise these. Clarify them, document them, train them, and inspect whether they are followed.
Ask where the answer exists but requires expertise. This might involve legal advice, technical architecture, pricing analysis, recruitment design, workflow redesign, or regulatory interpretation. Here the right move is not more opinion. It is access to the right expert judgement and enough time to think properly.
Ask which challenges cannot be solved through certainty in advance. Culture change, behaviour change, trust repair, AI implementation, leadership succession, and innovation often sit here. In these cases, the job is to run safe to learn experiments, watch what emerges, and adapt based on signals rather than ideology.
Reserve this for genuine crisis conditions. A major outage, safety event, severe reputational incident, or destabilising external shock may require immediate direction to stop the bleeding. But once stabilised, the task shifts quickly back to diagnosis and learning. Staying in command mode too long after the immediate threat has passed is one of the classic leadership errors.
To LEAD with these ideas in mind is to:
Learn before you label. Do not rush to call something complex because it feels uncomfortable, or chaotic because it feels urgent.
Educate the team on the difference between routine, expert, adaptive, and crisis work. A shared language reduces panic and improves judgement.
Advise where expertise is needed. Not every problem is democratic. Some issues need informed diagnosis.
Delegate where local judgement is best. Complex situations often need the people closest to the work to probe and report back quickly.
Then use EASE.
Explore by separating signal from noise and identifying the real domain of the problem.
Align around the nature of the challenge, because teams often disagree on the problem before they disagree on the solution.
Support with the right environment: process for clear work, expertise for complicated work, experimentation for complex work, and calm direction for crisis.
Empower people to act inside guardrails, so the business does not depend on the founder being the only source of judgement.
My article on leadership, management, and followership in uncertainty complements this piece by showing that good leaders do not just decide, they also know when to manage, when to follow expertise, and when to loan authority to the person closest to the facts.
A second useful link is How to deal with an emergency, because it helps readers who are dealing with genuinely critical situations, rather than merely messy ones.
Many founders and entrepreneurs are strongest in the complicated domain. They like analysis, expertise, and informed decision making. That is useful, but it creates a bias. When the organisation enters complexity, leaders can overreach by trying to analyse their way to certainty. Others have the opposite bias and call everything complex because it excuses vagueness and protects them from committing to process. Neither extreme is mature leadership.
The better discipline is this: simplify what can be simplified, analyse what can be analysed, experiment where emergence is real, and stabilise fast only when the situation is truly critical. That is the practical value of Cynefin and Grint together. They are an antidote to performative leadership and a start to diagnosing reality.
How do I know whether a problem is complex or just poorly managed? If a repeatable solution already exists and the main issue is inconsistency, ownership, or discipline, it is probably not complex. Start by cleaning up the clear and complicated work first.
When should I use command and control? Use it sparingly and mainly in genuinely critical moments where delay is dangerous. Once stability returns, move back to diagnosis, expertise, and learning.
What does a safe to learn experiment look like at work? It is a small, bounded test with clear constraints, fast feedback, and limited downside. It is designed to generate learning, not false certainty.
Why do teams jump straight to solutions? Because any disorder creates some anxiety, and answers feel emotionally safer than diagnosis. Some bosses state, "Bring me solutions not problems," but premature certainty and solutionising often increases cost, conflict, and rework.
Can EASE work alongside frameworks like OKRs or SOPs? Yes. EASE does not replace operational tools. It helps leaders decide what kind of problem they are facing so they can use those tools more intelligently. EASE enables clarity, delegation, and decision making under pressure.
Snowden, D. and The Cynefin Co. “The Cynefin Framework” and related essays on disorder and sense making.
Grint, K. Wicked Problems and Clumsy Solutions: The Role of Leadership.
Grint, K. Clumsy solutions for wicked problems: decision-making in uncertainty and the role of systems leadership.