Decarbonization is a multi-year transformation that touches strategy, operations, procurement, finance, product design, and external reporting. It fails when it is treated as “the sustainability team’s job,” and it succeeds when it is run like any other enterprise-critical agenda: clear governance, explicit decision rights, a managed portfolio, and accountability that shows up in day-to-day operating rhythms.
An effective operating model solves five recurring problems. First, it creates authority to make tradeoffs across functions and business units, especially when emissions reduction competes with throughput, reliability, cost, or growth. Second, it embeds decarbonization into planning and capital allocation rather than leaving it as a reporting exercise. Third, it builds a measurement and controls spine that can withstand assurance and stakeholder scrutiny. Fourth, it mobilizes the organization so initiatives are owned where the work happens, with capacity and incentives to deliver. Fifth, it builds capabilities—skills, tools, and routines—so progress persists through leadership changes and business cycles.
This chapter provides a practical blueprint. We describe governance roles from the board to site level, discuss where the decarbonization team should sit, define functional responsibilities, lay out decision rights and escalation paths, and close with capability building and change management that makes decarbonization “how we run the business.”
15.1 Governance: Board, Executive Committee, and Sustainability Steering Committees
Governance is not paperwork; it is the mechanism by which the organization makes decisions under constraint. Boards and executives should not choose individual technologies, but they must ensure that targets are credible, risks are understood, and resources are aligned. Good governance is simple enough to run monthly, disciplined enough to resolve conflict, and connected to the annual planning and capital cycle.
Board oversight: The board sets expectations for ambition and integrity, approves major strategic shifts, and ensures decarbonization is integrated into enterprise risk management. In practice, boards come back to three questions: do we have a credible pathway, are we funding it, and can we defend our claims under scrutiny? Boards also ensure that incentives do not quietly reward short-term margin at the expense of long-term transition readiness.
Executive committee ownership: The executive committee owns delivery, not only messaging. It approves the enterprise pathway, adjudicates cross-business tradeoffs, and holds leaders accountable for interim milestones. It also approves policy choices that affect credibility, such as how Scope 2 market-based accounting is used internally, what the company’s stance is on offsets and removals, and how base years are recalculated after acquisitions or divestitures.
Sustainability steering committee: The steering committee is the operating forum that converts ambition into a managed portfolio. It should be chaired by an executive with authority over capital and operational priorities (often the COO, CFO, or a designated transformation sponsor). Its core tasks are to review progress against milestones, approve portfolio changes, remove blockers, and ensure enabling capabilities—data, tools, and talent—are being built. Membership should be cross-functional and stable: operations, finance, procurement, product/R&D, IT/data, risk/compliance, and communications. Invite business-unit leaders when decisions affect their capital plans or customer commitments. Keep the group small enough to decide, and use pre-reads to keep meeting time focused on tradeoffs and approvals rather than updates.
Governance works best when it runs on a predictable cadence and uses consistent artifacts. A monthly steering meeting is usually sufficient if it is supported by weekly program routines. The monthly agenda should be standard: review emissions performance and drivers, review initiative delivery and variances, review capital and resource conflicts, and review key risks and external commitments. Avoid using the forum to re-litigate definitions every month; settle methodology through a controlled accounting policy, then manage performance against that policy. When methods must change, approve the change deliberately and document it so trend lines remain explainable.
Two specialized forums are often necessary. Data and controls forum: owns methodology, emissions factors, system changes, and assurance readiness. Claims and communications forum: owns approved language, disclosure consistency, and review of high-visibility statements and customer claims. Some organizations combine these, but separating them can reduce friction by keeping technical debates out of executive time and keeping communications grounded in evidence and approved definitions.
A final governance principle is escalation clarity. If a plant needs downtime for a retrofit, procurement needs to accept a higher-cost supplier, or finance needs to adjust hurdle logic for a strategic project, the organization must know where and how that conflict is resolved. When escalation is ambiguous, teams delay decisions until deadlines force rushed compromises.
15.2 Where the Decarbonization Team Sits: Central vs. Business-Embedded vs. Hybrid
There is no single best org chart for decarbonization, but there is a best fit for your context. The right design depends on where emissions sit, how complex your portfolio is, and how much standardization you need across business units and geographies. The wrong design is easy to spot: a small central team with no authority trying to drive operational change, or dozens of scattered initiatives with no standards, no data spine, and no portfolio discipline.
Central model: A central team sets strategy, owns the baseline and reporting spine, designs enterprise programs (renewable sourcing, supplier standards, internal carbon pricing), and coordinates major cross-cutting initiatives. This model works well when the organization needs consistent standards, when data and claims risk is high, and when meaningful abatement can be driven through enterprise levers such as procurement, power sourcing, and shared systems. Its risk is distance from operations. If the central team also “owns the tons,” it can become a bottleneck and can lose credibility with operators who know the constraints. In a central model, you must explicitly create execution ownership at the site and business-unit level, or the program becomes analytical and slow.
Business-embedded model: Decarbonization resources sit within business units and sites, close to assets and day-to-day decisions. This model is effective when emissions are concentrated in operations and local engineering realism matters. It can move quickly on site-level initiatives because owners are close to constraints, downtime windows, contractor availability, and operator routines. Its risk is fragmentation: inconsistent methodologies, duplicated tool investments, uneven capability, and initiative portfolios that do not add up at enterprise level. Embedded models require a strong set of enterprise standards and a disciplined portfolio cadence, or the organization ends up with many local successes and an enterprise target miss.
Hybrid model: The most common “winning” design is hybrid. A central team owns standards, measurement, portfolio governance, and a small set of enterprise programs, while embedded resources own delivery in business units, plants, and major categories. The hybrid model preserves local ownership while preventing a patchwork of incompatible definitions and tools. It also creates a talent pathway: specialists rotate between central roles (methods, systems, portfolio) and embedded roles (delivery, engineering integration), building both credibility and capability. The hybrid model typically performs best when there is a clear separation between “rule-setting and enablement” (central) and “execution and sustainment” (embedded).
Regardless of structure, define the central team’s mandate carefully. It should not try to own every ton. Its primary value is to set the rules of the game and make delivery easier: consistent baselines and factor libraries, initiative libraries with overlap rules, standardized business-case methods, tools and dashboards, contracting playbooks, and governance routines that unblock decisions. Embedded teams then focus on execution: designing, commissioning, operating, and sustaining initiatives within local constraints and business priorities.
A practical sizing rule is to staff the central team for coordination and rigor, and staff embedded teams for delivery capacity. Central teams are typically heavier in program management, data, and strategy integration. Embedded teams are heavier in engineering, operations integration, and supplier or customer work, depending on where the footprint sits. If most emissions are Scope 3, procurement and product resources must be embedded in those functions, not only in “sustainability.”
15.3 Roles and Responsibilities Across Functions: Operations, Finance, HR, Procurement, R&D, IT
Decarbonization is not a function; it is a cross-functional operating system. Clarity on roles prevents two common pathologies: everyone assumes someone else owns the work, or everyone touches everything and nothing gets delivered. The goal is to make responsibilities explicit, tie them to decision points, and connect them to performance routines.
Operations and engineering: Own delivery of Scope 1 and 2 initiatives in plants, facilities, fleets, and utility systems. They run energy efficiency, electrification, fuel switching, reliability integration, and commissioning. Operations also owns persistence: ensuring setpoints, maintenance routines, and operator training keep savings from decaying. Engineering owns technical standards, project design, and vendor qualification for repeatable measures.
Finance: Owns integration into planning and capital allocation. Finance ensures business cases use consistent methods, that incremental costs are compared to correct counterfactuals, and that capex cycles align with the pathway. Finance also owns internal carbon pricing policies where used, and ensures decarbonization is reflected in portfolio steering, impairment considerations, and risk disclosures aligned to enterprise reporting.
Procurement and supply chain: Own upstream Scope 3 strategy and execution. Procurement sets supplier data requirements, embeds carbon into RFx and scorecards, negotiates improvement plans, and contracts for low-carbon inputs where available. Supply chain owns network design levers that reduce logistics emissions and improves load factors, routing, and modal choices. Together, they translate “supplier engagement” into measurable sourcing outcomes.
R&D and product: Own product decarbonization and the roadmap for low-carbon offerings. They manage life-cycle footprinting assumptions, redesign levers, material substitution, circularity, and use-phase efficiency. They also own product claims discipline in coordination with legal and communications, because product-level statements are often the highest scrutiny area.
IT and data: Own the systems that make emissions measurable and auditable. IT integrates emissions platforms with ERP, energy management systems, procurement systems, and product data. IT also owns data governance: master data, access controls, versioning, and cybersecurity for any IoT or metering infrastructure. Without IT partnership, decarbonization remains spreadsheet-driven and fragile.
HR and change: Own capability building, training, and incentives. HR helps define roles, competencies, learning pathways, and recruiting for scarce skills such as energy engineering, carbon accounting, life-cycle assessment, supplier data validation, and program management. HR also supports change management: embedding decarbonization into performance reviews, leadership expectations, and frontline routines.
Legal, compliance, and communications: Own claims governance, regulatory alignment, and risk management for public statements. They ensure disclosures are consistent with methods, customer claims are defensible, and contracts reflect what is being promised. They also help manage emerging regulation risk and ensure data and controls can withstand external assurance.
A useful way to formalize responsibilities is a single-page RACI for the handful of activities that matter most: baseline ownership, target setting, portfolio governance, capital approval, supplier programs, product claims, and reporting. Keep it short and update it when organizational changes occur; stale RACIs create more confusion than none.
15.4 Decision Rights, Escalation Paths, and Accountability Mechanisms
Decarbonization creates tradeoffs: capex versus opex, efficiency versus throughput, supplier cost versus customer requirements, and short-term margin versus long-term competitiveness. A strong operating model makes those tradeoffs explicit and assigns decision rights so teams do not stall.
Decision rights: Pre-defined authority about who decides what, at what threshold, using what criteria, and with what required inputs and approvals.
Start by defining the decision rights that drive most friction. Capital allocation: who approves decarbonization capex and what is required in the business case. Operational changes: who can change setpoints, schedules, and operating modes, and how safety and quality sign-offs work. Procurement choices: how carbon performance is weighted in supplier selection and when premiums are permissible. Claims language: who approves customer-facing and public statements and what evidence is required. Document them once and keep them stable.
Then define escalation paths. Many organizations use a three-level model. Level 1 is the initiative owner resolving issues within their domain. Level 2 is the cross-functional program lead or site leadership resolving conflicts across functions. Level 3 is the steering committee resolving conflicts that require tradeoffs in capital, policy, or enterprise priorities. Set explicit time limits for each level.
To make escalations efficient, many organizations use a lightweight decision packet that is required whenever an issue is pushed to Level 2 or Level 3. The packet should fit on one page and force clarity on what is being decided and why. It reduces meeting time and prevents circular debate.
- Decision needed: The exact choice required and the deadline by which it must be made.
- Options: Two to three viable paths, including “do nothing,” with key pros and cons.
- Emissions impact: Expected change in CO2e and how it is calculated.
- Financial impact: Incremental capex, opex, and any savings, expressed as a range.
- Operational impact: Downtime, reliability, safety implications, and mitigation actions.
- Dependencies: External constraints such as interconnection, permitting, suppliers, or infrastructure.
- Recommendation: The owner’s preferred option and the assumptions behind it.
Accountability mechanisms must connect targets to owned actions. If a business unit has a target but no authority to fund initiatives or influence suppliers, accountability becomes symbolic. Conversely, if initiative owners control actions but targets remain only corporate, local teams lose motivation. Mature organizations tie accountability at three levels. Outcome accountability: business units and major sites own emissions outcomes and intensity metrics. Initiative accountability: program owners own delivery of specific measures with verified impact. Enabler accountability: Track critical enablers explicitly until they are completed.
Embed accountability in routines. Monthly portfolio reviews should include variance analysis: what changed, why, and what will be done. Quarterly reviews should refresh the pathway and funded plan, including any reallocation across initiatives. Annual planning should translate targets into budgets and capacity plans. If decarbonization is reviewed only annually, the organization will drift and then “explain” misses rather than correct them.
Align incentives carefully. Tie a small portion of variable pay to verified delivery milestones and data-quality improvements that leaders can influence. Keep metrics few and auditable. Avoid net metrics that can be moved by boundary changes or credit purchases without operational progress.
15.5 Building Capabilities: Skills, Training, and Change Management
Decarbonization is a capability challenge as much as a capital challenge. Many organizations underestimate the skills required to design, deliver, measure, and sustain reductions. The result is predictable: project bottlenecks, weak business cases, inconsistent data, and fragile reporting. Capability building should be treated as an explicit workstream with milestones and owners.
Capability building: Systematically developing the skills, tools, routines, and culture required to deliver decarbonization repeatedly at scale.
Start with a skills map and a gap assessment. Most programs require a mix of technical, analytical, and change leadership skills. Technical skills include energy engineering, electrification and power systems, process engineering for fuel switching, commissioning, and reliability integration. Analytical skills include carbon accounting, data engineering, life-cycle assessment, supplier data validation, and scenario modeling. Change leadership skills include program management, stakeholder management, and field change leadership that can translate targets into new routines.
Training should be role-based, not generic. Operators and facilities teams need practical training on new setpoints, new maintenance routines, and safe operation of new equipment. Procurement teams need training on how to request and validate supplier emissions data and how to apply carbon criteria in RFx and renewals. Finance teams need training on incremental business-case logic, overlap rules, and scenario-based appraisal. Product teams need training on footprint boundaries, design levers, and claims discipline. Build simple learning paths and refresh them annually as tools and standards evolve.
Change management is about making decarbonization part of “how we run the business.” That requires visible leadership signals, a small number of non-negotiable routines, and frontline enablement. Build momentum through early wins, but do not let the program become a collection of one-time projects. Standardize what works, replicate it, and protect it with ownership and measurement. Use communications to reinforce practical behaviors: fixing leaks, maintaining control logic, using low-carbon purchasing standards, and closing measurement gaps that block delivery and credibility.
Finally, invest in talent mechanisms. Create clear roles and career paths, rotate high-potential leaders through decarbonization delivery roles, and build communities of practice that share tools, designs, and lessons learned. Scarce experts will not stay if decarbonization is treated as a side job with no advancement. A strong operating model treats decarbonization as a strategic capability and invests accordingly.
