{"version":"1.0","type":"agent_native_article","locale":"en","slug":"why-65-percent-companies-rewrite-business-model-every-two-years-fail-execution-mr52tqb5","title":"Why 65% of Companies Rewrite Their Model Every Two Years and Still Fail to Execute It","primary_category":"leadership","author":{"name":"Ignacio Silva","slug":"ignacio-silva"},"published_at":"2026-07-03T14:02:52.345Z","total_votes":90,"comment_count":0,"has_map":true,"urls":{"human":"https://sustainabl.net/en/articulo/why-65-percent-companies-rewrite-business-model-every-two-years-fail-execution-mr52tqb5","agent":"https://sustainabl.net/agent-native/en/articulo/why-65-percent-companies-rewrite-business-model-every-two-years-fail-execution-mr52tqb5"},"summary":{"one_line":"PMI research across 700+ executives reveals that the core failure of organizational transformation is not lack of ambition but absence of operational architecture to execute what is declared.","core_question":"Why do organizations that continuously redesign their strategy still fail to execute transformation, and what structural conditions would need to change for that to stop?","main_thesis":"The planning-execution gap documented by PMI is not a speed, culture, or ambition problem — it is an organizational design problem. Most companies have built change strategies but not change capabilities, and the difference lies in governance structures, decision-making architecture, and metric systems that remain hierarchical and centralized even as transformation language becomes universal."},"content_markdown":"## Why 65% of Companies Rewrite Their Model Every Two Years and Still Fail to Execute It\n\nThere is something revealing about the fact that a survey of more than 700 senior executives across 12 countries produced, as its central finding, a gap that any chief operating officer would recognize instantly: organizations know they must change, they approve the change, they frame it within a strategy, and then they go no further. The Project Management Institute has just published the results of that research, alongside a Manifesto for Business Agility developed in collaboration with Agile Alliance, and the numbers that emerge are not those of an industry in the process of maturing. They are those of an industry with a structural design problem that has gone without precise diagnosis for years.\n\nThe most uncomfortable finding is not that **93% of senior executives acknowledge that operating models must be reviewed at least every five years**. That percentage merely indicates that there is intellectual consensus around the need for change, which costs very little. The figure that matters is this one: **65% of organizations are already rewriting their business approaches every two years or less**, and yet **35% of CEOs identify as their primary barrier a disconnect between planning and execution**. Two-year reinvention cycles, with 35% of the most senior leaders admitting they never manage to implement what they plan. That is not a speed problem. It is an architecture problem.\n\n## The Map Nobody Is Following\n\nThere is a distinction that the PMI research does not explicitly articulate but that runs through all of its findings: the difference between organizations that have a change strategy and organizations that have built a **change capability**. These are different things, with different structures, measured by different metrics.\n\nA change strategy is a document, a set of initiatives, a transformation calendar. A change capability is an operational condition: the organization can detect signals, reallocate resources, make decentralized decisions, and execute in short cycles without every movement needing to travel up and down the full hierarchy. The first can be produced in a week of executive work. The second takes years to build and is destroyed quickly when organizational design does not sustain it.\n\nWhat the PMI describes as \"reinvention as a rhythm\" points precisely to this. Giles Lindsay, Chief Information Officer at Agile Delta, articulates it with precision when he says that reinvention \"becomes a capability, not a program.\" But the leap from that statement to the structure that makes it possible is exactly where the 35% of CEOs stuck in the planning-execution gap are stranded. Declaring that reinvention must be continuous is easy. Designing the governance mechanisms, the review cycles, the thresholds for autonomous decision-making, and the metrics that accompany each stage of the process is another matter entirely. Most existing operating models were built for stability and scale, not for two-year cycles. When they are asked to sustain permanent reinvention without modifying their internal structure, they creak.\n\nThe PMI research records that **the rate of change across six simultaneous factors — technology, talent, economics, geopolitics, climate, and consumer behaviour — grew by 183% since 2019**, and that **88% of senior leadership leaders expect that pace to accelerate**. What it does not record with the same clarity is how many of those organizations have modified their decision-making architecture to absorb that speed. Approving a transformation strategy every two years without redesigning how operational decisions are made is like changing the destination of a flight without touching the engines.\n\n## Silos Are Not a Cultural Problem — They Are a Design Problem\n\nApproximately one in four CEOs surveyed identified the presence of functional silos and the absence of shared accountability as the central obstacle to business agility. It is a diagnosis that sounds familiar because it has been appearing in organizational transformation reports for two decades. What changes is the interpretation.\n\nSilos are not primarily a cultural problem to be solved with collaboration workshops or leadership messages about shared objectives. They are the predictable result of incentive systems, reporting structures, and metrics designed to optimize the performance of individual functions, not the aggregate outcome of the organization. When the Chief Marketing Officer is evaluated on acquisition metrics, the Chief Operating Officer on cost efficiency, and the Chief Technology Officer on system availability, coordination among them does not occur naturally. It occurs in spite of the design, not because of it.\n\nHoward Yu, professor at IMD Business School, notes that the most agile organizations are \"always two or three steps ahead of the competition.\" What is not always stated is that this advantage does not come from more talented teams or more innovative cultures in the abstract, but from structures that allow information to flow horizontally, decisions to be made close to the problem, and resources to be reallocated without every movement requiring executive approval. The competitive advantage of agility is, at its core, an advantage in decision speed. And decision speed depends on how the structure is designed, not on how much collaboration is discussed in leadership meetings.\n\nThe Manifesto for Business Agility that PMI and Agile Alliance are launching aims to establish this level of analysis as the standard in boardrooms and senior leadership teams. The initiative has historical logic: the original Agile Manifesto of 2001 was born in the domain of software development and took more than a decade to infiltrate the general management of organizations. This expanded version is designed to operate from the outset at the level where operating model decisions are made. The question is not whether the framework has conceptual value, but whether the organizations that adopt it will use it to audit their structural design or simply to underpin transformation narratives that already existed.\n\n## The Signal That Most Unsettles an Organizational Architect\n\nThere is one data point in the PMI research that deserves more attention than it has received in the public analysis of the report. The proportion of organizations that rate themselves as highly agile rose from **35% in 2021 to 44% in 2024**. At first glance, it looks like progress. And in part it is. But placed alongside the other numbers from the same study, it produces a tension worth examining.\n\nIf 44% of organizations declare high agility, while at the same time 35% of CEOs admit a gap between planning and execution, and 25% identify functional silos as the main obstacle, something does not add up. Either the organizations that rate themselves as highly agile have structural problems that their own perception fails to detect, or the operational definition of \"high agility\" is capturing something different from the actual capacity to execute transformation. Both possibilities are concerning, though for different reasons.\n\nThe first implies that progress in agility is partly illusory: teams adopt agile rituals, leaders learn the language, reports reflect improvement, but the mechanisms that generate the gap — function metrics over company metrics, centralized decisions, annual budget cycles that do not align with biannual strategic review cycles — remain intact. The second implies that the measurement standard needs to be better calibrated to distinguish between organizations that have adopted agile practices and organizations that have redesigned their operational architecture to sustain continuous transformation.\n\nData from the Boston Consulting Group cited in the research provides a complementary perspective: **the probability of a transformation succeeding is 70% greater when leadership is aligned on scope and actively communicates to employees why they should be part of the change**. That number matters not so much as a celebration of leadership but as an indicator of how much variance remains concentrated at the apex of the organization. A truly distributed organizational architecture should reduce — not maintain — the dependence on leadership alignment as the determining variable for success. The fact that 70% of the difference between successful and failed transformations is still explained by what the three or four most senior executives do or fail to do suggests that the operating model most of these organizations are attempting to transform remains, at its core, hierarchical and centralized.\n\n## What Is Built Versus What Is Declared\n\nThere is a distinction that most reports on organizational transformation tend to blur because it is uncomfortable for everyone involved. The distinction between declaring that reinvention is continuous and building the operational infrastructure that makes it possible for that to be true.\n\nDeclaring is relatively costly in terms of executive time and relatively cheap in terms of organizational design. Building requires the opposite: modifying reporting structures, redesigning metrics systems, distributing budgets with different time horizons according to the stage of each initiative, establishing review mechanisms that do not collapse early learning under the performance criteria of a mature business. It requires, in sum, doing the work that nobody sees but that determines whether what was declared gets executed.\n\nThe PMI research documents with precision the state of the first level: consensus on the need for change is almost universal, the language of transformation is widely adopted, and the most frequently cited leaders speak clearly about experimentation culture and psychological safety. What falls outside the frame is the second level: the structural audit of how many of these organizations have concretely modified their governance models, their budget cycles, their metrics systems, and their distribution of decision-making autonomy to sustain what they declare.\n\nDavid Dabscheck, CEO of GIANT Innovation, argues that \"reinvention thrives in cultures where people feel safe to experiment and learn.\" That is correct, and it is not trivial. But psychological safety to experiment in cultures where the innovation budget is reviewed with the same profitability criteria as the core business has a very short half-life. Teams learn quickly that the space to fail and learn exists as long as experiments do not consume visible resources or produce results that contrast with the performance of the established business. As soon as they do, the existing organizational design activates its natural protection mechanisms.\n\nThe problem is not that leaders do not want to create those environments. The problem is that operating models have not been redesigned so that those environments are sustainable once the experiment begins to scale and compete for resources with the business that pays the bills.\n\n## The Operating Model Is Not Reinvented With a Manifesto\n\nThe publication of the Manifesto for Business Agility, with all of its institutional backing and its grounding in data from 700 executives, represents a genuine step forward in formalizing the problem. Naming a structural gap precisely is a necessary step toward closing it. But the distance between a leadership manifesto and a concrete modification of the operating model of a large organization is the same distance that separates the 93% executive consensus on the need for change from the 35% of CEOs who cannot manage to execute it.\n\nWhat the PMI research reveals, read through the lens of organizational design rather than project management, is that **the central deficit of most large organizations is not one of ambition or strategic vocabulary, but of operational engineering**: the capacity to build structures that convert the intention of transformation into decisions made in the right place, with the right metrics, at the right moment.\n\nWhen 65% of organizations are already rewriting their model every two years and still fail to close the gap between what they decide and what they implement, the problem does not lie in the pace of reinvention. The problem lies in the fact that the architecture that should sustain that reinvention was never redesigned. And an operating model that was not built to change does not become agile simply because its leaders sign a manifesto asking it to.","article_map":{"title":"Why 65% of Companies Rewrite Their Model Every Two Years and Still Fail to Execute It","entities":[{"name":"Project Management Institute (PMI)","type":"institution","role_in_article":"Publisher of the 700-executive survey and co-author of the Business Agility Manifesto; primary source of research data."},{"name":"Agile Alliance","type":"institution","role_in_article":"Co-author of the Business Agility Manifesto alongside PMI."},{"name":"Giles Lindsay","type":"person","role_in_article":"Chief Information Officer at Agile Delta; cited for articulating reinvention as a capability rather than a program."},{"name":"Howard Yu","type":"person","role_in_article":"Professor at IMD Business School; cited on the structural sources of competitive agility advantage."},{"name":"David Dabscheck","type":"person","role_in_article":"CEO of GIANT Innovation; cited on psychological safety and experimentation culture."},{"name":"Boston Consulting Group","type":"institution","role_in_article":"Source of complementary data on leadership alignment and transformation success probability."},{"name":"IMD Business School","type":"institution","role_in_article":"Academic institution associated with Howard Yu, cited as expert source."},{"name":"Business Agility Manifesto","type":"product","role_in_article":"The framework jointly published by PMI and Agile Alliance; central institutional output analyzed in the article."},{"name":"Agile Manifesto 2001","type":"product","role_in_article":"Historical reference point for the new manifesto; originated in software development and took over a decade to reach general management."}],"tradeoffs":["Speed of declaring transformation vs. time required to build the operational infrastructure that makes it executable","Optimizing individual function performance (via siloed metrics) vs. optimizing aggregate organizational outcomes (requires structural redesign)","Maintaining centralized decision-making for control vs. distributing autonomy to accelerate execution speed","Applying uniform profitability criteria to all budgets (predictability) vs. differentiating budget evaluation by initiative maturity stage (enables experimentation)","Adopting agile rituals quickly for visible progress vs. redesigning governance slowly for durable capability","Dependence on top leadership alignment for transformation success vs. building distributed architecture that reduces that dependence"],"key_claims":[{"claim":"65% of organizations rewrite their business approaches every two years or less.","confidence":"high","support_type":"reported_fact"},{"claim":"35% of CEOs identify a disconnect between planning and execution as their primary barrier to agility.","confidence":"high","support_type":"reported_fact"},{"claim":"93% of senior executives acknowledge operating models must be reviewed at least every five years.","confidence":"high","support_type":"reported_fact"},{"claim":"The rate of change across six simultaneous factors grew 183% since 2019.","confidence":"high","support_type":"reported_fact"},{"claim":"88% of senior leaders expect the pace of change to accelerate further.","confidence":"high","support_type":"reported_fact"},{"claim":"Self-rated high agility rose from 35% in 2021 to 44% in 2024.","confidence":"high","support_type":"reported_fact"},{"claim":"BCG data shows transformation success probability is 70% higher when leadership is aligned and communicates actively.","confidence":"high","support_type":"reported_fact"},{"claim":"Silos are a design problem, not a culture problem — they result from incentive and metric systems optimized for individual functions.","confidence":"medium","support_type":"inference"}],"main_thesis":"The planning-execution gap documented by PMI is not a speed, culture, or ambition problem — it is an organizational design problem. Most companies have built change strategies but not change capabilities, and the difference lies in governance structures, decision-making architecture, and metric systems that remain hierarchical and centralized even as transformation language becomes universal.","core_question":"Why do organizations that continuously redesign their strategy still fail to execute transformation, and what structural conditions would need to change for that to stop?","core_tensions":["Universal consensus on the need for transformation vs. persistent failure to execute it at the structural level","Rising self-assessed agility scores vs. unchanged planning-execution gaps and silo prevalence","The declared goal of distributed, continuous reinvention vs. operating models that remain hierarchical and centralized","Psychological safety as a cultural aspiration vs. budget and metric systems that punish visible experimentation","The Business Agility Manifesto as a tool for structural change vs. its risk of becoming another layer of transformation narrative"],"open_questions":["How many of the organizations that rate themselves as highly agile have concretely modified their governance models, budget cycles, and decision autonomy thresholds?","What operational definition of 'high agility' would accurately distinguish ritual adoption from genuine architectural redesign?","At what point does leadership alignment cease to be the dominant variable in transformation success — and what structural conditions produce that shift?","How should innovation budgets be structured and evaluated differently from core business budgets to sustain experimentation beyond early stages?","Will the Business Agility Manifesto be used as a structural audit instrument or absorbed into existing transformation narratives without changing operating model design?","What is the minimum governance redesign required for a two-year strategic review cycle to produce executable outcomes rather than repeated declarations?"],"training_value":{"recommended_for":["Chief Operating Officers and Chief Transformation Officers designing or auditing operating models","Strategy consultants advising on organizational redesign and transformation execution","Board members evaluating the credibility of management transformation narratives","Organizational designers and governance architects","Business agents trained on strategy execution, organizational design, and transformation management","Investors or analysts assessing whether a company's stated transformation strategy is structurally executable"],"when_this_article_is_useful":["When advising an organization on why repeated strategic planning cycles are not producing execution results","When diagnosing whether an organization's agility problem is cultural, structural, or both","When evaluating the credibility of self-reported agility assessments in due diligence or organizational audit contexts","When designing governance or operating model changes to support a transformation initiative","When assessing whether an agility framework adoption is likely to produce structural change or remain at the practice and narrative level","When building a business case for redesigning incentive systems, reporting structures, or budget allocation models"],"what_a_business_agent_can_learn":["How to distinguish between a change strategy (document) and a change capability (operational condition) and why the difference determines execution outcomes","How to diagnose whether organizational silos are a culture problem or a design problem, and what interventions address each level","How to interpret self-assessed agility scores critically by cross-referencing them with structural indicators such as decision autonomy thresholds and budget cycle alignment","How leadership alignment data (e.g., BCG's 70% variance finding) can be read as a structural warning rather than a leadership prescription","How to evaluate whether a framework or manifesto is being used as a structural audit tool or as a narrative reinforcement instrument","How to identify the organizational design conditions — metrics, governance, budget cycles, decision thresholds — that determine whether declared transformation becomes executed transformation"]},"argument_outline":[{"label":"1. The central finding","point":"65% of organizations rewrite their business model every two years or less, yet 35% of CEOs identify a persistent disconnect between planning and execution as their primary barrier.","why_it_matters":"This combination proves the problem is not frequency of strategic review but the structural capacity to implement what is reviewed."},{"label":"2. Change strategy vs. change capability","point":"A change strategy is a document; a change capability is an operational condition enabling decentralized decisions, fast resource reallocation, and short execution cycles without full hierarchical traversal.","why_it_matters":"Most organizations invest in the first and assume the second follows. It does not. The second requires years to build and is destroyed quickly by misaligned organizational design."},{"label":"3. Silos as design output, not culture failure","point":"Functional silos persist because incentive systems, reporting structures, and metrics are designed to optimize individual functions, not aggregate organizational outcomes.","why_it_matters":"Solving silos with collaboration workshops leaves the structural cause intact. The fix requires redesigning metrics and accountability, not messaging."},{"label":"4. The self-assessment paradox","point":"Self-rated high agility rose from 35% to 44% between 2021 and 2024, yet planning-execution gaps and silo problems remain at the same scale.","why_it_matters":"Either agility progress is partly illusory — teams adopt rituals without redesigning architecture — or the measurement standard conflates agile practices with genuine operational transformation."},{"label":"5. Leadership dependence as a structural signal","point":"BCG data cited in the research shows transformation success is 70% more likely when senior leadership is aligned and communicates actively. This is framed as a leadership insight but is actually a structural warning.","why_it_matters":"A truly distributed architecture should reduce dependence on top leadership alignment as the primary success variable. Its persistence as the dominant factor confirms most operating models remain hierarchical at their core."},{"label":"6. Declared vs. built","point":"Declaring continuous reinvention is cheap in organizational design terms. Building it requires modifying governance, budget cycles, metrics, and decision autonomy thresholds — work that is invisible but determinative.","why_it_matters":"The gap between declaration and execution is precisely the gap between what leaders say in transformation narratives and what the operating model is actually engineered to sustain."}],"one_line_summary":"PMI research across 700+ executives reveals that the core failure of organizational transformation is not lack of ambition but absence of operational architecture to execute what is declared.","related_articles":[{"reason":"Directly parallel structure: documents a large-scale investment in transformation (AI) where execution and ROI fail despite massive resource commitment, mirroring the planning-execution gap analyzed here.","article_id":14401},{"reason":"Examines how 93% of AI budgets go to technology while the 7% allocated to organizational and human factors determines outcomes — a concrete instantiation of the declared-vs-built distinction central to this article.","article_id":14321}],"business_patterns":["Organizations achieve intellectual consensus on change but fail at structural implementation — the consensus-execution gap is a recurring pattern across industries and geographies","Agile practice adoption precedes and often substitutes for agile architecture redesign, creating a measurement illusion of progress","Transformation success remains disproportionately concentrated at the apex of the hierarchy, indicating operating models have not been fundamentally redesigned","Silos regenerate after cultural interventions because their structural causes (incentive and metric design) are not addressed","Innovation budgets evaluated with core-business profitability criteria systematically suppress experimentation at scale","Manifestos and frameworks are adopted as narrative tools before they are applied as structural audit instruments"],"business_decisions":["Whether to invest in building a change capability (operational architecture) versus producing a change strategy (document and initiatives)","Whether to redesign incentive systems and reporting structures to align function-level metrics with aggregate organizational outcomes","Whether to distribute budget authority with differentiated time horizons by initiative stage rather than applying uniform profitability criteria","Whether to establish autonomous decision-making thresholds that reduce hierarchical traversal for operational changes","Whether to audit governance models and decision-making architecture before adopting agility frameworks","Whether to use the Business Agility Manifesto as a structural audit tool or as a narrative reinforcement instrument","Whether to recalibrate self-assessment of organizational agility against structural indicators rather than practice adoption"]}}