From Complexity to Clarity

The cost of doing without is equally visible at ordinary scale. The Project Management Institute reports that fewer than two thirds of projects meet their original goals, that a meaningful share fail outright, and that for every billion dollars invested, organisations forfeit well over a hundred million to poor delivery [3]. The encouraging counterpoint is that high performers convert nine projects in ten into successes while low performers manage barely one in three, and the gap between them is driven by capabilities an organisation can deliberately build rather than by luck.

This is the territory in which Kairos works, and the conviction behind its practice that a framework is a strategic asset rather than an administrative tax. The argument of this article is that the difference between the high performers and the rest is rarely a single heroic decision. It is the quiet, compounding advantage of a framework that has been designed with intent, populated with capable people, and grounded in a clear set of principles. Those principles, in the Kairos articulation, are the 6Cs. To understand why they matter, it helps first to be precise about what a framework actually is, and what it is not.

Kairos approaches this work by embedding within client teams rather than handing over a report, an ethos set out in its core values. The framework that results is therefore owned by the people who run the projects, which is the only condition under which a framework survives contact with reality.

What a Project Management Framework Actually Is

A project management framework is frequently mistaken for its most visible artefacts. People point to a folder of templates, a stage-gate checklist or a reporting dashboard and call that the framework. Those artefacts are outputs of the framework, not the thing itself. The framework is the coherent system of governance, method, measurement and behaviour that determines how an organisation conceives, selects, executes and closes its projects. It answers the question of how work gets done here, in a way that holds whether the project is a coastal terminal, an enterprise software rollout or a vessel refit.

It is useful to distinguish a framework from a methodology. A methodology, such as a stage-gate model, a critical-path schedule discipline or an agile cadence, is a defined way of executing work. A framework is the larger container that decides which methodologies are appropriate for which work, how they connect to governance, and how performance is judged. The leading bodies of knowledge reflect this layering. The Project Management Institute standard has moved progressively away from a prescriptive catalogue of processes toward a principles-based orientation, and its eighth edition distils practice into six principles supported by a set of outcome-focused performance domains [4]. The PRINCE2 method, by contrast, retains a more structured set of principles, themes and processes, but is equally explicit that it must be tailored to the project environment rather than applied by rote [5]. A framework is where that tailoring decision lives.

Governance as the load-bearing wall

If a framework has a single load-bearing element, it is governance: the architecture of decision rights, accountability and escalation that tells everyone who may decide what, and under which conditions a matter rises to a higher authority. Ralf Müller and colleagues place governance at the centre of project performance, tracing a line from corporate governance at board level, through the management tier responsible for execution, down to the governance of the individual project [6]. Where that chain is clear, decisions are made at the right level and at the right time. Where it is ambiguous, projects stall in the space between people who each assume someone else holds the authority to act.

Governance is also what makes the rest of the framework credible. A risk register that no one is accountable for is theatre. A change-control process with no defined approver is an invitation to scope creep. The components of a framework only function because governance gives them teeth, which is why Kairos treats governance design, not template design, as the first act of building a framework. For asset-intensive and contract-heavy environments, that governance extends naturally into the management of agreements themselves, a discipline Kairos addresses through its contract management solutions.

The Evidence: Why Frameworks Earn Their Keep

Scepticism about frameworks is reasonable and should be welcomed. Many organisations have lived through a heavy, bureaucratic methodology that slowed everything and improved nothing. The honest question is therefore not whether process is virtuous in the abstract, but whether a well-constructed framework measurably improves the odds of success. The research record answers in the affirmative, with appropriate nuance.

The most direct evidence comes from Robert Joslin and Ralf Müller, who surveyed project managers across multiple continents to test whether the methodology a project uses actually affects its outcome. They found a positive relationship, and quantified it: the elements of the project management methodology accounted for roughly twenty-two percent of the variation in project success [7]. For a single factor in a field crowded with variables, from stakeholder behaviour to market conditions, that is a substantial share. Their work carries a second, subtler finding that matters for design. The effect of a methodology is moderated by governance and by context, meaning a method imported wholesale without regard to the organisation around it delivers far less than a method fitted to its setting [6]. A framework, properly understood, is precisely the mechanism that performs that fitting.

The institutional data reinforces the academic finding. Recall the Project Management Institute figures cited earlier: high performers succeed on roughly ninety percent of projects against barely a third for low performers, and ineffective project management wastes many times more money than disciplined practice [3]. In the institute’s measurements, the share of every invested dollar lost to poor performance has hovered around a tenth, easing to roughly nine percent in stronger years and rising above eleven in weaker ones [8], [9]. The deciding variables that separate the two groups, including an engaged executive sponsor, mature portfolio practices and the disciplined tracking of benefits beyond project closure, are not innate traits. They are exactly the capabilities a framework institutionalises.

None of this should be read as a claim that more process is always better. The same body of research is clear that completeness must be matched to context, and Flyvbjerg’s diagnosis of overruns points not at a shortage of paperwork but at weak front-end planning and, more uncomfortably, at optimism bias and the strategic misrepresentation of costs and benefits during approval [2]. A framework helps here not by adding bureaucracy but by forcing honest estimates, independent challenge and disciplined decision-making at the front end, where the largest errors are made and the cheapest corrections are available. The value of the framework, in other words, lies in the behaviours it makes routine, which returns us to the 6Cs.

The 6Cs: A Human Spine for the Framework

