{"id":2454,"date":"2026-06-11T11:23:56","date_gmt":"2026-06-11T11:23:56","guid":{"rendered":"https:\/\/tvg.pyw.mybluehost.me\/?p=2454"},"modified":"2026-06-13T16:58:11","modified_gmt":"2026-06-13T21:58:11","slug":"aligning-technology-strategy-with-esgobjectives","status":"publish","type":"post","link":"https:\/\/lumeraiadvisors.com\/staging\/9459\/aligning-technology-strategy-with-esgobjectives\/","title":{"rendered":"Aligning Technology Strategy with ESGObjectives"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"2454\" class=\"elementor elementor-2454\" data-elementor-post-type=\"post\">\n\t\t\t\t<div class=\"elementor-element elementor-element-ad07b24 e-con e-atomic-element e-flexbox-base e-24f6d3c \" data-id=\"ad07b24\" data-element_type=\"e-flexbox\" data-e-type=\"e-flexbox\" data-interaction-id=\"ad07b24\" data-e-type=\"e-flexbox\" data-id=\"ad07b24\">\n    \t\t<div class=\"elementor-element elementor-element-574e508 elementor-widget elementor-widget-heading\" data-id=\"574e508\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">Aligning Technology Strategy with ESG\nObjectives<\/h2>\t\t\t\t<\/div>\n\t\t\n<\/div>\n<div class=\"elementor-element elementor-element-1d5b7f2 e-con e-atomic-element e-flexbox-base e-d0826a5 \" data-id=\"1d5b7f2\" data-element_type=\"e-flexbox\" data-e-type=\"e-flexbox\" data-interaction-id=\"1d5b7f2\" data-e-type=\"e-flexbox\" data-id=\"1d5b7f2\">\n    \t\t<div class=\"elementor-element elementor-element-575d713 elementor-widget elementor-widget-post-info\" data-id=\"575d713\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"post-info.default\">\n\t\t\t\t\t\t\t<ul class=\"elementor-inline-items elementor-icon-list-items elementor-post-info\">\n\t\t\t\t\t\t\t\t<li class=\"elementor-icon-list-item elementor-repeater-item-767cc5e elementor-inline-item\" itemprop=\"author\">\n\t\t\t\t\t\t<a href=\"https:\/\/lumeraiadvisors.com\/staging\/9459\/author\/coywright\/\">\n\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-icon-list-icon\">\n\t\t\t\t\t\t\t\t<svg aria-hidden=\"true\" class=\"e-font-icon-svg e-far-user-circle\" viewBox=\"0 0 496 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M248 104c-53 0-96 43-96 96s43 96 96 96 96-43 96-96-43-96-96-96zm0 144c-26.5 0-48-21.5-48-48s21.5-48 48-48 48 21.5 48 48-21.5 48-48 48zm0-240C111 8 0 119 0 256s111 248 248 248 248-111 248-248S385 8 248 8zm0 448c-49.7 0-95.1-18.3-130.1-48.4 14.9-23 40.4-38.6 69.6-39.5 20.8 6.4 40.6 9.6 60.5 9.6s39.7-3.1 60.5-9.6c29.2 1 54.7 16.5 69.6 39.5-35 30.1-80.4 48.4-130.1 48.4zm162.7-84.1c-24.4-31.4-62.1-51.9-105.1-51.9-10.2 0-26 9.6-57.6 9.6-31.5 0-47.4-9.6-57.6-9.6-42.9 0-80.6 20.5-105.1 51.9C61.9 339.2 48 299.2 48 256c0-110.3 89.7-200 200-200s200 89.7 200 200c0 43.2-13.9 83.2-37.3 115.9z\"><\/path><\/svg>\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t<span class=\"elementor-icon-list-text elementor-post-info__item elementor-post-info__item--type-author\">\n\t\t\t\t\t\t\t\t\t\tCoy Wright\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t<\/a>\n\t\t\t\t<\/li>\n\t\t\t\t<li class=\"elementor-icon-list-item elementor-repeater-item-26e3f7d elementor-inline-item\" itemprop=\"datePublished\">\n\t\t\t\t\t\t<a href=\"https:\/\/lumeraiadvisors.com\/staging\/9459\/2026\/06\/11\/\">\n\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-icon-list-icon\">\n\t\t\t\t\t\t\t\t<svg aria-hidden=\"true\" class=\"e-font-icon-svg e-fas-calendar\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M12 192h424c6.6 0 12 5.4 12 12v260c0 26.5-21.5 48-48 48H48c-26.5 0-48-21.5-48-48V204c0-6.6 5.4-12 12-12zm436-44v-36c0-26.5-21.5-48-48-48h-48V12c0-6.6-5.4-12-12-12h-40c-6.6 0-12 5.4-12 12v52H160V12c0-6.6-5.4-12-12-12h-40c-6.6 0-12 5.4-12 12v52H48C21.5 64 0 85.5 0 112v36c0 6.6 5.4 12 12 12h424c6.6 0 12-5.4 12-12z\"><\/path><\/svg>\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t<span class=\"elementor-icon-list-text elementor-post-info__item elementor-post-info__item--type-date\">\n\t\t\t\t\t\t\t\t\t\t<time>June 11, 2026<\/time>\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t<\/a>\n\t\t\t\t<\/li>\n\t\t\t\t<\/ul>\n\t\t\t\t\t\t<\/div>\n\t\t\n<\/div>\n<div class=\"elementor-element elementor-element-b2fdbf4 e-con e-atomic-element e-flexbox-base e-53935bd \" data-id=\"b2fdbf4\" data-element_type=\"e-flexbox\" data-e-type=\"e-flexbox\" data-interaction-id=\"b2fdbf4\" data-e-type=\"e-flexbox\" data-id=\"b2fdbf4\">\n    \t\t<div class=\"elementor-element elementor-element-f709ee1 elementor-widget__width-initial elementor-widget elementor-widget-text-editor\" data-id=\"f709ee1\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t\t\t\t\t\t<p>Most ESG conversations in enterprise technology focus on what companies are building toward \u2014 renewable energy integration, AI-driven efficiency, decarbonization roadmaps. Fewer focus on what organizations are destroying in the process. Large-scale ERP migrations consume enormous resources, displace experienced teams, and generate emissions that never show up in sustainability reports. That gap deserves attention.<\/p><p>ERP vendors have spent decades perfecting the art of manufactured urgency. End-of-support deadlines. Cloud migration mandates. \u201cStrategic roadmap\u201d language that obscures what customers are actually being asked to fund. For energy, utilities, and industrial companies carrying real ESG commitments alongside constrained IT budgets, the reflexive acceptance of vendor upgrade cycles is worth examining more critically.<\/p><h3>The Environmental Cost Nobody Accounts For<\/h3><p>A large ERP migration typically runs 18 to 36 months. During that period, the organization runs parallel systems \u2014 old and new \u2014 which can effectively double electricity consumption for extended stretches. Consultant teams fly in for workshops, go-live sprints, and hypercare support. The emissions from that travel are real, calculable, and almost never included in the upgrade business case.<\/p><p>For companies that have made public Scope 3 commitments, this matters. Scope 3 covers indirect emissions across the value chain, and IT project activity is a legitimate contributor. The carbon footprint of a major implementation \u2014 consultant flights, parallel infrastructure, the organizational churn of managing two systems simultaneously \u2014 is not trivial. It just goes unmeasured because the conversation never starts there.<\/p><p>Extending the life of existing enterprise software eliminates that footprint. A system already in production, already optimized, already running lean, does not carry those migration costs. That is a real environmental benefit \u2014 not a theoretical one. Companies serious about Scope 3 should be tracking it.<\/p><p>The AI dimension adds another layer. Data centers running enterprise AI workloads draw heavily on electricity and water. As organizations scale inference and agentic AI applications, infrastructure costs grow. That is not an argument against AI investment \u2014 predictive maintenance, smart grid optimization, and real-time emissions monitoring all deliver genuine sustainability value. But it does mean the capital allocation question matters. An avoidable $30M ERP upgrade that consumes two years of IT bandwidth is a real opportunity cost against the AI capabilities that actually move emissions metrics.<\/p><h3>What Happens to the People<\/h3><p>IT moves fast and discards slowly. When a company replaces a core enterprise system, it is not just swapping software \u2014 it is displacing years of institutional knowledge. The finance analyst who spent eight years learning how the system was configured for the company\u2019s specific processes. The IT team that built the integrations and kept them running. The workflow optimizations that took three years of refinement to get right.<\/p><p>Those things do not transfer automatically to the new platform. Some of them disappear. The workforce disruption from large-scale migrations rarely shows up in ROI calculations, but it shows up clearly in culture, morale, and retention data in the years following go-live.<\/p><p>Organizations that hold onto stable, well-optimized systems \u2014 and layer innovation on top rather than underneath \u2014 protect that institutional capital. They also free IT leadership to invest in the workforce development that actually matters: reskilling for AI and data roles, change management for operational technology, the human infrastructure that makes digital transformation stick.<\/p><p>The capital freed by avoiding a major migration does not disappear. It can go into training programs, community energy initiatives, distributed energy resource platforms, or the operational technology upgrades that reduce real emissions in the field. A utility that makes that choice is making a better ESG investment than one that spent the same budget satisfying a vendor\u2019s upgrade timeline.<\/p><h3>Governance Means Owning the Decision<\/h3><p>Here is the governance reality that most IT organizations do not say out loud: when 60 to 70 cents of every IT dollar goes to maintaining existing systems \u2014 vendor support, forced upgrades, unplanned migrations \u2014 that is not a strategy. It is a default. Someone else is setting the agenda.<\/p><p>Strong technology governance starts with controlling the capital allocation. Organizations that extend enterprise software lifecycles through independent support and lifecycle optimization reclaim that control. They get to decide what gets funded and when, based on business priorities rather than vendor support schedules. That is a governance improvement with direct ESG consequences \u2014 because it means the capital can go where it should go.<\/p><p>From a fiduciary standpoint, there is also a straightforward case for ESG ratings. Organizations that maximize the return on existing software investments, rather than retiring functional assets prematurely, earn credit for circularity and resource efficiency. That is not a side benefit \u2014 it is how lifecycle discipline gets scored.<\/p><p>The governance risk argument runs the other direction too. Rushed migrations fail. Data integrity problems surface 18 months post-go-live. Business disruption from system transitions has derailed entire transformation programs. Those are governance failures with financial and reputational consequences. Avoiding them is not conservative \u2014 it is prudent.<\/p><p>Boards are watching technology governance more closely now than they were five years ago. Cyber risk, AI oversight, regulatory scrutiny around data infrastructure \u2014 the bar has risen. CIOs who can demonstrate that they are making deliberate, strategic technology investments \u2014 not just responding to vendor pressure \u2014 are in a stronger position with their boards than those who cannot explain why the ERP migration consumed three years of IT capacity.<\/p><h3>The AI Infrastructure Trade-off<\/h3><p>The energy demands of enterprise AI are real and worth being direct about. Training frontier models is electricity-intensive. Running inference at scale \u2014 particularly for always-on agentic applications \u2014 requires persistent data center investment. Water consumption for cooling is a growing concern in regions already under pressure.<\/p><p>For energy and utilities companies, this creates a tension that is not going away: sustainability commitments on one side, AI adoption imperatives on the other. The companies navigating this well are not trying to slow AI \u2014 they are funding it more intelligently. Stable core platforms that do not require constant reinvestment create the budget headroom to build AI capabilities without compromising sustainability targets.<\/p><p>The framing I use with clients: core enterprise platforms are infrastructure, not strategy. Your competitive position does not come from running the latest version of your financial management system. It comes from what you build on top of a stable foundation, and whether you have the capital and organizational bandwidth to build it. That calculation points consistently toward lifecycle extension over vendor-driven replacement.<\/p><h3>The Practical Question<\/h3><p>For CIOs and technology executives, the question is where to start. A useful exercise is a time-to-value audit of every significant IT investment on the roadmap. For each one, ask honestly: what competitive or operational advantage does this deliver, and on what timeline? Back-office application upgrades driven by vendor end-of-support dates score poorly on that test. Grid modernization, predictive maintenance platforms, customer sustainability dashboards, advanced analytics \u2014 these score much higher.<\/p><p>The companies moving fastest in energy and utilities right now are not the ones with the largest IT budgets. They are the ones who figured out how to redirect maintenance spend toward innovation spend. That is the ESG technology story that is not getting told often enough.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\n<\/div>\n<div class=\"elementor-element elementor-element-0d499c9 e-con e-atomic-element e-flexbox-base e-684eebc \" data-id=\"0d499c9\" data-element_type=\"e-flexbox\" data-e-type=\"e-flexbox\" data-interaction-id=\"0d499c9\" data-e-type=\"e-flexbox\" data-id=\"0d499c9\">\n    \t\t<div class=\"elementor-element elementor-element-e25529a elementor-author-box--avatar-yes elementor-author-box--name-yes elementor-author-box--biography-yes elementor-author-box--link-no elementor-widget elementor-widget-author-box\" data-id=\"e25529a\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"author-box.default\">\n\t\t\t\t\t\t\t<div class=\"elementor-author-box\">\n\t\t\t\t\t\t\t<div  class=\"elementor-author-box__avatar\">\n\t\t\t\t\t<img decoding=\"async\" src=\"https:\/\/secure.gravatar.com\/avatar\/e4039614184b96d057aa115cafbc626a0f0c940e304e3afebf1a1cac06b9e541?s=300&#038;d=mm&#038;r=g\" alt=\"Picture of Coy Wright\" loading=\"lazy\" title=\"\">\n\t\t\t\t<\/div>\n\t\t\t\n\t\t\t<div class=\"elementor-author-box__text\">\n\t\t\t\t\t\t\t\t\t<div >\n\t\t\t\t\t\t<h4 class=\"elementor-author-box__name\">\n\t\t\t\t\t\t\tCoy Wright\t\t\t\t\t\t<\/h4>\n\t\t\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t\t\t\t\t\t<div class=\"elementor-author-box__bio\">\n\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\n<\/div>\n\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>Aligning Technology Strategy with ESG Objectives Most ESG conversations in enterprise technology focus on what companies are building toward \u2014 renewable energy integration, AI-driven efficiency, decarbonization roadmaps. Fewer focus on what organizations are destroying in the process. Large-scale ERP migrations consume enormous resources, displace experienced teams, and generate emissions that never show up in sustainability reports. That gap deserves attention. ERP vendors have spent decades perfecting the art of manufactured urgency. End-of-support deadlines. Cloud migration mandates. \u201cStrategic roadmap\u201d language that obscures what customers are actually being asked to fund. For energy, utilities, and industrial companies carrying real ESG commitments alongside constrained IT budgets, the reflexive acceptance of vendor upgrade cycles is worth examining more critically. The Environmental Cost Nobody Accounts For A large ERP migration typically runs 18 to 36 months. During that period, the organization runs parallel systems \u2014 old and new \u2014 which can effectively double electricity consumption for extended stretches. Consultant teams fly in for workshops, go-live sprints, and hypercare support. The emissions from that travel are real, calculable, and almost never included in the upgrade business case. For companies that have made public Scope 3 commitments, this matters. Scope 3 covers indirect emissions across the value chain, and IT project activity is a legitimate contributor. The carbon footprint of a major implementation \u2014 consultant flights, parallel infrastructure, the organizational churn of managing two systems simultaneously \u2014 is not trivial. It just goes unmeasured because the conversation never starts there. Extending the life of existing enterprise software eliminates that footprint. A system already in production, already optimized, already running lean, does not carry those migration costs. That is a real environmental benefit \u2014 not a theoretical one. Companies serious about Scope 3 should be tracking it. The AI dimension adds another layer. Data centers running enterprise AI workloads draw heavily on electricity and water. As organizations scale inference and agentic AI applications, infrastructure costs grow. That is not an argument against AI investment \u2014 predictive maintenance, smart grid optimization, and real-time emissions monitoring all deliver genuine sustainability value. But it does mean the capital allocation question matters. An avoidable $30M ERP upgrade that consumes two years of IT bandwidth is a real opportunity cost against the AI capabilities that actually move emissions metrics. What Happens to the People IT moves fast and discards slowly. When a company replaces a core enterprise system, it is not just swapping software \u2014 it is displacing years of institutional knowledge. The finance analyst who spent eight years learning how the system was configured for the company\u2019s specific processes. The IT team that built the integrations and kept them running. The workflow optimizations that took three years of refinement to get right. Those things do not transfer automatically to the new platform. Some of them disappear. The workforce disruption from large-scale migrations rarely shows up in ROI calculations, but it shows up clearly in culture, morale, and retention data in the years following go-live. Organizations that hold onto stable, well-optimized systems \u2014 and layer innovation on top rather than underneath \u2014 protect that institutional capital. They also free IT leadership to invest in the workforce development that actually matters: reskilling for AI and data roles, change management for operational technology, the human infrastructure that makes digital transformation stick. The capital freed by avoiding a major migration does not disappear. It can go into training programs, community energy initiatives, distributed energy resource platforms, or the operational technology upgrades that reduce real emissions in the field. A utility that makes that choice is making a better ESG investment than one that spent the same budget satisfying a vendor\u2019s upgrade timeline. Governance Means Owning the Decision Here is the governance reality that most IT organizations do not say out loud: when 60 to 70 cents of every IT dollar goes to maintaining existing systems \u2014 vendor support, forced upgrades, unplanned migrations \u2014 that is not a strategy. It is a default. Someone else is setting the agenda. Strong technology governance starts with controlling the capital allocation. Organizations that extend enterprise software lifecycles through independent support and lifecycle optimization reclaim that control. They get to decide what gets funded and when, based on business priorities rather than vendor support schedules. That is a governance improvement with direct ESG consequences \u2014 because it means the capital can go where it should go. From a fiduciary standpoint, there is also a straightforward case for ESG ratings. Organizations that maximize the return on existing software investments, rather than retiring functional assets prematurely, earn credit for circularity and resource efficiency. That is not a side benefit \u2014 it is how lifecycle discipline gets scored. The governance risk argument runs the other direction too. Rushed migrations fail. Data integrity problems surface 18 months post-go-live. Business disruption from system transitions has derailed entire transformation programs. Those are governance failures with financial and reputational consequences. Avoiding them is not conservative \u2014 it is prudent. Boards are watching technology governance more closely now than they were five years ago. Cyber risk, AI oversight, regulatory scrutiny around data infrastructure \u2014 the bar has risen. CIOs who can demonstrate that they are making deliberate, strategic technology investments \u2014 not just responding to vendor pressure \u2014 are in a stronger position with their boards than those who cannot explain why the ERP migration consumed three years of IT capacity. The AI Infrastructure Trade-off The energy demands of enterprise AI are real and worth being direct about. Training frontier models is electricity-intensive. Running inference at scale \u2014 particularly for always-on agentic applications \u2014 requires persistent data center investment. Water consumption for cooling is a growing concern in regions already under pressure. For energy and utilities companies, this creates a tension that is not going away: sustainability commitments on one side, AI adoption imperatives on the other. The companies navigating this well are not trying to slow AI \u2014 they are funding it more intelligently. Stable core platforms that do not require constant reinvestment create the budget headroom<\/p>\n","protected":false},"author":2,"featured_media":2469,"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":[10],"tags":[],"class_list":["post-2454","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-featured-insight"],"_links":{"self":[{"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/posts\/2454","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\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/comments?post=2454"}],"version-history":[{"count":19,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/posts\/2454\/revisions"}],"predecessor-version":[{"id":2720,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/posts\/2454\/revisions\/2720"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/media\/2469"}],"wp:attachment":[{"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/media?parent=2454"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/categories?post=2454"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lumeraiadvisors.com\/staging\/9459\/wp-json\/wp\/v2\/tags?post=2454"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}