Alexandra, a technology director at an international logistics group, has just finished reading a memo from the CEO. The company, under pressure from investors and upcoming regulations, is preparing its first comprehensive ESG (Environmental, Social, and Governance) report. The memo was short, but it contained one question that completely changed Alexandra’s priorities for the coming months: “What is the carbon footprint of our IT department and what is our strategy to reduce it by 20% in the next three years?”. Alexandra realized that throughout her career she had been optimizing technology along three dimensions: performance, reliability and cost. Never before had she had to measure or manage the fourth, key dimension: environmental impact. Suddenly she was faced with a new, unfamiliar challenge. She had no tools, no reliable data, and most importantly, no coherent strategy. She realized that her role as a technology leader had just fundamentally evolved. It is no longer enough to be the guardian of digital transformation. It is necessary to become the guardian of its sustainability. Alexandra’s story heralds a new era of responsibility for technology leaders around the world. Sustainability issues and ESG criteria have ceased to be a “soft”, marketing add-on, and have become a hard, measurable and increasingly regulated element of business strategy. The IT department, as one of the largest and fastest-growing consumers of electricity in any organization, has naturally found itself at the center of this discussion. CTOs today are expected not only to deliver innovation, but also to answer the fundamental question: how to do it responsibly? This article is a strategic guide for leaders facing this new challenge. We will show how to approach the topic of Green IT in a systemic way, how to measure and reduce the carbon footprint of technology and, most importantly, how to transform sustainability from a perceived burden and cost center into a powerful source of innovation, efficiency and long-term competitive advantage.

What is ESG and why is the IT department suddenly at the center of this discussion?

“90% of large enterprises will have adopted a multi-cloud infrastructure management approach by 2025.”

— HashiCorp, State of Cloud Strategy Survey 2024 | Source

ESG is an acronym for Environmental, Social and Governance. It’s a set of criteria used to evaluate the non-financial aspects of a company’s operations. Investors, customers and regulators are increasingly using these criteria to assess whether a company is managed in a responsible, ethical and sustainable ma

er.

  • E - Environment: Refers to the company’s impact on the planet. Includes aspects such as greenhouse gas emissions, energy and water consumption, waste management or biodiversity conservation.

  • S - Social responsibility: Refers to a company’s relationship with its employees, suppliers, customers and the communities in which it operates. Includes, among others, labor rights, diversity and inclusiveness, product safety or community involvement.

  • G - Corporate governance: Refers to the way a company is managed. Includes issues such as transparency, ethics, shareholder rights or board structure.

Why has IT taken center stage, especially in the context of “E”?

For a long time, IT’s impact on the environment was largely invisible. Servers tucked away in air-conditioned server rooms didn’t smoke like factory chimneys. But the scale of digitization has made this “invisible” footprint huge and continues to grow exponentially.

  • Huge energy consumption: Data centers, telecommunications networks and end devices already account for several percent of global electricity consumption, and forecasts indicate that this share will grow rapidly with the development of AI, IoT and 5G technologies. Just training advanced AI models, as we wrote in an article about the role of CTOs in the GenAI era, consumes gigantic amounts of energy.

  • Generation of electro-waste (e-waste): The short life cycles of IT equipment (servers, laptops, smartphones) lead to a huge mountain of toxic electro-waste, which is one of the fastest-growing environmental problems in the world.

  • Regulatory and market pressure: Regulations, such as the EU’s Corporate Sustainability Reporting Directive (CSRD), require large companies to report in detail on their environmental impact, including their carbon footprint. At the same time, customers and business partners are increasingly choosing companies that can demonstrate their commitment to sustainability.

As a result, the IT department has ceased to be viewed only through the prism of cost and functionality. It has become a key component of any company’s ESG strategy. Today, technology leaders are expected not only to manage their budgets, but also to manage the “carbon budget” of their organization.

What are the three main areas (Scope 1, 2, 3) of emissions and where does the technology fit into them?

To effectively manage a carbon footprint, one must first understand where greenhouse gas emissions are coming from. The most widely used international standard is the Greenhouse Gas Protocol, which divides emissions into three scopes (Scopes). Understanding this division is crucial for CTOs to know what they are directly responsible for and where they can have the greatest impact.

Shutterstock

Scope 1 (Scope 1): Direct emissions

  • What is it? Emissions from sources that are owned or directly controlled by the company.

  • Examples: Burning fuels in company cars, heating boilers or power generators.

  • IT’s role: In most technology companies, IT’s share of Scope 1 emissions is relatively small, unless the company has its own large backup generators for its data centers.

