Section 1
The era of digital abundance is ending.
For two decades, IT strategy was built on an assumption of abundance. Unlimited storage. Elastic compute. Cheap experimentation. Clean up later, optimise later, account for it later.
That abstraction helped organisations move quickly. It also normalised waste. When something feels consequence-free, people stop asking whether it needs to happen at all.
We are now in a different era, and not because of new ambition. Because of physical limits that have caught up with the assumption. Power availability. Water availability. Material and manufacturing pressures. Capacity lead times. Supply chain fragility. Regulatory pressure. These are no longer abstract sustainability issues. They are technology management issues.
Before any of the rest of this course is useful, two things have to land. What IT actually does to the planet. And how big it has become. We take each in turn, then return to what that means operationally.
Section 2
What IT actually does to the planet.
Most sustainability conversations in IT collapse into a carbon-only frame. Carbon matters. It is also incomplete. The full footprint runs across six categories. A credible programme can name all six and explain how its own estate touches each.
Carbon and energy
Operational electricity used by servers, networks, devices, and cooling. The driver is grid intensity multiplied by demand. Visible on energy bills, but the real footprint depends on where and when the power is drawn.
Water
Evaporative cooling at large data centres. Closed-loop chillers in semiconductor fabrication. A single hyperscale facility can use water comparable to a small town. Often unmeasured, often excluded from disclosure, often material in water-stressed regions.
Materials and minerals
Copper, aluminium, silicon, rare earth elements, lithium, cobalt. Mined, refined, transported, assembled. A modern smartphone contains over seventy elements drawn from multiple continents. The footprint is locked in long before the device powers on.
E-waste
Over 50 million tonnes generated globally each year. The fastest-growing waste stream on the planet. A material share is processed informally, often in conditions that recover little of the value and damage local environments. Refresh culture is the upstream cause.
Social and supply chain
Labour conditions in mining and assembly. Conflict minerals routes. Informal recycling exposure. The social dimension is not optional alongside the . Increasingly it is the dimension regulators, investors and customers ask about first.
Land and heat
Data centre siting concentrates power, cooling and land demand on local grids and communities. Waste heat is rarely reused. Where capacity clusters, the local : on planning, on water, on , becomes the conversation, not the carbon number.
Why this taxonomy matters
If your sustainability story only talks about carbon and electricity, it is incomplete before the first challenge question lands. Each of these six is a different conversation, with different evidence, different owners, and different operational levers. The course returns to all six across later modules.
Section 3
The scale most people still underestimate.
The most common defensive reflex inside IT is to assume the estate is too small to matter. At organisational scale that argument collapses quickly. Globally, it does not survive the numbers.
The global digital footprint: headline figures
The headlines obscure where the load actually concentrates. National-level numbers reveal the exposure better than global averages.
Concentration: what the averages hide
"We're too small to matter" does not survive contact with the baseline
A large bank, retailer, hospital trust or government body running hundreds of thousands of devices, multiple data centres and a significant cloud estate is not too small to matter. The argument only sounds reasonable until somebody builds the baseline. After that, it stops sounding reasonable to anyone in the room.
Section 4
Digital systems are physical systems.
The single mindset shift that the rest of this course rests on is simple to state and uncomfortable to apply.
Every cloud service runs on physical infrastructure. Every server consumes electricity. Many data centres consume water. Every laptop is mined, manufactured, transported, used, and eventually disposed of. Every dataset sits on physical storage. Every network transaction relies on physical infrastructure somewhere.
Cloud does not remove infrastructure. It moves it. Software does not remove physical consequences. It shapes them. This is not activism. It is basic physics and supply chain reality, applied to the systems we all use every day.
The line you carry into every later module
If digital is physical, then digital consumption is physical consumption. Wasted compute is wasted electricity, wasted water, wasted minerals, and wasted manufacturing capacity. That framing is the through-line for the rest of the course.
Section 5
Five categories of digital waste.
If reporting is the wrong place to start, and it usually is, waste is the right one. It is where you build credibility fast, because outcomes are tangible. Every category below is simultaneously a cost problem and a sustainability problem.
Idle Compute
Instances left running with no meaningful workload. VMs spun up for testing and never terminated. Dev environments left on overnight. Systems running at 5–10% CPU utilisation with nobody noticing, or nobody accountable.
Storage Waste
Data retained indefinitely "just in case." Logs held for years with no access. Multiple uncompressed copies. Triple redundancy on non-critical assets. Dark data, stored but never used, is the fastest-growing category in most enterprise estates.
Application Waste
Duplicate platforms. Zombie applications nobody uses but IT still pays to run. Portfolio sprawl built up over years because rationalisation is politically difficult. Every unused application has a support cost, a licence cost, a security exposure, and an energy draw.
End-User Waste
Devices replaced on fixed procurement cycles regardless of condition. Peripheral sprawl: two monitors by default, docking stations issued as standard, cables and chargers treated as consumables. Laptops shipped by air because onboarding was planned at the last minute.
AI Consumption
Heavyweight model calls for queries that don't need them. No caching strategy. No tiered inference. Prompt inefficiency at scale: verbose prompts sent thousands of times daily by users who never think about the compute behind the response. AI is the fastest-growing ungoverned consumption category in enterprise IT.
The operational case for GreenOps
"If you're consuming compute, storage, or network that creates no value, you're paying for it twice: once on the invoice, and once in the carbon account."
GreenOps is a discipline that engineers, finance, procurement, and leadership should all care about equally.
Section 6
The GreenOps action model.
Most organisations that describe themselves as having a sustainability programme are, on closer inspection, running a reporting function. That is a starting point. It is not a destination.
Necessary for disclosure, compliance, and setting baselines. Not sufficient for operational improvement. Most organisations are at this level, and do not always know it.
If this is all you have, you have a communications function, not a sustainability programme. The output is data about the past. The question it cannot answer is: what are we doing about it?
Rightsizing, improving utilisation, reducing facility overhead, extending device lifespans. This is where most operational GreenOps effort sits, and where the most immediate wins are found.
Critical caveat: optimisation does not guarantee absolute reduction. A business growing at 20% per year while improving efficiency at 10% is still growing its footprint. This is where the rebound effect lives (covered in Module 5).
Consolidating duplicate platforms. Retiring unused applications. Designing services that require less compute. The highest-leverage decisions live here, because you are preventing waste, not managing it after the fact.
This is shift-left in practice. It requires earlier intervention than most governance models currently allow. Portfolio decisions, architecture choices, and data minimisation policies are all avoidance mechanisms.
Where is your organisation right now?
Honest self-placement is more valuable than optimistic placement. Most organisations sit at Level 1 or between 1 and 2. That is normal. The question is: what is blocking the next step?
Knowledge Check · Module 1 · Q1
Which of the following best describes the environmental impact of enterprise IT?
Select an answer to reveal the explanation.
✓ Correct: Option C
IT's environmental footprint sits across six interconnected categories. Treating carbon as the only impact misses cooling and chip-fabrication water draw, the mineral intensity of devices (70+ elements in a smartphone), 50+ million tonnes of e-waste a year, the social conditions in mineral and electronics supply chains, and the localised land use and waste-heat impact of large sites.
A credible GreenOps programme tracks carbon and the other five. Narrow framing produces narrow action, and usually shifts impact rather than reduces it. Scope-based emissions accounting is one cut through this picture and is treated in depth in Module 3.
Knowledge Check · Module 1 · Q2
An organisation announces it has "moved to cloud and eliminated its data centre carbon footprint." What is the most accurate assessment of this claim?
Select an answer to reveal the explanation.
✓ Correct: Option C
Moving to cloud is one of the most widely held and consequential misconceptions in enterprise IT sustainability. Cloud moves IT emissions from Scope 1 and 2 into Scope 3: it does not eliminate them. Under CSRD and SBTi, Scope 3 is required where material, and for organisations using cloud at scale, it always is.
Cloud providers run on energy with its own carbon intensity, which varies significantly by region. A shared responsibility model applies: providers manage infrastructure efficiency; the IT organisation is responsible for how it uses that infrastructure and for engaging providers on sustainability performance.
Knowledge Check · Module 1 · Q3
In the GreenOps action model, which level involves preventing unnecessary demand from materialising in the first place?
Select an answer to reveal the explanation.
✓ Correct: Option C
Avoidance is the most mature and impactful level. Rather than measuring waste (Reporting) or reducing it after the fact (Optimisation), Avoidance prevents the demand from occurring: through portfolio rationalisation, shift-left architecture decisions, data minimisation policies, and choosing not to run heavyweight AI where it is not needed.
Most organisations are stuck at Reporting. The financial and sustainability case is to progress to Optimisation and then into Avoidance, to shift left in the lifecycle where intervention is cheapest and most effective.
⏸ Pause & Reflect
Take 5–10 minutes. Write answers down. Specificity matters more than completeness.
Open discussion question: Where is the biggest single source of digital waste in your organisation right now, and who owns it?
Module 1: Key Takeaways
Carbon and energy, water, materials and minerals, e-waste, social and supply chain, and land and heat. Treating carbon as the whole picture is the first form of narrow action.
ICT is 2–4% of global GHG, comparable in order of magnitude to aviation. In Ireland, data centres reached around 20% of national electricity. A single hyperscale site can use as much water as a small town.
Cloud does not remove infrastructure. It moves it. Wasted compute is wasted electricity, water, minerals, and manufacturing capacity. This framing carries through every later module.
Idle compute, storage bloat, zombie apps, fixed-cycle device refresh, and ungoverned AI inference are simultaneously cost problems and sustainability problems. They are where credibility is built fast.
Reporting → Optimisation → Avoidance. Most organisations are still at Reporting and do not always know it. Honest self-placement is the precondition for moving up.
Designing demand out before it exists: portfolio rationalisation, shift-left architecture, data minimisation, model tiering. All of those beat optimising what should never have been built.
We now have the operational reality: what IT consumes, the order of magnitude, the mindset shift that digital is physical, the categories of waste that recur in every estate, and the three-level model that frames where action sits.
In Module 2 we define digital sustainability itself, separate footprint from handprint cleanly, and clear the three confusions (green IT, sustainable IT, and digital sustainability) that still derail otherwise serious conversations. From Module 3 onwards, the course turns to measurement, the estate, and the operational disciplines that follow from this foundation.