{"id":670,"date":"2026-01-15T01:26:25","date_gmt":"2026-01-15T01:26:25","guid":{"rendered":"https:\/\/matt-rider.com\/?p=670"},"modified":"2026-06-24T16:36:22","modified_gmt":"2026-06-24T21:36:22","slug":"stop-upgrading-start-governing-rethinking-how-enterprises-operate-erp-at-scale","status":"publish","type":"post","link":"https:\/\/lumeraiadvisors.com\/staging\/9459\/stop-upgrading-start-governing-rethinking-how-enterprises-operate-erp-at-scale\/","title":{"rendered":"Stop Upgrading, Start Governing: Rethinking How Enterprises Operate ERP at Scale"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Enterprise resource planning platforms remain the operational backbone of most large institutions. They run finance, HR, supply chain, compliance, and reporting. Yet the prevailing model for managing ERP \u2014 perpetual upgrades driven by vendor roadmaps, multi-year transformation programs, and escalating maintenance obligations \u2014 has become a strategic liability rather than a source of competitive advantage.<\/span><\/p>

Boards increasingly recognize the contradiction. Organizations invest hundreds of millions of dollars in ERP platforms designed to ensure stability and control, yet these same systems often constrain agility, divert scarce talent from innovation, and absorb capital that could otherwise fuel growth. The result is not simply a technology challenge. It is a governance and operating model challenge.<\/span><\/p>

The question enterprise leaders must now confront is not whether ERP is important \u2014 it clearly is \u2014 but whether the way it is governed and operated still aligns with modern business priorities.<\/span><\/p>

<\/div>

The Hidden Cost of Vendor-Driven Roadmaps<\/span><\/b><\/p>

For decades, large organizations accepted a predictable cycle: implement ERP, customize heavily to match business needs, then undertake periodic, costly upgrades to remain on the vendor\u2019s supported path. These upgrade programs often span multiple years, consume significant executive attention, and require large cross-functional teams. They are justified as necessary to maintain security, compliance, and operational continuity.<\/span><\/p>

What is less frequently examined is the opportunity cost of this model.<\/span><\/p>

Major upgrade programs routinely pull the organization\u2019s best architects, engineers, analysts, and business SMEs into prolonged delivery efforts that deliver little net new business capability. Innovation slows. Digital initiatives stall. Modernization at the edges becomes secondary to sustaining the core. Technology leaders spend more time managing vendor timelines than advancing enterprise strategy.<\/span><\/p>

This pattern is visible across industries: highly capable organizations with talented teams trapped in cycles of \u201ckeeping the lights on\u201d rather than building the future.<\/span><\/p>

That is not a tooling issue. It is a structural design issue.<\/span><\/p>

<\/div>

ERP as Infrastructure, Not Differentiator<\/span><\/b><\/p>

One of the most important mindset shifts for modern technology leadership is recognizing what ERP is \u2014 and what it is not.<\/span><\/p>

ERP is infrastructure. It should be:<\/span><\/p>

  • Stable<\/span><\/li>
  • Predictable<\/span><\/li>
  • Secure<\/span><\/li>
  • Governed<\/span><\/li>
  • Compliant<\/span><\/li><\/ul>

    But it is rarely a source of differentiation. Customers do not choose an institution because its general ledger system is on the latest version. Market advantage increasingly comes from:<\/span><\/p>

    • Digital experience<\/span><\/li>
    • Data intelligence<\/span><\/li>
    • Automation<\/span><\/li>
    • Speed to market<\/span><\/li>
    • Product innovation<\/span><\/li><\/ul>

      Yet many organizations continue to invest disproportionate time and capital into the core while underinvesting at the edges \u2014 precisely where differentiation is created.<\/span><\/p>

      When ERP consumes the majority of executive attention, engineering capacity, and investment funding, the organization unintentionally optimizes for internal stability at the expense of external relevance.<\/span><\/p>

      That tradeoff is no longer acceptable in most competitive markets.<\/span><\/p>

      <\/div>

      The Governance Problem, Not the Technology Problem<\/span><\/b><\/p>

      It is tempting to frame this as a technology challenge \u2014 legacy platforms, technical debt, vendor constraints. In reality, the deeper issue is governance.<\/span><\/p>

      Most enterprises still operate ERP under a delivery model designed for an earlier era:<\/span><\/p>

      • Projects funded annually<\/span><\/li>
      • Roadmaps shaped heavily by vendor release cycles<\/span><\/li>
      • Success measured by on-time upgrades rather than business outcomes<\/span><\/li>
      • Architecture decisions driven by platform constraints rather than enterprise strategy<\/span><\/li><\/ul>

        This governance model implicitly treats ERP as the center of gravity for innovation rather than as foundational infrastructure that should fade into the background.<\/span><\/p>

        Modern operating environments require the opposite.<\/span><\/p>

        The ERP core must be governed for resilience and efficiency. Innovation must be governed separately \u2014 with distinct funding models, architectural patterns, and success metrics. When these two imperatives are blended together, both suffer.<\/span><\/p>

        <\/div>

        Decoupling Stability from Innovation<\/span><\/b><\/p>

        High-performing enterprises increasingly adopt a different posture:
        stabilize the core, decouple innovation from it.<\/b><\/span><\/p>

        This does not imply neglecting ERP. It means operating it deliberately:<\/span><\/p>

        • Prioritize stability over feature accumulation<\/span><\/li>
        • Limit customization that creates perpetual upgrade risk<\/span><\/li>
        • Treat upgrades as risk-mitigation events, not innovation programs<\/span><\/li>
        • Optimize operating cost and complexity<\/span><\/li><\/ul>

          At the same time, innovation occurs outside the core:<\/span><\/p>

          • Digital experiences<\/span><\/li>
          • Customer platforms<\/span><\/li>
          • Data and analytics layers<\/span><\/li>
          • Workflow orchestration<\/span><\/li>
          • Automation and AI capabilities<\/span><\/li><\/ul>

            These layers evolve continuously without being tightly coupled to the ERP upgrade cycle.<\/span><\/p>

            Architecturally, this often manifests as:<\/span><\/p>

            • API-first integration<\/span><\/li>
            • Modular service layers<\/span><\/li>
            • Event-driven architectures<\/span><\/li>
            • Decoupled user experiences<\/span><\/li>
            • Composable capability models<\/span><\/li><\/ul>

              Organizationally, it requires:<\/span><\/p>

              • Distinct ownership models<\/span><\/li>
              • Clear accountability for outcomes<\/span><\/li>
              • Funding mechanisms aligned to business value<\/span><\/li>
              • Governance structures that prevent the core from consuming all capacity<\/span><\/li><\/ul>

                This is not theoretical. Organizations that successfully separate core stability from edge innovation consistently outperform peers in both operational resilience and time-to-market.<\/span><\/p>

                <\/div>

                Rethinking the Role of Upgrades<\/span><\/b><\/p>

                None of this suggests that ERP upgrades are inherently wrong. They are often necessary for:<\/span><\/p>

                • Security posture<\/span><\/li>
                • Regulatory compliance<\/span><\/li>
                • Supportability<\/span><\/li>
                • Technical risk reduction<\/span><\/li><\/ul>

                  The issue is how upgrades are positioned and governed<\/b>.<\/span><\/p>

                  In too many organizations, upgrades are framed as transformation. They are treated as opportunities to redesign processes, re-engineer workflows, and modernize everything simultaneously. This framing dramatically increases risk, scope, and duration \u2014 and often results in fatigue rather than progress.<\/span><\/p>

                  A more disciplined approach treats upgrades as what they truly are:<\/span><\/p>

                  • Risk management exercises<\/span><\/li>
                  • Platform hygiene<\/span><\/li>
                  • Infrastructure stewardship<\/span><\/li><\/ul>

                    Transformation should occur deliberately and continuously outside the core, not episodically within it.<\/span><\/p>

                    This distinction alone can materially change how organizations allocate capital, deploy talent, and measure success.<\/span><\/p>

                    <\/div>

                    Implications for CIOs and Boards<\/span><\/b><\/p>

                    This shift has direct implications for executive leadership and governance.<\/span><\/p>

                    Boards increasingly expect technology leaders to:<\/span><\/p>

                    • Clearly articulate what technology investments are actually enabling<\/span><\/li>
                    • Demonstrate disciplined stewardship of foundational platforms<\/span><\/li>
                    • Explain how innovation capacity is being protected from operational drag<\/span><\/li>
                    • Quantify opportunity cost, not just project spend<\/span><\/li><\/ul>

                      CIOs who frame ERP decisions purely in technical terms are increasingly out of step with board expectations. The conversation must move toward:<\/span><\/p>

                      • Strategic alignment<\/span><\/li>
                      • Capital allocation effectiveness<\/span><\/li>
                      • Organizational design<\/span><\/li>
                      • Risk versus agility tradeoffs<\/span><\/li>
                      • Long-term enterprise capability building<\/span><\/li><\/ul>

                        This is no longer a conversation about tools. It is a conversation about enterprise architecture as strategy.<\/span><\/p>

                        <\/div>

                        A More Sustainable Model<\/span><\/b><\/p>

                        The organizations best positioned for the next decade are converging on a model with several consistent characteristics:<\/span><\/p>

                        • A deliberately simplified ERP core, governed for stability<\/span><\/li>
                        • Clear architectural boundaries between core and innovation layers<\/span><\/li>
                        • Funding models that prioritize capabilities over projects<\/span><\/li>
                        • Measurement frameworks tied to business outcomes rather than delivery volume<\/span><\/li>
                        • Executive alignment that treats technology as enterprise infrastructure, not a perpetual transformation engine<\/span><\/li><\/ul>

                          This model does not eliminate complexity, but it contains it. It does not reject modernization, but it channels it toward areas of highest business leverage.<\/span><\/p>

                          Most importantly, it frees leadership capacity \u2014 both human and financial \u2014 to focus on what actually differentiates the enterprise.<\/span><\/p>

                          <\/div>

                          The Strategic Shift Leaders Must Make<\/span><\/b><\/p>

                          The critical shift for executive leaders is this:<\/span><\/p>

                          Stop asking whether ERP should be upgraded.
                          Start asking whether your operating model for ERP is enabling or constraining the enterprise.<\/span><\/p>

                          When ERP governance, funding, and architecture are designed with intentionality, the platform becomes what it should have always been: a stable foundation that quietly supports growth rather than dominating the organization\u2019s future.<\/span><\/p>

                          That is not a technology decision.
                          It is an executive one.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

                          Enterprise resource planning platforms remain the operational backbone of most large institutions. They run finance, HR, supply chain, compliance, and reporting. Yet the prevailing model for managing ERP \u2014 perpetual upgrades driven by vendor roadmaps, multi-year transformation programs, and escalating maintenance obligations \u2014 has become a strategic liability rather than a source of competitive advantage. Boards increasingly recognize the contradiction. Organizations invest hundreds of millions of dollars in ERP platforms designed to ensure stability and control, yet these same systems often constrain agility, divert scarce talent from innovation, and absorb capital that could otherwise fuel growth. The result is not simply a technology challenge. It is a governance and operating model challenge. The question enterprise leaders must now confront is not whether ERP is important \u2014 it clearly is \u2014 but whether the way it is governed and operated still aligns with modern business priorities. The Hidden Cost of Vendor-Driven Roadmaps For decades, large organizations accepted a predictable cycle: implement ERP, customize heavily to match business needs, then undertake periodic, costly upgrades to remain on the vendor\u2019s supported path. These upgrade programs often span multiple years, consume significant executive attention, and require large cross-functional teams. They are justified as necessary to maintain security, compliance, and operational continuity. What is less frequently examined is the opportunity cost of this model. Major upgrade programs routinely pull the organization\u2019s best architects, engineers, analysts, and business SMEs into prolonged delivery efforts that deliver little net new business capability. Innovation slows. Digital initiatives stall. Modernization at the edges becomes secondary to sustaining the core. Technology leaders spend more time managing vendor timelines than advancing enterprise strategy. This pattern is visible across industries: highly capable organizations with talented teams trapped in cycles of \u201ckeeping the lights on\u201d rather than building the future. That is not a tooling issue. It is a structural design issue. ERP as Infrastructure, Not Differentiator One of the most important mindset shifts for modern technology leadership is recognizing what ERP is \u2014 and what it is not. ERP is infrastructure. It should be: Stable Predictable Secure Governed Compliant But it is rarely a source of differentiation. Customers do not choose an institution because its general ledger system is on the latest version. Market advantage increasingly comes from: Digital experience Data intelligence Automation Speed to market Product innovation Yet many organizations continue to invest disproportionate time and capital into the core while underinvesting at the edges \u2014 precisely where differentiation is created. When ERP consumes the majority of executive attention, engineering capacity, and investment funding, the organization unintentionally optimizes for internal stability at the expense of external relevance. That tradeoff is no longer acceptable in most competitive markets. The Governance Problem, Not the Technology Problem It is tempting to frame this as a technology challenge \u2014 legacy platforms, technical debt, vendor constraints. In reality, the deeper issue is governance. Most enterprises still operate ERP under a delivery model designed for an earlier era: Projects funded annually Roadmaps shaped heavily by vendor release cycles Success measured by on-time upgrades rather than business outcomes Architecture decisions driven by platform constraints rather than enterprise strategy This governance model implicitly treats ERP as the center of gravity for innovation rather than as foundational infrastructure that should fade into the background. Modern operating environments require the opposite. The ERP core must be governed for resilience and efficiency. Innovation must be governed separately \u2014 with distinct funding models, architectural patterns, and success metrics. When these two imperatives are blended together, both suffer. Decoupling Stability from Innovation High-performing enterprises increasingly adopt a different posture:stabilize the core, decouple innovation from it. This does not imply neglecting ERP. It means operating it deliberately: Prioritize stability over feature accumulation Limit customization that creates perpetual upgrade risk Treat upgrades as risk-mitigation events, not innovation programs Optimize operating cost and complexity At the same time, innovation occurs outside the core: Digital experiences Customer platforms Data and analytics layers Workflow orchestration Automation and AI capabilities These layers evolve continuously without being tightly coupled to the ERP upgrade cycle. Architecturally, this often manifests as: API-first integration Modular service layers Event-driven architectures Decoupled user experiences Composable capability models Organizationally, it requires: Distinct ownership models Clear accountability for outcomes Funding mechanisms aligned to business value Governance structures that prevent the core from consuming all capacity This is not theoretical. Organizations that successfully separate core stability from edge innovation consistently outperform peers in both operational resilience and time-to-market. Rethinking the Role of Upgrades None of this suggests that ERP upgrades are inherently wrong. They are often necessary for: Security posture Regulatory compliance Supportability Technical risk reduction The issue is how upgrades are positioned and governed. In too many organizations, upgrades are framed as transformation. They are treated as opportunities to redesign processes, re-engineer workflows, and modernize everything simultaneously. This framing dramatically increases risk, scope, and duration \u2014 and often results in fatigue rather than progress. A more disciplined approach treats upgrades as what they truly are: Risk management exercises Platform hygiene Infrastructure stewardship Transformation should occur deliberately and continuously outside the core, not episodically within it. This distinction alone can materially change how organizations allocate capital, deploy talent, and measure success. Implications for CIOs and Boards This shift has direct implications for executive leadership and governance. Boards increasingly expect technology leaders to: Clearly articulate what technology investments are actually enabling Demonstrate disciplined stewardship of foundational platforms Explain how innovation capacity is being protected from operational drag Quantify opportunity cost, not just project spend CIOs who frame ERP decisions purely in technical terms are increasingly out of step with board expectations. The conversation must move toward: Strategic alignment Capital allocation effectiveness Organizational design Risk versus agility tradeoffs Long-term enterprise capability building This is no longer a conversation about tools. It is a conversation about enterprise architecture as strategy. A More Sustainable Model The organizations best positioned for the next decade are converging on a model with several consistent characteristics: A deliberately simplified ERP core, governed for stability Clear architectural boundaries<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[153],"tags":[12,13,14,16,17],"class_list":["post-670","post","type-post","status-publish","format-standard","hentry","category-technology-strategy","tag-cio-perspectives","tag-enterprise-transformation","tag-erp-strategy","tag-operating-models","tag-technology-governance"],"_links":{"self":[{"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/posts\/670","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/comments?post=670"}],"version-history":[{"count":1,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/posts\/670\/revisions"}],"predecessor-version":[{"id":3037,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/posts\/670\/revisions\/3037"}],"wp:attachment":[{"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/media?parent=670"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/categories?post=670"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/tags?post=670"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}