Frameworks fail less often on their diagrams than on their behaviour. A governance chart can be impeccable and still be ignored. A methodology can be documented in exhaustive detail and still be bypassed under deadline pressure. The purpose of the 6Cs is to name the behavioural conditions under which a framework actually works, so that they can be designed for rather than hoped for.

Where the 6Cs Come From

Precision about provenance matters in a piece that aspires to rigour, and the honest account is more interesting than a manufactured pedigree. The 6Cs of a project management framework are a practitioner heuristic rather than an academic theory, and they did not emerge from a single research programme. The earliest clearly datable and attributable articulation appears in a short article by Paul Naybour, a United Kingdom project management consultant and trainer accredited by the Association for Project Management, published on 12 October 2013 under the title Six reasons to use a project management framework [10]. Naybour set out six reasons, which he labelled the 6Cs, for adopting a framework: consistency, clarity, collaboration, continuity, capability and communication. From that origin the mnemonic spread quickly through training providers, professional blogs and practitioner courses, which is why it now appears in many slightly varying forms across the field while rarely carrying a citation back to its source.

This practitioner lineage should not be confused with the academic 6C Model published by Silje Kamille Friis and Anne Katrine Gelting in 2016, a model concerned with knowledge production in co-creative design. That model moves a design process through the stages of collect, comprehend, conceptualise and create, bound together by collaboration and communication, and it was developed in the design-thinking tradition at the Technical University of Denmark. It shares its initials with the project management 6Cs and very little else. Conflating the two attributes a project delivery mnemonic to a design research model that was never about project delivery, and the distinction is worth stating plainly.

The deeper point is that although the mnemonic itself is recent and informal, the ideas underneath it are not. Each C corresponds to a mature stream of scholarship: clarity to the literature on governance and decision rights, consistency to the study of methodology and standardisation, communication to research on information flow and sponsorship, collaboration to decades of work on team development, competence to the science of capability and individual performance, and continuous improvement to the foundational theory of organisational learning. The 6Cs, in other words, are a memorable practitioner shorthand for conclusions that serious research reached independently and earlier. Kairos retains the mnemonic for that communicative power, while deliberately substituting competence for capability and continuous improvement for continuity, two changes that shift the emphasis from static attributes toward the active behaviours that determine whether a framework lives or dies. The version used here is therefore Kairos’s own articulation, grounded in the practitioner origin but sharpened against the research.

Clarity

Clarity is the discipline of removing ambiguity before it becomes expensive. A framework earns its first dividend by insisting that objectives, scope, roles, decision rights and success criteria are defined and agreed at the outset rather than discovered in dispute later. Ambiguity in any of these is among the most reliable predictors of failure, because it allows two people to believe they agree while building toward different ends. Clarity is established through defined governance with explicit escalation paths, standardised charters that fix scope and constraints in writing, and transparent decision criteria tied to organisational strategy. It is sustained by the willingness to say plainly what is in scope and, harder, what is not.

Clarity also has an ethical dimension that the overrun research makes unavoidable. When Flyvbjerg attributes much of the megaproject problem to optimism bias and to estimates shaped to win approval, he is describing a failure of clarity at the most consequential moment in a project’s life. A framework that demands honest, independently challenged baselines is enforcing clarity against the natural human pull toward flattering forecasts.

Consistency

Consistency converts project management from a personal art into a repeatable organisational discipline. When lifecycle phases, documentation standards and performance metrics are uniform across teams and geographies, the organisation gains something subtle and valuable: comparability. A risk register means the same thing in two business units. A progress report can be read at a glance because its shape is familiar. Lessons from one project transfer to the next because both were run in a recognisable way. Consistency is what allows a portfolio to be governed as a portfolio rather than as a collection of unrelated adventures.

The caution worth stating is that consistency is a means, not an end. The research on methodology completeness is explicit that uniformity must be fitted to context, and that a method which is comprehensive in one setting can be unnecessarily heavy in another [7]. Mature frameworks therefore standardise the spine, including governance, gates and core reporting, while allowing the execution method to vary with the nature of the work. The art lies in knowing which elements are load-bearing and must not flex, and which are local and should.

Communication

Communication is the circulatory system of a project, and its failure is rarely dramatic. It shows up as a decision made on stale information, a risk that someone saw coming but no one escalated, a stakeholder surprised by a result they should have helped shape. A framework embeds communication as structure rather than goodwill: defined reporting cadences calibrated to each audience, a single source of truth for project documentation, and feedback loops that surface problems while they are still small and cheap. The Project Management Institute’s own analysis identifies an actively engaged executive sponsor as the single strongest driver of projects meeting their goals [8], and an engaged sponsor is, in practical terms, a communication achievement before it is anything else.

Good communication is also honest communication. A reporting culture that punishes bad news teaches teams to hide it, and hidden problems compound. Part of designing for communication is therefore designing the psychological conditions under which a project manager can report a slipping schedule early, without flinching, because early disclosure is rewarded rather than penalised.

Collaboration

Collaboration turns a set of individual contributions into a collective result. Modern projects are cross-functional by nature, drawing on engineering, commercial, legal, operational and digital expertise that no single person commands. A framework supports collaboration through integrated teams with clearly mapped interdependencies, shared platforms for real-time coordination, and explicit mechanisms for resolving the conflicts that any serious collaboration produces. The classic account of how groups become effective, Bruce Tuckman’s sequence of forming, storming, norming and performing, remains a useful reminder that conflict is a stage to be worked through rather than a sign of dysfunction [11].