Scope 2 (Scope 2): Indirect emissions related to purchased energy

  • What is it? Emissions generated during the production of electricity, heat or steam that the company buys for its needs.

  • Examples: Power consumption by offices, and especially by in-house , on-premise data centers (on-premise data centers).

  • IT’s role: This is the CTO’s first key area of responsibility. Energy consumption of servers, cooling systems and network infrastructure in a company’s server room accounts for a significant portion of Scope 2 emissions in many organizations. Optimizing this area is the foundation of a Green IT strategy.

Scope 3 (Scope 3): Other indirect emissions (in the value chain).

  • What is it? This is the broadest and often the largest category. It includes all other emissions that are the result of a company’s operations, but come from sources that are not owned or controlled by the company.

  • Examples:

  • Production of purchased equipment: The carbon footprint associated with the production of servers, laptops and smartphones that the company buys.

  • Cloud services: Emissions generated by the data centers of cloud providers (AWS, Azure, GCP) in connection with the services used by the company.

  • Business travel and employee commuting.

  • Disposal of products at the end of their life cycle (e.g., electro-waste).

  • The role of IT: The CTO’s influence on Scope 3 is enormous and growing. Decisions about choosing a cloud provider, hardware purchasing strategy, remote working policy or designing energy-efficient software have a direct impact on this issue category. This is where the greatest potential for strategic action lies.

For most modern technology companies, the largest IT footprint lies in Scope 2 (in-house data centers) and, most importantly, Scope 3 (cloud services and hardware supply chain). An effective Green IT strategy must address both of these areas.

What is Green IT and what are its key principles?

**Gree ** IT, also known as sustainable IT, is a comprehensive approach to designing, manufacturing, using and disposing of information technology in a way that minimizes its negative impact on the environment. It is not a single initiative, but a holistic philosophy that should permeate all aspects of IT operations.

The goal of Green IT is not only to reduce negative impact, but also to use technology as a tool to drive sustainability throughout the company. The Green IT strategy is based on several key principles:

1 Measure & Report: You can’t manage what you don’t measure. The first step is to implement systems and processes to measure the energy consumption and carbon footprint generated by your IT infrastructure. This includes in-house data centers as well as resources in the cloud (where providers such as AWS, Azure and GCP are offering increasingly better reporting tools).

2. optimize & reduce (Optimize & Reduce): Once we know where we are using the most energy, we can start implementing optimization strategies. This includes:

  • Energy efficiency in data centers: Cooling system upgrades, server consolidation, virtualization.

  • Cloud resource optimization (GreenOps): Shutting down unused machines, sizing instances appropriately (rightsizing), using regions powered by renewable energy.

  • Software efficiency: Designing and writing code that is more efficient and requires less computing power to perform the same task.

3 Manage the Lifecycle: IT’s environmental impact is not only energy consumption, but also hardware.

  • Responsible Purchasing: Choosing equipment from manufacturers that care about a sustainable supply chain and produce equipment that is energy-efficient, repairable and recyclable.

  • Life cycle extension: Instead of replacing equipment every 3 years, aim to extend its life cycle through repairs and upgrades.

  • Responsible Disposal (ITAD - IT Asset Disposition): Implement safe and environmentally sound recycling and disposal processes for decommissioned equipment to prevent the generation of electro-waste.

4. use technology to transform (Enable Transformation): This is the most strategic aspect. IT should not only be “less harmful,” but should actively help the entire company achieve its sustainability goals. Examples include:

  • Promote remote working and virtual meetings, reducing commuting and business travel emissions.

  • Digitization and dematerialization of processes, which reduces paper consumption.

  • Building intelligent systems (e.g., for logistics or building management) that optimize fuel and energy consumption across the organization.

Implementing these principles transforms the IT department from a perceived environmental “problem” to a key “problem solver” and leader of the company-wide sustainability strategy.

How do you practically measure the carbon footprint of IT infrastructure, especially in the cloud?

Measuring IT’s carbon footprint is the first and most important step in any Green IT strategy. Without hard data, all measures remain guesswork. The measurement process differs depending on whether we are talking about on-premise infrastructure or the public cloud.

