Sustainable by design: rethinking digital quality

Sustainability in digital is still often framed around infrastructure choices - hosting, performance and carbon reduction. But this is only part of the picture.

There’s growing recognition that sustainability is also shaped by how digital systems are designed, built and maintained. This can be seen in the W3C Web Sustainability Guidelines (WSGs), as well as the work of the Green Software Foundation, which provides more technical guidance for making sustainability part of digital products.

In other words, sustainability is not just about what the web runs on, but how it’s built.

Sustainability doesn’t stop at launch

Most digital products aren’t finished at launch; they evolve continuously. This isn't just about maintenance to keep things running smoothly, but adding new features, responding to changing requirements and fixing those hidden bugs that can pop up.

This means sustainability is not defined at release, but in the ongoing cost of keeping systems usable, stable and adaptable over time. The more friction introduced during delivery, the more effort is required to sustain the product afterwards. Under pressure to focus on other priorities and metrics, sustainability can sometimes fade into the background.

Having a strategy in place to manage and maintain products is therefore incredibly useful in ensuring sustainability remains at the heart of a digital product.

The WSGs include this as one of their guidelines. Follow a product management and maintenance strategy calls on organisations to “maintain clear documentation, resourcing, and measurement practices for long-term product support, including security, sustainability, and early detection of failure risks.”

Sustainability, then, isn't just something to consider when a product is being designed or launched. It needs to be part of how that product is managed throughout its lifecycle.

The hidden cost of complexity

Complexity rarely appears all at once. It accumulates. Small inconsistencies, assumptions and shortcuts made during delivery compound into long-term overhead.

This creates a hidden cost - ongoing effort spent maintaining and correcting avoidable issues rather than improving or extending the system.

Again, there’s an item within the WSGs that speaks directly to this. Make deliverables understandable and reusable directs organisations to “create discoverable, maintainable, and reusable documentation and code resources that support long-term understanding, reuse, and sustainability”.

While this sits within the user experience design section, it's a principle worth keeping in mind across every aspect of creating and maintaining a digital product.

Complexity can also be found elsewhere. User journeys can become unnecessarily complicated rather than efficient and streamlined. User interfaces can become inconsistent as product requirements change over time. It can even exist within the finer details of a system, such as database queries that are unnecessarily numerous or inefficient.

In each case, complexity creates additional work. And when that complexity is avoidable, so too is some of the time, effort and resource required to maintain it. It's a form of waste that can exist within QA and delivery itself, as well as within the products we build.

Better quality means less rework

Well-built systems don’t just perform better - they require less intervention over time. Higher quality reduces instability, reactive fixes and the costs of change.

In this sense, quality is not about perfection at launch, but about reducing the need for future remediation. This is where digital quality becomes an important part of the sustainability conversation.

Testing, performance, accessibility and other quality practices can help teams identify problems before they become embedded within a product. Finding and addressing issues earlier can mean fewer reactive fixes, less duplicated work and systems that are easier to maintain as they evolve.

It's something we've seen in practice through the partnership between Studio 24 and Zoonou, where bringing independent QA into projects earlier has helped identify issues sooner and reduce time-consuming fixes later in development.

The result isn't simply a better product at launch. It's a product that requires less avoidable effort to sustain over its lifetime.

Building for the long-term

Sustainability in digital systems is about efficiency over time, not just efficiency at runtime.

Hosting, energy consumption and carbon output remain important parts of the conversation. But there is also a cost upstream, in how systems are designed, built, documented and maintained long after launch.

Complexity creates maintenance overhead. Poor quality creates rework. Over time, those effects can compound.

Thinking about sustainability through this wider lens gives teams another reason to focus on the quality and maintainability of what they build - not simply because it produces better digital products today, but because it can reduce the resources required to keep them useful tomorrow.