Collaboration is where the choice of execution method earns its evidence. In a global study of agile adoption, Pedro Serrador and Jeffrey Pinto found a positive relationship between agile use and reported project success, with the strongest effect on stakeholder satisfaction, the most relational of all success measures [12]. Their data also showed that hybrid combinations of agile and traditional methods were the norm in practice rather than the exception, which is itself an argument for a framework flexible enough to host both. Kairos supports this collaborative core through its digital project management solutions, which give distributed teams a shared operating surface rather than a scatter of disconnected tools.

Competence

Competence is the pillar that the others depend upon and the one most often assumed rather than built. A framework is executed by people, and where the people lack the skills, judgement and authority the framework presumes, it fails quietly regardless of how well it is designed. Building competence means role-specific development for project managers, sponsors and team members, a competency baseline that defines what good looks like at each level, and mentoring that accelerates the slow transfer of judgement that no course can fully teach. The International Project Management Association’s competence baseline, organised around the perspective, people and practice of project work, offers one well-developed map of what such capability comprises [13].

The strategic importance of competence is no longer a matter of assertion. The Project Management Institute’s recent research finds that practitioners with strong business acumen and so-called power skills, including communication and stakeholder leadership, achieve markedly better outcomes and materially lower failure rates than peers who rely on technical skill alone [14]. Competence, in other words, is not a soft adjunct to the framework. It is a primary driver of the results the framework is built to produce, and it deserves investment on those terms.

Continuous Improvement

A framework that cannot learn will slowly diverge from the reality it is meant to govern. Continuous improvement is the pillar that keeps the framework alive: structured post-project reviews that capture what worked and what did not, knowledge systems that make those insights findable rather than filed and forgotten, and periodic audits that test the framework against current conditions. The intellectual roots are deep. Chris Argyris and Donald Schön distinguished single-loop learning, which corrects errors within existing assumptions, from double-loop learning, which questions the assumptions themselves [15]; a mature framework is built for the second kind. W. Edwards Deming’s plan-do-check-act cycle gave the same instinct an operational rhythm that remains the backbone of improvement practice [16].

The hardest part of continuous improvement is not capturing lessons but converting them into knowledge the organisation can reuse. Ikujiro Nonaka’s account of organisational knowledge creation describes how tacit insight, the kind that lives in an experienced project manager’s instinct, becomes explicit and shareable only through deliberate social processes [17]. A framework that holds a lessons-learned meeting and files the minutes has captured information. A framework that turns those lessons into revised templates, updated training and changed decision criteria has created knowledge. The difference is the entire value of the pillar.

The Working Components of a Framework

With the principles established, the structural components of a framework can be described as the means by which those principles are made operational. A sound framework integrates several components that reinforce one another, and the integration matters more than the inventory. A brilliant risk process attached to weak governance achieves little; the components earn their value collectively. Each is treated below in turn.

Governance structure

Governance defines the decision rights, accountability and escalation paths that tell everyone who may decide what, and under which conditions a matter rises to a higher authority. In practice this means a named sponsor who owns the business case and the benefits, a steering arrangement for decisions that exceed the project manager’s mandate, and explicit thresholds, for changes in cost, scope or schedule, at which authority passes upward. It also means keeping the governance of a project distinct from the day-to-day management of it, so that the people delivering the work are not the only people judging it. The research places governance at the centre of performance, flowing from the board through the management tier down to the individual project [6], and as argued earlier it is the component that makes every other one credible, since a control that no one is accountable for is decoration. Governance is therefore designed first, before a single template is drafted.

Lifecycle model

A defined lifecycle delineates the phases a project moves through, from initiation and feasibility, through concept selection and engineering, into execution and closure, each with explicit entry and exit criteria. The gates between phases are where a framework exercises its most valuable and most underused power, the power to confirm, reshape or stop a project before more is committed to it, which is precisely the front-end discipline whose absence drives the largest overruns [2]. A mature framework does not impose one lifecycle on every project. It offers a considered choice between a linear sequence suited to well-understood work, an iterative or incremental cadence suited to emergent work, and the hybrid combinations that now describe most real delivery, a taxonomy the APM Body of Knowledge sets out while deliberately avoiding the reductive contest of waterfall against agile [18]. The lifecycle is the framework’s clock, and matching it to the nature of the work is one of the highest-value design decisions an organisation makes.

Methodology and standards

The framework codifies which methods, standards and tools apply to which classes of work, creating a common language without forcing every project into an identical mould. This is the layer that selects, for a given project, between a plan-driven, an adaptive or a hybrid approach, and that defines the templates, estimating conventions and quality standards teams will share. The purpose of standardisation here is not uniformity for its own sake but comparability and transferability: a schedule built the same way in two divisions can be read, audited and learned from across both. The standards a framework adopts are rarely invented from scratch; they are tailored from established professional sources, since both leading bodies of knowledge are explicit that their content must be fitted to the project rather than applied by rote [4], [5]. Templates, in this view, are enablers that remove repetitive decisions, not ends that the project exists to feed.

Performance measurement

Metrics translate progress into evidence, tracking schedule, cost, quality and stakeholder satisfaction so that decisions rest on data rather than impression. Good measurement distinguishes lagging indicators, which report what has already happened, from leading indicators, which warn of what is about to, and it compares performance against an agreed baseline so that variance is visible early enough to act on. The discipline of measuring and controlling delivery against that baseline is the heart of project control, which Kairos treats as a distinct capability through its project control solutions. Measurement is also where benefits realisation lives, the practice of tracking value beyond closure that the Project Management Institute identifies as a hallmark of high performers [3]; a project that delivered on time but produced no benefit has not succeeded in any sense that matters. Measurement is the component that turns a framework from a set of intentions into a system that can show, in numbers, whether it is working.