Measuring carbon footprint in the on-premise data center: This is relatively simple, although it requires the right tools.

  • Measuring energy consumption: The basis is to measure the electricity consumption (in kilowatt-hours - kWh) of the entire data center, including servers, network, storage and, very importantly, cooling and uninterruptible power supply (UPS) systems.

  • Calculation of the Power Usage Effectiveness (PUE) indicator: PUE is a standard data center energy efficiency ratio. It is calculated by dividing the total energy consumed by the data center by the energy consumed directly by the IT equipment. The ideal PUE is 1.0. The average PUE is about 1.5-2.0, which means that for every kilowatt hour consumed by a server, an additional kilowatt hour is used for cooling and other auxiliary systems.

  • Conversion to CO2 emissions: The energy consumed (in kWh) is multiplied by a grid-specific emission factor (expressed in kg CO2e / kWh). This factor depends on the energy mix of the country or region (the more renewable energy, the lower the factor).

Measuring carbon footprint in the public cloud: This is much more complicated because we don’t have physical access to data centers. We rely on the tools and data provided by the cloud providers themselves (AWS, Azure, GCP). Fortunately, in response to increasing pressure, these tools are getting better.

  • AWS Customer Carbon Footprint Tool: This is a tool available in the AWS console that shows the estimated carbon emissions associated with an account’s use of AWS services. It also shows historical trends and forecasts.

  • Microsoft Sustainability Calculator: a similar tool for the Azure platform that allows detailed analysis of Scope 1, 2 and 3 emissions associated with the use of Microsoft services.

  • Google Cloud Carbon Footprint: A tool that provides detailed reports on the gross emissions associated with the use of Google Cloud services for a given project and period.

How do these tools work? Cloud providers measure the total energy consumption of their data centers and then, using complex models, allocate a portion of that energy (and associated emissions) to individual customers in proportion to their resource consumption (e.g., VM hours, amount of data storage).

Challenges and Key Actions:

  • Ensure comprehensive tagging: To make cloud measurement useful, it’s crucial to have a rigorous tagging strategy, as we wrote about in the FinOps article. Only with tags will you be able to assign emissions to specific applications, teams and projects.

  • Combine data from different sources: In a hybrid environment, the real challenge is to integrate data from your own data centers with data from multiple cloud providers to get a single, consistent view of your total IT footprint.

  • Go beyond supplier data: Remember that vendor tools only measure emissions related to the operation of services. They do not include Scope 3 emissions associated with the production of the equipment on which these services run.

Measurement is an ongoing process. Implementing regular, automated carbon footprint reporting is the foundation for setting reduction goals and tracking progress over time.

How do FinOps and GreenOps practices complement each other in optimizing cloud resources?

In the context of cloud computing, cost optimization and environmental impact optimization are two sides of the same coin. FinOps and GreenOps are two, closely related disciplines that pursue the same goal - eliminating waste - but look at it through slightly different lenses.

  • FinOps asks: “How can we achieve the same business goals while spending less money?”.

  • GreenOps asks: “How can we achieve the same business goals while using less energy and generating fewer emissions?”.

In the cloud, where we pay directly for resources consumed (CPU hours, gigabytes of memory), the answer to both questions is often exactly the same. Every u

eeded server shut down is both a money-saver and a reduction in emissions. Every optimized, “lean” virtual machine means a smaller bill and a smaller carbon footprint.

Synergy in practice: All of the key FinOps practices we discussed in detail in our FinOps 101 guide are also key GreenOps practices:

  • Elimination of “zombie resources”: Identify and remove unused VMs, unconnected disks or old snapshots. This is pure financial and environmental savings.

  • “Rightsizing”: Matching the size and power of instances to their real-world load. “Oversizing” a server that bores at 10% CPU usage most of the time is a waste of money and energy.

  • Automatic shutdown/scaling: Implement policies that automatically shut down development and test environments during off-hours or scale applications to zero during periods of low demand.

  • Optimizing data storage: Moving infrequently used data to cheaper and less energy-intensive storage classes (e.g., from S3 Standard to S3 Glacier).

Where does GreenOps go one step further? GreenOps adds an additional “green” dimension to FinOps analysis, leading to even more informed decisions.

  • Choosing a cloud region: FinOps, looking only at price, could choose the cheapest region. GreenOps will also take into account the carbon intensity of the region’s energy. Launching an application in a region powered by hydro or wind energy (even if it is marginally more expensive) can drastically reduce the carbon footprint.

  • Carbon-aware scheduling of batch tasks: Tasks that do not need to be executed immediately (e.g., data processing, AI model training) can be automatically run at night or at times of day when renewable energy is highest on the grid.

  • Architecture choice: GreenOps points out that different types of cloud services have different carbon footprints. A serverless-based architecture can be much more energy efficient for erratic workloads than keeping virtual machines running all the time.

