Why This Matters

When people talk about digital sustainability, the conversation often starts with topics like servers and image compression. That matters, and we cover it here. But the larger opportunity sits somewhere else. Digital products shape what people do in the real world, and those behavioural effects often outweigh the technical footprint of the product itself.

This page sets out both sides of that equation, along with a third dimension that is just as important: who your product works for, and who it leaves out.

Behaviour design

The footprint of what we enable

The products with the highest potential to drive environmental benefit are not always the ones with the smallest technical footprint. A well-designed feature that helps users share car journeys could have a more significant impact than a development efficiency like switching to WebP images. A logistics tool that reduces empty return trips, a booking system that encourages public transport, a platform that connects neighbours for shared school runs. These are product decisions, and they create or prevent real-world carbon.

Product teams shape behaviour at scale. The features they design, the defaults they set, the choices they surface all have consequences beyond the screen. A notification that nudges someone towards a lower-impact delivery option is a design decision with a measurable environmental outcome. A returns flow that makes keep-or-exchange more prominent than refund-and-rebuy is a design decision with a measurable environmental outcome. These opportunities can often get overlooked.

This is the less obvious argument for digital sustainability, and the more important one.

Digital efficiency

The footprint of what we build

The global digital sector accounts for between 2% and 4% of greenhouse gas emissions, roughly comparable to aviation. Every server request, every image load, every background sync consumes energy. The difference between a well-optimised product and a bloated one is measurable, and it compounds at scale. The average web page is now several times heavier than it was ten years ago, not because user needs changed, but because of defaults: uncompressed images, auto-playing video, unused JavaScript. The footprint is shaped by decisions, and most of those decisions were made without thinking about impact at all.

AI inference is accelerating this, a single query to a large language model can use more energy than a standard search. Teams building AI-assisted features need to factor inference cost into architecture decisions, not treat it as invisible.

Social impact

Whose needs get met

Digital products determine access to services, reinforce or reduce bias, and shape whose needs are prioritised. A product that works poorly on low-bandwidth connections or older devices is not a neutral technical decision. A feature built on assumptions about user context can exclude whole groups. An interface that fails basic accessibility standards locks people out of services they are entitled to use.

A product that reduces its carbon footprint but is unusable for a significant portion of its audience has not moved forward. Equitable access, inclusive design, and fair representation are part of the same conversation.

How the kit works across all three

The kit is designed to surface these decisions during normal delivery, not as a separate workstream. The Digital Carbon Quick Reference and Impact Scan help teams address technical efficiency. User + Planet Story Cards and Sprint Planning Prompts create space for behavioural and social impact opportunities that would otherwise go unnoticed.