Risk management

A systematic approach to identifying, assessing, responding to and monitoring risk keeps potential disruptions from becoming actual ones, and a mature framework treats opportunity as seriously as threat rather than reducing risk to a register of things that might go wrong. Risk management is most valuable at the front end, where Flyvbjerg locates the origin of most overruns and where honest assessment is the natural antidote to the optimism bias that flatters early estimates [2]. A framework gives risk teeth by attaching it to governance and to money: a defined risk appetite that states how much uncertainty the organisation will tolerate, contingency held against identified risks, and management reserves held against the unknown. Risk that is identified but not owned, funded or reviewed is merely documented, and documentation has never stopped a project from failing.

Resource management

Protocols for allocating people, money and technology ensure that scarce capability is directed to the work that matters most, and that the same expert is not silently committed to three critical paths at once. Effective resource management works at two levels: within the project, where the right skills must be available at the right time, and across the portfolio, where finite specialist capacity must be balanced against competing demands. The discipline that matters is matching capacity honestly to demand, since a plan that assumes people are available when they are not is a plan that will slip regardless of how well everything else is managed. Resource management is what turns a portfolio of individually sensible projects into a deliverable whole, and its absence is why organisations so often start far more than they can finish.

Knowledge management

A system for capturing and sharing lessons and good practice ensures each project adds to the organisation’s collective intelligence rather than relearning what a previous team already knew. This is the structural home of the continuous improvement pillar, and the place where the distinction between captured information and created knowledge is won or lost. Holding a lessons-learned meeting and filing the minutes captures information; turning those lessons into revised templates, updated training and changed decision criteria creates knowledge, and only the second changes what the next project does [17]. Effective knowledge management combines accessible repositories with the human channels, communities of practice, mentoring and shared delivery, through which the tacit judgement of experienced practitioners actually transfers. The APM Body of Knowledge treats knowledge management as a core function of preparing for and learning across change [18], a recognition that an organisation which cannot remember is condemned to keep paying for the same mistakes.

The 6Cs and the Professional Standards

A fair and obvious question is how the 6Cs relate to the established professional standards, principally the APM Body of Knowledge and the PMI PMBOK Guide, both of which reached substantial new editions in 2025 [18], [4]. The honest answer begins with altitude. The 6Cs are a compact behavioural heuristic, six conditions an organisation can hold in its head, while the standards are comprehensive professional references that run to hundreds of pages and define the full breadth of the discipline. They are not competitors, and reading them as rivals misunderstands both. The 6Cs sit on top of a body of knowledge; they do not replace one. What follows sets out what each standard now is, where the 6Cs align with it, and where they diverge and why.

What the two standards now are

The APM Body of Knowledge, in its eighth edition, describes itself as a statement of the concepts, functions and activities that make up professional project management, written for project-based working across projects, programmes and portfolios [18]. Its guiding philosophy is evolution rather than revolution: it builds on the 2019 seventh edition and keeps that structure largely intact, organised around the arc of delivering change through six chapters, from implementing change and setting up for success, through preparing for change and people and behaviours, to planning and managing deployment. The eighth edition adds two chapters that signal where the profession is heading, one on the strategic context in which projects are commissioned and, for the first time, one on the impact of data and artificial intelligence on delivery. It recognises a spectrum of life cycles, from linear to iterative to hybrid, and pointedly declines to stage the tired contest of waterfall against agile, framing the choice instead as a judgement leaders make.

The PMBOK Guide, in its eighth edition and billed by its publisher as its most evidence-based revision to date, is built on two halves [4]. Its Standard for Project Management distils practice into six principles, a deliberate, community-driven simplification of the twelve principles of the previous edition: adopt a holistic view, focus on value, embed quality into processes and deliverables, be an accountable leader, integrate sustainability across all project areas, and build an empowered culture. Its Guide then describes seven performance domains, namely governance, scope, schedule, finance, stakeholders, resources and risk, framed around the outcomes a project must achieve rather than the processes it must run, and it reintroduces the familiar five focus areas of initiating, planning, executing, monitoring and controlling, and closing. The direction of travel is unmistakable: away from prescriptive process and toward principles, value and judgement.

Where the 6Cs align with the standards

The first thing to notice is convergence. Both standards have moved decisively toward the territory the 6Cs occupy. PMBOK’s shift from a process catalogue to a short set of principles, and the APM Body of Knowledge’s dedicated chapter on people and behaviours, both elevate human judgement and behaviour above procedure, which is the central move the 6Cs make. Pillar by pillar, the alignment is close. Clarity maps onto PMBOK’s governance and scope domains and its call to be an accountable leader, and onto APM’s treatment of governance and business cases. Consistency is the standardised method, life cycle and domain structure that both standards exist to codify. Communication corresponds to PMBOK’s stakeholders domain and to APM’s chapter on stakeholder engagement. Collaboration answers to PMBOK’s principle of building an empowered culture and its resources domain, and to APM’s people and behaviours. Competence is explicit in both, with APM aligning its Body of Knowledge directly to its Competence Framework [18] and PMBOK foregrounding team competence and a project management mindset. Continuous improvement lives in APM’s treatment of assurance, learning and maturity and in PMBOK’s principle of embedding quality, as well as in the simple fact that both standards are themselves evidence-based and periodically revised. Every one of the 6Cs, in short, has a clear home in each standard. The model is broadly compliant with both.

Where the 6Cs differ, and why