The combination of FinOps and GreenOps creates a powerful feedback loop. The pursuit of cost efficiency leads to emissions reductions, and the pursuit of sustainability leads to the discovery of new opportunities for financial savings. For the modern CTO, the two disciplines are inseparable.

How does software architecture (e.g., efficient microservices) affect sustainability?

Discussions about Green IT often focus on the infrastructure - on servers and data centers. However, it’s what runs on that infrastructure - that is, software - that has just as much, and often more, impact on final energy consumption. An inefficiently written, “heavy” and resource-intensive application will waste energy, no matter how optimized the data center is.

CTOs and architects have a tremendous responsibility and opportunity to influence a company’s carbon footprint through informed architectural decisions and the promotion of “green coding” (Green Coding) practices.

1 Efficiency is sustainability: The bottom line is simple: every CPU cycle that can be saved and every byte of data that doesn’t need to be transferred is a real energy savings. Optimizing software performance is no longer just a matter of better user experience - it’s becoming a pro-environmental measure. This includes:

  • Algorithmic efficiency: Selection of optimal algorithms and data structures.

  • Optimization of database queries: Avoiding u

ecessary queries and retrieving too much data.

  • Network transfer minimization: Data compression, efficient use of cache.

Application performance monitoring (APM) tools, such as the Flopsar Suite from ARDURA Consulting, which help identify bottlenecks and inefficient code, are also becoming Green IT tools in this context.

2 Architecture vs. resource consumption: The choice of architecture is fundamental.

  • **Monolith vs. Microservices: ** A monolithic application, in order to handle load growth in one small module, often needs to be scaled in its entirety, leading to wasted resources. A well-designed microservices architecture allows granular, independent scaling of only those components that actually need it, leading to much more efficient use of infrastructure.

  • Serverless architecture: For workloads that are highly irregular and “bursty,” a serverless architecture (e.g. AWS Lambda, Azure Functions) can be much more energy efficient. Resources are consumed only when code is actually executed, rather than kept idle.

3. “Carbon Awareness” at the application level (Carbon-aware Applications): This is a more advanced concept. An application can be designed to make decisions on its own based on the current carbon intensity of the power grid.

  • Load flexibility: An application can decide to run less critical, energy-intensive tasks (e.g., report generation, reindexing) at times when energy is “greener.”

  • “Eco” mode: The application can offer the user an “eco” mode that, for example, reduces the quality of video streaming or the data refresh rate when the user is on battery power, which saves power on both the device and the server.

Incorporating sustainability criteria into the definition of “good architecture” and “clean code” is an important next step in the evolution of software engineering. It’s a task for technology leaders to promote this awareness within their teams.

How to combine sustainability goals with innovation and competitive advantage building?

Many companies still view ESG and Green IT initiatives as an onerous chore and a cost center - something that needs to be done to please regulators and investors. This is short-sighted thinking. Leaders who can look at sustainability strategically are discovering that it can be a powerful driver of innovation, efficiency and long-term competitive advantage.

1 Efficiency as a source of savings: As we have shown with FinOps and GreenOps, the drive to minimize energy and resource consumption almost always leads to direct financial savings. Every unused CPU core, every gigabyte of u

ecessarily stored data is real money that can be invested in innovation. Sustainability enforces an engineering and operational discipline that makes the organization leaner and more efficient in the long run.

2 Innovation driven by constraints: The most creative solutions often emerge in response to difficult constraints. The need to design an application that consumes 50% fewer resources forces architects and developers to go beyond the usual and seek innovative, more efficient solutions. The requirement for sustainability can become the spark that ignites technological innovations that under other circumstances would never have occurred.

3 Talent advantage: A new generation of top technology talent wants to work for companies that share their values. An organization that can credibly demonstrate its commitment to sustainability and gives its engineers the opportunity to work on solving real global problems becomes a much more attractive employer.

4 Build a stronger brand and customer confidence: Today’s consumers and business customers are increasingly environmentally conscious. They are more willing to choose and are more loyal to brands that conduct business responsibly. A transparent and credible Green IT strategy can become an important part of a company’s value proposition and a key differentiator from competitors.

