Section 1
The definition problem.
Ask ten people in a large organisation what sustainable IT means and you will get ten different answers. None of them are entirely wrong. The problem is they are all partial. Each describes a tactic rather than a discipline.
Common partial answers: all tactics, not a discipline
Carbon reporting. Renewable energy. Data centre PUE. Device recycling. Ethical AI. Green cloud. Net zero targets. E-waste programmes. None of those are entirely wrong. They are all tactics without a discipline behind them. Without a shared definition, programmes talk past each other, budgets get contested, and accountability does not land anywhere useful.
In practice, that means two things happening simultaneously: reducing negative impacts (energy, carbon, water, materials, waste, and harmful outcomes in supply chains) and increasing positive impacts (technology that enables sustainability outcomes elsewhere, and improves societal outcomes when deployed responsibly).
Section 2
Where impact sits: the lifecycle view.
Most programmes focus on operational energy. The definition includes the full lifecycle, and the biggest surprises are at the edges. Click each phase to explore.
IT lifecycle: proportional carbon footprint (illustrative). Click to explore
Section 3
Three dimensions that prevent confusion.
Without this separation, programmes routinely conflate different types of value, and end up talking past each other. This framework stops that.
The sustainability of the technology estate itself
This is where GreenOps sits. This is where operational control lives. The energy and water consumed by data centres and networks, the utilisation of cloud resources, the embodied impact of devices and servers, the data we grow, retain, and dispose of.
This is the non-negotiable foundation. Without it, nothing else is credible. A leader who leads with the handprint before securing the footprint creates a credibility problem the first time anyone asks for evidence.
Measurement frameworks (GHG Protocol), regulatory requirements (CSRD), and operational practices are established. Most organisations are somewhere on this journey. The question is where, and how honestly they answer it.
How technology enables sustainability outcomes outside the IT estate
Optimisation platforms that reduce waste in operations. Analytics that eliminate unnecessary transport. Building systems that cut energy and water demand. Digital workflows that replace physical activity. The multiplier effects technology creates on the wider business.
The catch: Handprint stories only land credibly once your own footprint is already under discipline. "We enabled significant carbon reductions elsewhere, but we have not measured our own estate" is a hard position to defend publicly.
Methodologies are less mature. Attribution is harder. But the scale of the opportunity exceeds the footprint dimension for most technology organisations. The measurement frameworks (Scope 4 / avoided emissions) are developing. The business case is significant.
Broader digital inclusion, equitable access, and responsible deployment
Digital inclusion and accessibility by design. Equitable access to technology. Responsible data use and privacy. Responsible AI deployment. The broader societal consequences of how technology is deployed and who it serves.
Treating this as charity is too narrow. Social outcomes intersect with governance and regulation, particularly as regulatory expectations around AI fairness, data ethics, and supply chain standards expand.
Regulatory expectations are expanding. Supply chain due diligence (CSDDD), AI regulation, and accessibility standards are creating governance obligations. This is no longer purely voluntary; it is increasingly a compliance domain.
The social conscience of the technology function
Introduced in Sundberg's Sustainable IT Playbook, the heartprint is worth treating separately from the broader social dimension because its intent and measurement are different. The heartprint represents direct positive impact for people, communities, and society through responsible and inclusive design.
Introduced as a fourth concept alongside the three dimensions. The heartprint focuses on direct social impact from design decisions, distinct from the broader structural social dimension of digital inclusion policy.
Section 4
Why sequence matters.
These are not competing priorities. They are nested disciplines, and the order in which you build them matters. The footprint is the non-negotiable foundation.
Section 5
Four things digital sustainability is not.
Being clear about what this is not will save significant time and prevent the most common programme failures.
A marketing narrative
If you cannot explain what you are measuring, how you are measuring it, and what operational changes that measurement is driving, you are running a communications exercise, not a GreenOps programme.
A single team's responsibility
Treating sustainable IT as a project owned by a central sustainability function turns it into reporting and workshops. Outcomes are driven by decisions across lifecycle phases. If accountability is not distributed, it stalls.
Just a data centre issue
Data centres matter, but modern estates include cloud, SaaS, networks, end-user devices, software behaviour, and data growth. Focus on one layer and you shift impact elsewhere, creating blind spots you will struggle to explain later.
A problem only technology can solve
Technology choices matter, but governance, incentives, procurement, and leadership behaviour are equally important. A technical fix applied to a governance failure will not stick.
The connection to corporate sustainability
The drivers creating urgency for corporate sustainability teams are the same ones landing on IT leaders' desks. They are the same conversation. An IT programme that exists in isolation from corporate sustainability goals will compete for investment as if it were a discretionary initiative, and will usually lose.
Section 6
Five characteristics of a credible GreenOps programme.
Knowing what digital sustainability is matters less than knowing what a credible programme looks like in practice. These five characteristics separate programmes that change decisions from programmes that produce documents.
Clear scope
The programme names what is inside the boundary and what is not: which facilities, which cloud providers, which device categories, which supply chain tiers. Ambiguity in scope allows every stakeholder to assume someone else owns the problem.
Decision points tied to real owners
Each material consumption area has a named person who can change it. Procurement owns supplier evidence. Platform engineering owns cloud utilisation. Facilities own PUE. If a metric has no owner with authority to act, it is decoration.
Operational metrics, not annual totals
Annualised carbon numbers tell you where you were, not where you are heading. Credible programmes track consumption at a frequency that supports intervention: monthly at minimum, weekly or real-time where the data exists.
Waste and efficiency focus
The starting point is always: what are we consuming that we do not need to consume? Idle resources, over-provisioned infrastructure, retained data with no business value, unnecessary application sprawl. Efficiency before offsetting. Demand reduction before optimisation.
Integrated into normal governance
GreenOps is not a side theatre. It runs through architecture review, procurement governance, capacity planning, portfolio rationalisation, and budget cycles. A programme that exists outside those forums has no route to changing decisions.
The test
If your programme cannot point to a specific operational decision that changed because of the data it produced, it is not yet a GreenOps programme. It is a reporting exercise with ambition.
Knowledge Check · Module 2 · Q1
An organisation's GreenOps lead says: "We offset our IT emissions by purchasing renewable energy certificates. Our carbon footprint is covered." What's the most accurate response?
Select an answer to reveal the explanation.
✓ Correct: Option C
Renewable energy certificates are a market-based instrument. They are a contractual mechanism used in sustainability reporting, but purchasing one does not change which electrons power your workload in a given hour. The grid is still the grid. GreenOps stays anchored in physical operational reality: how much you actually consume, how efficiently you consume it, and what levers you have to reduce waste and intensity.
Certificates can be part of a broader corporate sustainability strategy, but treating them as a substitute for operational discipline creates credibility problems the moment someone looks closely. Does your organisation currently distinguish between market-based and location-based carbon reporting?
Knowledge Check · Module 2 · Q2
Which of the following best describes the "handprint" dimension of digital sustainability?
Select an answer to reveal the explanation.
✓ Correct: Option B
The handprint is the positive sustainability value that technology creates outside the IT estate. Optimisation platforms that reduce operational waste, analytics that cut unnecessary transport, building management systems that reduce heating and cooling demand. These are real.
The catch is that handprint stories only land credibly once you have demonstrated discipline on your own footprint. "We enabled significant carbon reductions elsewhere, but we have not measured our own estate" is a hard position to defend publicly. Sequence matters.
⏸ Pause & Reflect
Take 5–10 minutes. Write answers down. Specificity matters more than completeness.
Module 2: Key Takeaways
Digital sustainability is a lifecycle and leadership discipline, not a brand position or a reporting exercise.
Footprint (in IT), Handprint (by IT), Social dimension (IT for society). Do not conflate them. They serve different purposes and require different measurement.
IT direct positive social impact (accessible design, digital inclusion, responsible AI) is worth separating from the broader social dimension.
Leaders who lead with the handprint before securing the footprint create a credibility problem the first time anyone asks for evidence.
IT sustainability operating in isolation from the broader corporate agenda will consistently lose the resource allocation argument.
Next
What comes next.
You now have a working definition, a framework that separates three dimensions, and five characteristics that distinguish a credible programme from a reporting exercise. The next question is: how do you measure any of this with enough rigour to support real decisions? Module 3 covers measurement: scopes, data quality tiers (measured, modelled, and proxy), carbon intensity, and how to build a baseline that holds up under scrutiny.