The differences are as instructive as the alignments, and there are three worth naming. The first is one of scope and altitude. The 6Cs deliberately omit the technical disciplines the standards cover in depth, scope definition, scheduling, finance, procurement, risk analysis and quality as crafts, because they are not a body of knowledge and were never meant to be. They presuppose that knowledge and direct attention to the behavioural conditions under which it is applied well. The reason is purpose: a professional standard must serve certification and the entire profession, whereas the 6Cs serve a leader deciding whether and how to invest in a framework at all, a decision neither standard is primarily written to support. Read this way, the omission is not a weakness but a division of labour.

The second difference is a genuine tension worth confronting rather than smoothing over. Both 2025 standards lean hard into tailoring and adaptability; PMBOK has no standalone principle of consistency and explicitly elevates tailoring, and the APM Body of Knowledge declines to prescribe a single method. The 6Cs, by contrast, hold consistency as a named virtue. The resolution, argued throughout this article, is consistency of the spine and tailoring of execution, and read that way the model and the standards agree. The 6Cs keep consistency visible precisely because the standards’ proper emphasis on tailoring can be misread, by organisations looking for permission, as licence to standardise nothing. The pillar is a deliberate counterweight, not a contradiction.

The third difference cuts the other way and is a candidate for the model’s evolution rather than a point of pride. Both standards now treat sustainability as first-class, a named PMBOK principle and a dedicated APM chapter, while the 6Cs do not name it at all. An honest comparison has to record that as a gap rather than dress it as a virtue. As client expectations on environmental and social outcomes rise, and as both standards make sustainability central, the case for a seventh C, or for folding sustainability explicitly into clarity of purpose and continuous improvement, grows stronger. Kairos weighs that openly rather than papering over it, which is the only intellectually honest position to take when the formal standards have moved ahead of a practitioner shorthand on a point that increasingly matters.

The practical conclusion is that the 6Cs and the standards are complementary, operating at different altitudes on the same problem. Kairos uses the standards as the authoritative source of the what and the how, the deep content of governance, scheduling, finance, risk and the rest, and uses the 6Cs as the behavioural compass that decides whether that content is being applied in a way that will actually hold. A framework grounded in the APM and PMI bodies of knowledge but animated by the 6Cs captures the strength of each [18], [4]: the rigour and completeness of the profession’s accumulated knowledge, and the behavioural focus that determines whether any of it survives a real project under real pressure. The standards tell an organisation what excellent project management contains. The 6Cs remind it why that excellence so often fails to appear, and what to attend to so that it does.

What a Framework Delivers

The benefits of a well-built framework follow directly from its components, and they compound. The first is strategic alignment. By linking every initiative to organisational objectives, a framework ensures that effort flows to the work that advances the strategy, and that projects which no longer serve it can be stopped without embarrassment. Misalignment is expensive precisely because it is invisible until late; a framework makes it visible early.

The second benefit is predictability. Standardised processes and disciplined estimating reduce the variance in outcomes, which is what allows leaders to forecast with confidence and to make commitments they can keep. Predictability is not glamorous, but in a project economy it is the foundation of trust with customers, regulators and investors.

Efficiency follows. When duplication is removed and teams are not reinventing process for every initiative, delivery accelerates and cost falls. Quality assurance, embedded through the lifecycle rather than inspected in at the end, raises the floor on what the organisation produces, while transparency and accountability strengthen the confidence of everyone with a stake in the outcome. Finally, a sound framework is scalable: success in one project can be replicated across portfolios and geographies because the means of that success are documented and teachable rather than locked in one person’s head.

It is worth restating the magnitude at stake. The difference between the organisations that capture these benefits and those that do not is the difference between succeeding on nine projects in ten and succeeding on barely three, and between wasting a few cents of every invested dollar and wasting many times more [3], [8]. A framework is one of the few interventions that moves an organisation along that entire spectrum.

The Challenges, Honestly Stated

A framework is not self-installing, and the obstacles to making one work are mostly human rather than technical. Naming them plainly is the first step to overcoming them.

Cultural resistance is the most common. Teams accustomed to informal or improvised working often experience standardisation as a loss of autonomy and a vote of no confidence. The resistance is not irrational, and it cannot be overridden by mandate alone. It is answered by involving practitioners in the design, by demonstrating that the framework removes friction rather than adding it, and by visible early wins that change the story from imposition to advantage.

Bureaucratic overreach is the opposite failure, and frameworks built by enthusiasts are especially prone to it. A framework that demands more documentation than a project can justify becomes a tax that teams pay grudgingly and bypass when they can. The corrective is proportionality: heavy governance for high-risk, high-value work and a lighter touch for the routine, with the framework itself specifying which is which.

Resource constraints, change fatigue and integration with existing systems round out the list. Building and maintaining a framework takes budget, skilled people and time, and organisations that have already endured several waves of process change will be weary of another. Integrating a new framework with legacy systems, contracts and habits is as much a political task as a technical one. These are real, and they are why a framework rollout must itself be run as a serious project with proper change management.

On that point, the change-management literature is directly applicable. John Kotter’s account of why transformations fail, and his emphasis on a genuine sense of urgency, a guiding coalition with real authority, and short-term wins that build momentum, maps almost exactly onto the task of embedding a framework [19]. A framework is, after all, a behavioural change dressed as a process initiative, and it succeeds or fails on the same terms as any other change. Leadership sponsorship is not a nicety here. It is the variable the evidence identifies as decisive [8].

Building a Resilient Framework: A Structured Process

