There’s more to setting up a PMO than setting up a standard stage-gate model for project delivery. PMOs today face a wide spectrum of project types. There are the straightforward repeatable initiatives through to highly ambiguous programmes. As a PMO leader, you might have experienced the frustration of applying a one-size-fits-all governance process, only to see it falter on complex projects. The Cynefin framework offers a way out of this dilemma. Cynefin is pronounced kuh-nev-in, a Welsh word roughly meaning “habitat” or “place”. It is a sense-making model that helps leaders categorise situations and tailor their decision-making approach accordingly. Dave Snowden created the framework, beginning the work at IBM in 1999, and refined its language with Mary Boone in a 2007 Harvard Business Review article, “A Leader’s Framework for Decision Making”.
In plain terms, it defines five domains of complexity: Clear, Complicated, Complex, Chaotic, and Confused (Aporetic). Each domain requires a different style of management and governance. By understanding these domains, a PMO can avoid over-engineering simple scenarios and, equally, avoid trying to force complex or chaotic situations into standard processes that won’t fit. The result is a more adaptive PMO that supports better outcomes across the project portfolio.
The Five Domains of Cynefin
Understanding each Cynefin domain is key to applying the framework. Below, we explain the five domains with definitions and examples tailored to a PMO context. These examples show how various project scenarios might fall into each domain and how a PMO leader can recognise them.
1. Clear Domain – “Known Knowns”
The Clear domain represents situations that are well-understood and highly predictable – the known knowns. The domain now called Clear was originally named Simple, then briefly Obvious. Here, the relationship between cause and effect is obvious to everyone. The right approach is to apply established best practices and standard operating procedures. Projects in the Clear domain will typically be using checklists and templates with limited modifications or tailoring. Projects, initiatives, or workflows here should take the view that if a tried-and-tested method exists, use it and move on. Cynefin describes the decision making approach here as “sense – categorise – respond”: identify the situation, classify it, and apply a proven solution.
Example: Think of an SSL certificate update project that your PMO oversees each year. The requirements are well-defined and the process is the same each time. This is a Clear domain project – you’d use a standard checklist and timeline. The PMO’s role here is to ensure the team follows the best practice procedure (e.g., using last year’s plan as a template) and to monitor progress through routine status reports. Because the work is predictable, governance can be lightweight and simply confirm that standard process is being followed.
2. Complicated Domain – “Known Unknowns”
In the Complicated domain, there is a clear relationship between cause and effect, but it may not be obvious to everyone without analysis or expertise. These are known unknowns – you know what you need to achieve, but determining how requires examination by subject matter experts. Good practices (as opposed to best practices) apply here, meaning there may be multiple right ways to approach the problem. The decision-making approach is “sense – analyse – respond”: assess the situation, bring in expertise, analyse options, and then implement a solution.
Many traditional projects fall into this domain – complicated but manageable with the right expertise. For example, consider a project to implement a new finance system across the organisation. The project’s outcome is understood, but figuring out the optimal configuration or integration requires specialists (business analysts, IT architects) and careful planning. The PMO should ensure experts are engaged in the project team, and/or supporting the sponsor, and that there is detailed planning, and risk analysis throughout the project. Governance might involve stage gates, design reviews, or external consultations to ensure due diligence. Unlike the Clear domain, a bit of critical thinking and options analysis is necessary, but once the plan is set, the project can proceed in a controlled fashion.
Example: A portfolio may include a project to upgrade an enterprise IT Service Management platform. It’s complicated: there are many interdependent components and possible solutions. But it is not truly novel. As a PMO leader, you’d assemble a team of experienced project managers and technical experts to devise the plan. You might leverage “good practice” frameworks or methodologies (e.g. ITIL for process, or vendor implementation guidance). You may decide to bring in external expertise to consult on the best approach. The PMO would use thorough oversight here: for instance, requiring clear documentation approvals and conducting stage gate assurance reviews to verify the project is on track. The key is that the PMO ensures the project has expert guidance and robust analysis to navigate the complexity, but expects that with enough knowledge, the project will have a predictable solution.
3. Complex Domain – “Unknown Unknowns”
The Complex domain is where things get lively – and challenging – for PMOs. Here we deal with unknown unknowns: situations where cause and effect can only be understood in hindsight, and no amount of upfront analysis can guarantee the right answer.
Many innovative or strategic initiatives fall into the Complex domain. Examples include digital transformation efforts, cultural change programmes, or developing a product for an emerging market. In such cases, outcomes are uncertain and there are no proven best practices that guarantee success. The appropriate approach is “probe – sense – respond”: conduct safe-to-fail experiments, learn from results, and gradually steer the project based on what works.
For PMO leaders, managing Complex domain projects means embracing adaptability and learning. Rather than demanding a detailed fixed plan upfront (which would likely be fiction), the PMO can set up frameworks for experimentation. Dave Snowden, Cynefin’s creator, advocates for running multiple safe-to-fail experiments in parallel to see what approaches yield valuable results.
The PMO can encourage project teams to try different tactics on a small scale, gather data, and then amplify the strategies that work (and dampen those that don’t). Governance in the Complex domain should be light-touch and flexible – for example, shorter review cycles focused on learning (what did we discover this iteration?) rather than strict compliance to a preset plan. This domain calls for adaptive leadership: the PMO must be comfortable with some ambiguity and support the team in exploring the problem space.
Example: Imagine your organisation undertakes an AI innovation programme to improve customer experience. No one has a certainty on how the customers will respond or what features will succeed. As a PMO, you classify this as Complex. Instead of a rigid project plan, you guide the team to run a series of pilot experiments (perhaps A/B testing different AI features with a subset of users). You establish a governance approach that focuses on metrics and feedback – the team reports on what they’ve learned each sprint, and you help remove barriers so they can adapt quickly. The portfolio governance might allow this project more flexibility in scope and timeline, recognising that discovery is part of the process. By using Cynefin’s Complex domain guidance, the PMO manages expectations with the business, ensuring the team isn’t penalised for changing course. In this context change is a sign of learning, not a failure of planning.
4. Chaotic Domain – High Uncertainty, Urgent Action
In the Chaotic domain, we face situations with no apparent cause-and-effect linkage at the outset. This is true uncertainty – things are changing rapidly and nothing is stable. Crises and emergencies typically fall here: for example, a sudden cyber-attack on the company or a major regulatory shock that forces immediate changes.
In a chaotic scenario, trying to analyse or experiment before acting is futile, because the situation can deteriorate while you ponder. The Cynefin guidance is to “act – sense – respond”: take swift action to establish some order, then observe the effect, and respond accordingly.
The goal in chaos is to impose enough stability to move the situation into the Complex (or Complicated) domain as quickly as possible.
For PMO leaders, encountering a Chaotic domain situation means stepping into a crisis-management mode. Normal project governance is thrown out the window – there’s no time for committees or detailed plans. Instead, the PMO might assume a coordination role to enforce rapid response. This could mean empowering a special task force or war room with the authority to make immediate decisions.
Examples in PMO context could include handling a project that suddenly loses its executive sponsor and faces political turmoil, or coordinating the company’s projects during a pandemic outbreak in the workforce. In such moments, the PMO’s responsibility is to act decisively to contain the chaos (for instance, pausing non-critical work, allocating extra resources, or communicating urgent directives). Only after stabilising do you assess what happened (“sense”) and guide the next steps to recover (“respond”).
Example: Consider a scenario where a key programme in your portfolio has a major vendor fail suddenly, throwing the project into disarray. This is chaotic – there’s no immediate pathway to success and every moment counts to prevent total failure. As a PMO leader, you might impose a temporary structure: assign a crisis manager to the programme, hold daily stand-up calls with all stakeholders to triage issues, and perhaps put less critical projects on hold to free up resources. The emphasis is on quick action – for instance, bringing in a backup vendor overnight. Your oversight is very hands-on in the moment (micro-governance, one might say), but this is temporary. Once the situation stops free-falling, you’ll transition the project into Complex or Complicated domain management.
5. Confused (Disorder/Aporetic) Domain – Unclear State
At the centre of the Cynefin framework is the Confused (or Disorder/Aporetic) domain. This represents situations where it’s not yet clear which of the other domains apply.
In a sense, it’s the state of not knowing what state you’re in. Often, when a new problem arises, we start in this Confused domain until we gather enough information. The danger is remaining in confusion and applying the wrong management approach by assumption or bias. The guidance for this domain is to break the situation down and assign parts to the other domains as soon as possible.
If a challenge is too broad or unclear, try to triage its aspects: perhaps some parts are Clear (well-understood tasks), others are Complex (requiring research), etc. In some cases, leaders might deliberately introduce an “aporetic turn,” meaning they acknowledge confusion and encourage questioning to stimulate fresh thinking. But generally for PMOs, the Confused domain is a transitional space. The goal is to figure out what you’re dealing with.
Example: You’re handed a new strategic initiative with an objective like “Improve organisational agility,” but it’s initially just a slogan with no clear scope. As a PMO leader, you find yourself in the Confused domain – it’s unclear if this is a straightforward training project (Clear), a multi-faceted cultural change (Complex), or perhaps a bit of both. The best move is to consult stakeholders and decompose the challenge. You might break it into parts: one workstream to implement agile tools (Complicated, requiring experts), another to run pilot workshops for culture change (Complex, requiring experiments). By doing so, you dispel the confusion and manage each part with the appropriate domain approach. In practical terms, the PMO might initially initiate a small discovery project to gather information (for example, run a survey or a few interviews) – essentially “sensing” the situation. Once the situation is better understood, the initiatives can be separated into Clear, Complicated, Complex and/or Chaotic elements which can be managed accordingly.
While the Cynefin Framework helps categorise projects by complexity, the Biomes of Delivery model from HotPMO builds tailored environments for each domain. It aligns governance and tools to fit the context, whether it’s a Compliance Biome for predictable work or a High Innovation Biome for complex, experimental projects. For example, the High Innovation Biome suits the Complex domain, focusing on iteration, learning, and adaptability.
Applying Cynefin in PMO Practice
Understanding Cynefin’s domains is just the start. The real value comes from applying this framework to how your PMO operates. By integrating Cynefin into portfolio governance, oversight, and coaching, PMO leaders can tailor their approach to fit each project’s context, rather than enforcing a rigid model across the board. Below are key areas of PMO responsibility and guidance on using Cynefin insights in each:
Portfolio Governance and Prioritisation with Cynefin
At the portfolio level, Cynefin can inform how you select and structure your mix of projects. Rather than viewing all initiatives through the same lens, a PMO can categorise proposed projects by domain early on. For example, you might label projects or programmes as Clear, Complicated, Complex, or Chaotic based on their characteristics and uncertainty. This helps in making governance decisions: clear projects might be fast-tracked with minimal oversight, while complex projects might be given exploratory charters or incremental funding.
Using the Cynefin framework in portfolio management ensures that investment and oversight are aligned with the nature of the work – you avoid smothering innovative projects with bureaucracy, and you avoid underestimating the oversight needed for critical but complicated projects. In practice, this could mean having different portfolio criteria or stage gates depending on the domain.
A Complex domain initiative, for instance, might require evidence of learning (e.g. results from a pilot) before moving to the next phase, whereas a Complicated domain project might require a detailed business case and expert sign-off.
Another aspect is portfolio balance. Cynefin encourages a healthy mix: you wouldn’t want all your projects to be high-risk Complex experiments, but you also might miss opportunities if everything is kept in the Clear/Complicated space. Some organisations use Cynefin to ensure they have a portion of safe-to-fail experimental projects in the portfolio for innovation. The PMO can use this thinking to argue for a strategic balance between predictable projects (“hygiene” or maintenance work) and innovative, exploratory initiatives. By doing so, the PMO enables short-term results while also fostering long-term growth and adaptability.
Governance in action: Suppose during portfolio planning, a proposal comes up for an unproven technology pilot (Complex domain). Instead of evaluating it with the same criteria as a routine upgrade, the PMO might create a separate path – approving a small-scale experiment budget rather than a full rollout. This flexibility in governance, guided by Cynefin domain, helps match the decision criteria to the project type, improving the quality of portfolio decisions and ultimately project outcomes.
Project Oversight and Assurance
Not all projects should be monitored and controlled in the same way. Cynefin provides a lens for PMO oversight to be context-sensitive. For Clear projects, oversight can be checklist-driven and focused on compliance with the known process. Regular status reports and automated metrics might suffice, and assurance (health-check or audit) can be a simple tick-the-box exercise. In contrast, for Complex projects, traditional status reports might not tell the full story – a project could be “off plan” yet still healthy if it’s pivoting after new learnings. Here, PMOs should adjust oversight to focus on learning and adaptation rather than strict variance from plan.
For example, an assurance review for a Complex domain initiative might ask, “What experiments have you run and what did you learn?” instead of “Are you on time and on budget?”. This kind of adaptive assurance ensures the project is following emergent good practice (probe-sense-respond) and not stuck in analysis paralysis or chaos.
In Complicated domain projects, PMO oversight might emphasise expert peer reviews and risk management. Since these projects benefit from analysis, the PMO can schedule technical stage gates, architecture reviews, or external quality assurance at key points. The governance style is heavier than Clear but more plan-based than Complex. You ensure that good practices are being followed (e.g., “did we evaluate multiple options before choosing this vendor?”).
Meanwhile, Chaotic projects (or projects in a temporarily chaotic phase) may require the PMO to take a direct control role until the chaos subsides. This could involve daily checkpoints or even embedding a PMO representative in the project team during the crisis. The key is to be hands-on to restore order, then step back as soon as the project moves into a Complex/Complicated state.
A smart PMO will also use Cynefin to tailor its assurance checklists or frameworks. For instance, a PMO could maintain different health check questionnaires for different domains: a clear project gets a straightforward audit of process compliance, while a complex project gets an advisory review focusing on whether the team has the right environment for innovation (e.g., support from leadership for experimentation, fast feedback loops, etc.). By aligning oversight with domain, the PMO avoids two pitfalls: overcontrol (which can smother a complex project’s agility) and undercontrol (which can let a predictable project run into easily avoidable issues). Adapting oversight in this way builds credibility with project teams – they see the PMO adding value by meeting them where they are, not imposing irrelevant hurdles.
The Biomes of Delivery approach dovetails effectively with Cynefin’s recommendation for context-sensitive governance. By establishing distinct biomes, such as Compliance Biomes for predictable work or High Innovation Biomes for exploratory initiatives, PMO leaders can create governance structures that match the complexity of the work. This alignment prevents the ‘one-size-fits-all’ approach from stifling innovation or underestimating risk. When applying Cynefin’s principles, PMO leaders can leverage Biomes of Delivery to operationalise governance practices that are tailored to the specific needs of each domain.
Coaching and Supporting Project Managers
One of the PMO’s roles is to develop project management capability in the organisation. Cynefin can be a powerful coaching tool to help project managers (and teams) succeed in different environments. Project managers often default to the methodologies they know, but those might not fit a new challenge. By introducing the Cynefin model, a PMO can coach managers to first assess the complexity of their project and then choose an approach. For example, if a project manager is trying to run an R&D-heavy initiative (Complex domain) with a rigid Waterfall plan, the PMO can gently course-correct by highlighting the domain mismatch – “This is an unknown unknowns situation, perhaps we need to incorporate iteration and experimentation.” Conversely, if a project is clearly in the Clear domain but the team is overengineering the solution, the PMO can coach them to simplify: “Don’t reinvent the wheel – a best practice template exists.” In essence, the PMO helps project managers expand their toolkit and apply the right technique to the right problem.
Practically, this might involve training sessions or playbooks aligned to each Cynefin domain. The PMO could provide:
- For Clear projects: templates, checklists, and “best practice” guides so even less-experienced PMs can follow proven procedures.
- For Complicated projects: access to experts or knowledge bases, and advice on analytical techniques (e.g., SWOT analysis, Monte Carlo simulation for risk) to make informed decisions.
- For Complex projects: coaching in agile methodologies or iterative frameworks, and creating a safe space for them to report failures or surprises without blame (since those yield important insights). The PMO might encourage techniques like safe-to-fail experiments and teach how to design those within project constraints.
- For Chaotic situations: crisis management training and scenario drills. A PMO might establish an emergency protocol that any PM can invoke (like an escalation path straight to leadership and a predefined “stop everything” authority for severe incidents). Knowing this exists can empower project managers to act decisively when chaos strikes, without waiting for permission in a truly time-sensitive crisis.
- For Confused situations: mentoring on problem decomposition. A PMO could introduce facilitation techniques for sense-making (like workshops to map out what is known vs unknown). Essentially, teaching managers how to quickly identify what domain they’re in and not panic if initially things are unclear.
By tailoring its coaching and support to the Cynefin domains, the PMO builds a more resilient project management community. Project managers learn to recognise complexity and adapt their style. Over time, they become comfortable navigating uncertainty – they know when to follow the book, when to bring in an expert, when to experiment, and when to take swift action. This directly translates to improved project delivery. Snowden and Boone’s Harvard Business Review article, A Leader’s Framework for Decision Making, makes the underlying case: leaders make better decisions when they identify which context they are in and match their approach to it. The PMO essentially becomes a champion of contextual leadership, growing the next generation of project leaders who can handle both the “art and science” of delivery.
Adapting Governance for Better Outcomes with Cynefin
Adopting the Cynefin framework within a PMO is ultimately about improving project outcomes through contextual governance and support. When PMO leaders adjust their approach based on a project’s domain, projects are more likely to get what they need to succeed. Imagine the difference in results between a PMO that blindly applies the same checklist to every project and a Cynefin-aware PMO that provides just enough process for ordered projects, and supportive flexibility for complex ones. The latter will likely see higher project success rates, more innovation, and faster recovery from setbacks.
By using Cynefin, no energy is wasted overthinking the routine, and at the same time the PMO never tries to force a complex challenge into a standard solution. In practice, this means simple projects aren’t burdened by bureaucracy (they finish faster and with less fuss), while complex initiatives aren’t suffocated by unrealistic plans (they’re free to discover the viable path as they progress). Teams feel empowered because the oversight “makes sense” for the work they’re doing. Executives see value because the PMO focuses its attention where it’s needed most – heavy control on high-risk predictable work, and guidance and learning on high-uncertainty innovative work.
Finally, integrating Cynefin into PMO practice fosters a culture of learning and adaptation. The organisation becomes more adept at handling uncertainty because the PMO is actively managing complexity, not ignoring it. Over time, patterns from complex and chaotic projects can even inform strategy – the PMO can feed back lessons into portfolio decisions (a virtuous cycle of learning). It’s no surprise that the Cynefin framework has been embraced in fields from software to healthcare to government for exactly these reasons.
By adapting your governance and coaching approach based on Cynefin’s insights, your PMO can significantly improve project and programme outcomes, ensuring that each initiative is managed with a style that fits its context.