5 Exploring new business models: Competencies and technologies developed as part of an internal Green IT strategy can become the basis for entirely new products and services. A company that has become an expert in optimizing energy consumption in its systems can begin to offer this knowledge and tools as a consulting service to others.

Leaders who can tell the story of how their technology strategy contributes not only to revenue growth, but also to building a better, more sustainable future, are building companies that are not only profitable, but also resilient and respected.

Green IT strategy roadmap for a technology organization

The table below provides a sample, simplified roadmap that can help IT leaders structure their sustainability strategy, breaking down activities into logical time horizons.

Pillar of strategyShort-term actions (Quick Wins)Medium-term actions (Investments)Long-term actions (Transformation)Key metrics
**Measurement and Reporting**Activate and analyze data from cloud vendors' carbon footprint reporting tools.Implementation of a central platform for aggregating emissions data from various sources (on-prem, multi-cloud).Full integration of ESG reporting with financial systems. Automation of reporting for regulatory purposes (CSRD). Total IT carbon footprint (tCO2e), Carbon Intensity (CO2e per revenue/user).
**Infrastructure Optimizatio **Implement automatic shutdown policies for dev/test environments. Basic "rightsizing" in the cloud. Purchase of savings plans. Strategic selection of "green" cloud regions. Optimizing PUE in your own DC. Transitioning to a "carbon-aware" architecture. Dynamic load shifting to the greenest regions. Cloud Cost (Cloud Spend), Resource Utilization Index (Utilization), PUE (for on-premise).
**Sustainable Software Architecture**Adding performance criteria to code reviews. Promoting "Green Coding" awareness. Introduce "performance budgets" for applications. Refactoring of the most inefficient modules. Integrating sustainability criteria into the architecture design process. Experimenting with serverless architecture. Application response time, Resource consumption per transaction.
**Equipment Lifecycle Management (ITAD).**Audit of current recycling processes. Introducing basic recycling principles. Implement a policy to extend the life cycle of equipment (e.g., from 3 to 4-5 years). Establish cooperation with a certified ITAD company. Implementation of "Circular Economy" principles - choosing modular, easily repairable equipment. Equipment buy-back program from employees. Percentage of equipment recycled/reused, Average age of equipment.
**Culture and Processes**Launching an information campaign for employees. Establish an informal "green guild" in IT. Integration of ESG goals into IT department objectives. Organization of training courses. Implementing a responsible purchasing policy. Integration of ESG criteria into employee evaluation and bonus system. Full integration into the company culture. Level of employee engagement (survey results).

Planning an IT project? Learn about our Software Development services.

See also

Let’s discuss your project

Have questions or need support? Contact us – our experts are happy to help.

How can ARDURA Consulting help you develop and implement a sustainable IT strategy?

At ARDURA Consulting, we understand that sustainability has ceased to be a side topic and has become one of the key challenges and opportunities for modern technology leaders. We approach Green IT and ESG not as an isolated initiative, but as an integral part of a mature, holistic technology and business strategy.

As your Trusted Advisor, we help you every step of the way on this journey:

  • Assessment and Strategy: We start with a comprehensive audit of your current carbon footprint and Green IT maturity. We help you understand where you are and where you can go. Then, together with your leadership team, we develop a pragmatic and measurable sustainable IT strategy that is fully aligned with your business goals.

  • FinOps and GreenOps Optimization: Our deep expertise in FinOps is a natural foundation for GreenOps. We help you implement tools and processes that will allow you to accurately measure and optimize the cost and carbon footprint of your cloud resources, translating your green goals into real financial savings.

  • Designing sustainable architectures: Our architects and engineers understand how to design efficient, scalable and energy-efficient software. We help modernize existing applications and design new systems based on modern, sustainable patterns such as microservices and serverless.

  • Asset Lifecycle Management (SAM & ITAD): Our expertise in Software Asset Management (SAM) and equipment lifecycle management helps optimize procurement, eliminate waste and implement responsible disposal processes.

  • Access to competence: We know that finding sustainable IT experts is difficult. In flexible models such as **Staff Augmentation **, we can supplement your team with specialists to help implement your Green IT strategy.

At ARDURA Consulting, we believe that the companies of the future are those that can harmoniously combine innovation with responsibility. Our goal is to be a partner that delivers strategic vision and engineering excellence to help you build technology that is good not only for your business, but also for the planet.

If you are a leader who wants to turn an ESG challenge into your competitive advantage, consult your project with us. Together we can program a more sustainable future.