Designing a framework is itself a strategic project, and it deserves the same rigour, stakeholder engagement and phased discipline it will later ask of the projects it governs. It needs a sponsor with real authority, a business case that states the value it is expected to return, defined stage gates, and a plan that can be tracked. An organisation that builds its framework casually, in spare moments and by committee, produces a casual framework. The process set out below describes six movements, followed by two disciplines that keep the framework alive once it exists. Each movement draws on the 6Cs in a way that becomes its own quiet demonstration of the principles at work.

A word on how Kairos approaches this matters here, because the method shapes the outcome. Kairos does not write a framework in isolation and present it as a finished document for an organisation to adopt. It embeds within the client’s teams and co-creates the framework alongside the people who will run it, an approach set out in the Kairos core values. The reasoning is practical rather than philosophical: a framework handed down from outside is complied with at best and resisted at worst, whereas a framework built with the delivery teams is owned by them, and ownership is the single condition under which a framework survives the first difficult project. Every Kairos practitioner brings more than twenty years of frontline delivery experience to that collaboration, which means the framework is shaped by people who have lived with the consequences of weak ones.

Stage one: Assess the current state honestly

The work begins with diagnosis, and the quality of everything that follows depends on the honesty of this stage. A credible assessment examines what the organisation actually does rather than what its process documents claim it does, and the gap between the two is usually the most useful finding. The activities are concrete: a review of recent project outcomes against their original baselines, structured interviews across the delivery community from sponsors to schedulers, an audit of existing governance and tooling, and a maturity assessment mapped against an external reference such as the maturity dimensions set out in the APM Body of Knowledge [18]. The output is a factual baseline, a clear statement of strengths to preserve and weaknesses to address, expressed in evidence rather than opinion.

This stage depends on clarity and on competence in those conducting it, because a flattering self-diagnosis guarantees a framework that solves the wrong problems. It is also where the most common failure of framework projects is avoided. Many organisations skip straight to designing templates, encoding the very habits that were producing poor outcomes. Kairos applies its approach by working inside the delivery teams during this stage rather than interviewing them from across a table, which surfaces the informal practices and quiet workarounds that never appear in a process manual but explain most of what actually happens on a project. Reviewing the Kairos project management case studies shows how this evidence-led starting point changes the questions a framework is built to answer.

Stage two: Define objectives, principles and the measures of success

With the baseline established, the organisation states precisely what the framework must achieve. Vague aims such as better project management produce vague frameworks; useful objectives are specific and measurable, for instance improving delivery predictability so that schedule and cost variance fall within a defined band, raising stakeholder satisfaction, or tightening the link between projects and strategic priorities. Alongside the objectives, this stage sets the design principles that will resolve the hard trade-offs later: how much standardisation the organisation wants against how much local autonomy, how heavy governance should be for different classes of project, and how much the framework should lean toward plan-driven or adaptive delivery.

Crucially, the measures of success are agreed now, before any design begins, so that the framework can be judged on evidence rather than on impression once it is live. These measures fall into two groups: adoption measures, which track whether teams are actually using the framework, and outcome measures, which track whether delivery is improving as a result. Clarity and consistency dominate this stage. Kairos applies its approach by tying these objectives directly to the organisation’s strategy and to the realities uncovered in the assessment, so that the framework is designed to close the specific gaps that are costing the organisation, not to satisfy an abstract idea of best practice imported from elsewhere.

Stage three: Design the framework as a system

Design is where the components described earlier are assembled into a working whole, and it proceeds in a deliberate order. Governance comes first, because it is the load-bearing element: the design fixes decision rights, accountability, escalation paths and the thresholds at which a decision rises to a higher authority [6]. Next comes the lifecycle and its gates, the defined phases through which every project passes and the entry and exit criteria at each gate where the organisation can confirm, reshape or stop a project before more is spent on it. Only then are methodology and tooling chosen, so that the way work is executed is fitted to the governance around it rather than bolted on afterwards.

The decisive design judgement, made here, is which elements are load-bearing and fixed across the whole organisation, and which are local and tailorable to the project in hand. Get this wrong toward rigidity and the framework will be resented and bypassed; get it wrong toward looseness and it will not bind. A resilient design fixes the spine, including governance, gates and core reporting, while allowing execution method to vary, which is what the research on methodology and context requires [7]. This is also the stage at which the framework’s digital backbone is chosen, the shared platforms and dashboards that give distributed teams one operating surface rather than a scatter of disconnected tools. Kairos supports this through its digital project management solutions, and embeds the measurement and control discipline that turns plans into evidence through its project control solutions. For contract-intensive sectors, the design extends into the management of agreements as living instruments, addressed through Kairos contract management solutions, so that commercial and delivery governance reinforce rather than contradict each other.

Kairos applies its co-creative approach most visibly at this stage. Rather than designing the system and reviewing it with the client, Kairos designs it with the client, in working sessions that include the people who will operate each part. The result is a framework calibrated to the organisation’s real constraints, its sectors, its contract types and its delivery culture, rather than a generic model that looks impressive and fits poorly.

Stage four: Build the capability to run it

No framework outperforms the people executing it, so capability is built deliberately rather than assumed, and this is the stage where framework initiatives most often underinvest. Building capability means defining a competency baseline that states what good looks like at each role and level [13], developing role-based training for project managers, sponsors, schedulers and team members, and establishing mentoring and coaching so that the slow transfer of judgement, which no course fully teaches, actually happens. It also means creating communities of practice where practitioners share what they are learning, which turns capability from a one-time training event into a continuing organisational habit.

The evidence that this investment pays is now strong rather than assumed. The Project Management Institute finds that practitioners with developed business acumen and power skills, including communication and stakeholder leadership, achieve markedly better outcomes and lower failure rates than those who rely on technical skill alone [14]. Kairos treats capability as the heart of the engagement rather than a closing module. Because its consultants work inside the teams, capability is transferred through shared delivery rather than through classroom abstraction, and the explicit aim is self-sustainment: Kairos builds the organisation’s ability to run and evolve the framework without ongoing external dependence, which is the practical meaning of leaving a client stronger than it was found.

Stage five: Pilot, learn and refine

Before any organisation-wide rollout, the framework is tested on a controlled set of real projects chosen to represent the range of work it must serve, including at least one demanding case rather than only easy wins. This stage is continuous improvement made concrete and follows the rhythm of plan, do, check and act [16]: the framework is applied, its performance against the agreed measures is observed, the gaps and points of friction are identified, and the design is revised in response to real use rather than to its authors’ intentions. A pilot that surfaces problems is a success, not a setback, because it converts expensive future failures into cheap present corrections.

The discipline that matters here is the willingness to change the design in response to what the pilot reveals, rather than defending it. Lessons are documented and fed back with the same rigour the framework will later require of every project, which also gives the delivery teams an early, visible demonstration that the framework listens. Kairos runs pilots alongside the teams, captures what works and what does not as the work happens rather than reconstructing it afterwards, and uses the pilot deliberately to build the internal advocates whose support will carry the wider rollout.

Stage six: Roll out and institutionalise

The final movement embeds the framework into the organisation so that it becomes how work is done rather than a parallel system to be tolerated. This is a change-management task before it is a process task, and it succeeds or fails on the same terms as any other change. John Kotter’s analysis of why transformations fail points directly at the levers that matter: a genuine sense of urgency, a guiding coalition with real authority, and a sequence of short-term wins that build momentum [19]. The framework must be written into the machinery of the organisation, including its performance management, its planning and budgeting cycles, and the criteria by which projects are approved and reviewed, because a framework that lives only in a manual will be quietly abandoned under the first deadline.

Visible and sustained sponsorship is decisive here, since an engaged executive sponsor is the variable the evidence identifies as the strongest single driver of projects meeting their goals [8]. At this point all six pillars converge: clarity of purpose, consistency of execution, communication in reporting, collaboration in delivery, competence in application and continuous improvement in evolution. Institutionalisation is the difference between a framework that is launched and a framework that lasts; the first is an event, the second is a change in the organisation’s character. Kairos works toward what it describes as self-sustaining momentum, the point at which the framework is carried forward by the organisation’s own people because they own it and can see it working, rather than by the consultants who helped build it.

The two ongoing disciplines: govern the framework, and measure it

A framework is not finished when it is rolled out, and two disciplines run continuously beneath the six stages. The first is governance of the framework itself. Like any asset, a framework needs an owner, a custodian or a project management office responsible for its upkeep [20], a version-controlled record of what it currently requires, and a periodic audit that tests it against changing conditions. Without an owner, a framework drifts: teams quietly add exceptions, the documented process and the real process diverge again, and within a few years the organisation is back where it started. Mature frameworks are built to question their own assumptions, not merely to correct errors within them, which is the distinction between single-loop and double-loop learning that Argyris and Schön drew [15], and they convert the lessons of each project into revised templates, updated training and changed decision criteria rather than filing them as information no one reuses [17].

The second discipline is measurement, which closes the loop opened in stage two. The framework should be judged on the adoption and outcome measures agreed at the outset: are teams actually using it, and is delivery improving as a result, in predictability, in benefit realisation, and in stakeholder satisfaction. Tracking benefits beyond project closure, a practice the Project Management Institute identifies as a hallmark of high performers [3], is part of this discipline, as is a periodic re-assessment of maturity to confirm the organisation is moving in the intended direction. Measurement is where Kairos applies its data-driven conviction in the most direct way, instrumenting the framework so that its value can be demonstrated in evidence rather than asserted in narrative, and so that the framework continues to adapt on the basis of what the data shows rather than on instinct. A framework that is governed and measured in this way stops being a document and becomes what it was always meant to be, a living system that improves the organisation’s odds on every project it touches.

Resilience Means Adaptability, Not Rigidity

There is a persistent misreading of frameworks worth confronting directly: the belief that a framework’s purpose is to make everything uniform and fixed. A resilient framework does the opposite of imposing a single rigid method. It supplies a stable spine of governance, gates and core measurement while deliberately permitting the execution approach to vary with the work. This is what the research demands, given that methodology effectiveness is moderated by context, and it is what practice confirms, given that hybrid approaches dominate real delivery. It is also, notably, the position both professional standards now take.

The evidence on adaptive methods is instructive precisely because it is not uncritical. Serrador and Pinto found agile use positively associated with success and especially with stakeholder satisfaction, yet they also found that the majority of real projects blend agile and traditional methods rather than choosing one in its pure form [12]. The lesson for framework design is not to declare allegiance to a method but to build a container capable of hosting the right method for each project, and of changing that choice as a project’s character changes. Bennett and Lemoine’s core argument applies here too: the right response depends on whether you face volatility, uncertainty, complexity or ambiguity, and a framework that offers only one response to all four is mismatched to the world it operates in [1].

This is the deeper meaning of a data-driven framework, and the conviction at the centre of the Kairos approach. As measurement matures and as analytics and intelligent tooling make the state of a project more legible in real time, the framework gains the ability to adapt on evidence rather than on instinct. It is no accident that the APM Body of Knowledge added a chapter on data and artificial intelligence in its latest edition [18]; the profession is recognising what Kairos has built its practice around. The point is not technology for its own sake but a tighter loop between what a project is actually doing and the decisions made about it. Organisations curious about how this plays out in practice can review the Kairos project management case studies, which trace these principles through delivered work across sectors.

Conclusion: A Framework Is a Strategic Asset

The argument of this article can be compressed into a single claim: the capacity to deliver projects reliably is now a primary determinant of organisational success, and a project management framework is the system that builds that capacity. The evidence is not ambiguous. Projects fail at rates that should alarm any leader, the failures are structural rather than accidental, and the organisations that escape the pattern do so through capabilities they deliberately construct rather than through fortune.

A framework delivers that escape only when it is understood correctly, as a living operating system rather than a binder of templates, and only when its structure is animated by the behavioural conditions the 6Cs describe. Clarity removes the ambiguity that breeds failure. Consistency makes success repeatable and comparable. Communication keeps decisions grounded in current reality. Collaboration turns individual effort into collective result. Competence supplies the people without whom no design succeeds. Continuous improvement keeps the whole system honest and current. Set against the professional standards, the 6Cs are not a rival body of knowledge but the behavioural compass that decides whether such a body of knowledge is applied in a way that holds. Structure without these behaviours is an artefact; behaviours without structure are improvisation. The value lies in their union.

To realise that value, organisations should approach both design and adoption in phases and with participation, champion the framework visibly from the top, link it explicitly to strategy and performance expectations, and communicate early wins to build the momentum that overcomes resistance. Investment in capability is not optional, and the establishment of genuine feedback mechanisms is what keeps the framework relevant as conditions change. Treated as a compliance exercise, a framework becomes the bureaucracy its critics fear. Treated as a strategic asset and nurtured accordingly, it becomes a durable source of advantage, an organisation that can be relied upon to move well at the moment that matters.

References

[1]  Bennett, N., & Lemoine, G. J. (2014). What a difference a word makes: Understanding threats to performance in a VUCA world. Business Horizons, 57(3), 311–317. https://doi.org/10.1016/j.bushor.2014.01.001

[2]  Flyvbjerg, B. (2014). What you should know about megaprojects and why: An overview. Project Management Journal, 45(2), 6–19. https://doi.org/10.1002/pmj.21409

[3]  Project Management Institute. (2013). Pulse of the Profession: The High Cost of Low Performance. PMI. https://www.pmi.org/learning/thought-leadership/pulse/the-high-cost-of-low-performance-2013

[4]  Project Management Institute. (2025). A Guide to the Project Management Body of Knowledge (PMBOK Guide) and The Standard for Project Management (8th ed., ANSI/PMI 99-001-2025). PMI.

[5]  AXELOS. (2017). Managing Successful Projects with PRINCE2 (6th ed.). The Stationery Office.

[6]  Joslin, R., & Müller, R. (2016). The relationship between project governance and project success. International Journal of Project Management, 34(4), 613–626. https://doi.org/10.1016/j.ijproman.2016.01.008

[7]  Joslin, R., & Müller, R. (2015). Relationships between a project management methodology and project success in different project governance contexts. International Journal of Project Management, 33(6), 1377–1392. https://doi.org/10.1016/j.ijproman.2015.03.005

[8]  Project Management Institute. (2018). Pulse of the Profession: Success in Disruptive Times. PMI. https://www.pmi.org/learning/thought-leadership/pulse/pulse-of-the-profession-2018

[9]  Project Management Institute. (2021). Pulse of the Profession: Beyond Agility. PMI. https://www.pmi.org/learning/thought-leadership/pulse/pulse-of-the-profession-2021

[10]  Naybour, P. (2013, October 12). Six reasons to use a project management framework. Parallel Project Training. https://www.parallelprojecttraining.com/blog/six-reasons-use-project-management-framework/

[11]  Tuckman, B. W. (1965). Developmental sequence in small groups. Psychological Bulletin, 63(6), 384–399. https://doi.org/10.1037/h0022100

[12]  Serrador, P., & Pinto, J. K. (2015). Does Agile work? A quantitative analysis of agile project success. International Journal of Project Management, 33(5), 1040–1051. https://doi.org/10.1016/j.ijproman.2015.01.006

[13]  International Project Management Association. (2015). Individual Competence Baseline for Project, Programme and Portfolio Management (ICB4). IPMA.

[14]  Project Management Institute. (2023). Pulse of the Profession: Power Skills, Redefining Project Success. PMI. https://www.pmi.org/learning/thought-leadership/power-skills-redefining-project-success

[15]  Argyris, C., & Schön, D. A. (1978). Organizational Learning: A Theory of Action Perspective. Addison-Wesley.

[16]  Deming, W. E. (1986). Out of the Crisis. MIT Center for Advanced Engineering Study.

[17]  Nonaka, I. (1994). A dynamic theory of organizational knowledge creation. Organization Science, 5(1), 14–37. https://doi.org/10.1287/orsc.5.1.14

[18]  Association for Project Management. (2025). APM Body of Knowledge (8th ed.). APM. ISBN 978-1-913305-39-0.

[19]  Kotter, J. P. (1996). Leading Change. Harvard Business School Press.

[20]  Hobbs, B., & Aubry, M. (2007). A multi-phase research program investigating project management offices (PMOs): The results of phase 1. Project Management Journal, 38(1), 74–86. https://doi.org/10.1177/875697280703800108