Running a Net Positive Digital Sprint

But they often miss a bigger opportunity to shift behaviours toward more sustainable outcomes. Outcomes that still deliver commercially, while improving results for people and the planet.

The problem isn’t a lack of intent. Most teams care. But sustainability tends to arrive late, raised after key decisions are made, scoped too narrowly, or quietly dropped in the name of speed.

That’s why we developed Net Positive Sprints, a simple, practical way to build sustainability into delivery work from the start, without slowing teams down or adding overhead.

Here’s how it works, and how to start using it in your next sprint.

What is a Net Positive Sprint?

A Net Positive Sprint is a standard delivery sprint, same cadence, same ceremonies, but approached with a different lens to not just get work done, but make conscious choices that reduce harm and add value. Each sprint is treated as an opportunity to deliver measurable benefit not only for users and the business, but for the wider system the product operates in, including its environmental footprint.

It’s built on our sprint methodology, ImpactStack - a lightweight layer that overlays your existing delivery process with key sustainability prompts, decision points, and metrics.

Each sprint in your project presents an opportunity to leave things in a better state than you found them. Our job is to surface that opportunity, make it visible, and help teams act on it.

⚠️ Note: In this context, “Net Positive” is our ambition - a direction, not a certified outcome. It demonstrates our intent to build digital experiences that give more than they take.

The Five Elements of a Net Positive Sprint

Every sprint includes five key elements from the ImpactStack framework. They are deliberately simple but work best when used consistently.

1. Impact Lens

Every sprint shapes impact, whether or not you talk about it. The key is to make that impact visible.

Before sprint planning begins, we ask a single strategic question:

“Where might this sprint create or reduce impact?”

The answers aren’t always obvious. Sometimes it’s a chance to reduce page weight or move away from carbon-intensive hosting. Other times, it’s about rethinking flows that nudge users toward unnecessary consumption, or optimising backend interactions to reduce server load.

We capture this in a simple Impact Note a sentence added to the backlog or sprint goal to surface where impact lives. Not every story will have one, but over time, patterns emerge.

2. Carbon Checks

At the end of each sprint, we run a lightweight sustainability check to flag where features may have increased or reduced environmental impact.

This does not calculate exact carbon emissions but builds team awareness, so they can spot patterns, and surface hotspots, such as bloated bundles, unnecessary API calls, or high-load third-party dependencies.

We treat it like a quick scan: visible trade-offs, red flags for review, and green flags where we’ve done well.

Over time, this helps teams develop a shared intuition for what drives impact and how small technical decisions accumulate into system-wide effects.

3. User + Planet Stories

Where it makes sense, we adapt conventional user stories into User + Planet format. These stories combine user value with environmental benefit, without compromising either:

As a frequent traveller, I want to see my booking history offline, so I can access my details without connectivity, reducing unnecessary data requests.

The key word is “so” the environmental benefit should be a natural extension of the user’s need, not an add-on. If it feels forced, don’t use it.

These stories are most helpful during backlog grooming and prioritisation, where they can tip decisions towards solutions that serve both user and planet. They’re not mandatory, but can be revealing.

4. Sustainable Defaults

Some of the most effective sustainability decisions are the ones users never see. That’s why we focus on sustainable defaults, practical, low-effort choices that quietly reduce impact while improving performance and usability.

These might include:

• Serving compressed images by default
• Lazy loading non-essential content
• Encouraging offline-first interactions where possible
• Encouraging reuse or repair before replacement, where it’s a natural fit
• Nudging users toward greener behaviours (e.g. low-carbon delivery choices)

The key is to design the default path with sustainability in mind. Users benefit from faster, smoother experiences. Businesses reduce server and data costs. And the system as a whole becomes lighter by design, not by exception.

The aim is to make small nudges that compound over time.

5. Retrospective Reflection

We close each sprint with a simple question:

“What did we do this sprint that had a sustainability angle either intended or not?”

We are not focused on metrics or blaming inaction but noticing what matters.

Sometimes the wins are deliberate, a feature optimised, a dependency removed. Sometimes they’re accidental, a decision that reduces load or cuts unnecessary steps. And sometimes there’s nothing to note, which is fine too.

The point is to build a habit of observation. Over time, teams develop a stronger sense of what shapes environmental impact, identify blind spots, and understand how decisions ripple across the product. That’s where the real shift happens.

Why This Matters

We think most teams care about sustainability, but in practice, it’s usually treated as a retrofit. It’s raised too late, scoped too narrowly, or handed off to someone else.

By the time you’ve chosen your architecture, data model, and user flows, most of your impact is already locked in.

Net Positive Sprints shift that timing. They integrate sustainability into the same decisions that shape performance, usability, and business outcomes, at the exact moment those decisions are being made.

That’s why it works. You’re not adding extra work. You’re changing the questions you ask while doing the work you’re already doing. Over time, this builds muscle memory, and teams begin to see the impact as part of product quality, rather than an external constraint.

Ready to Start?

We’re actively evolving the ImpactStack framework in real-world projects, refining our prompts, improving our carbon checks, and adapting to different delivery styles. Whether your team works in Scrum, Kanban, or something else, the core approach overlays your current process without disruption.

If you’re interested in piloting this in your workflow, or building a capability around sustainable delivery, we’d love to explore what that could look like together.

You don’t need to overhaul your whole process. Start with one sprint. Add one Impact Note. Build the habit.

That’s how change starts: not with a new framework, but with better decisions at the right moment.

The Net Positive Sprint approach is how we embed sustainability into everyday delivery. If you want help running one with your team, or building sustainability into your digital projects more broadly, we’re here. Our Sustainability & Circular Economy service.

Further Reading

• What Does the Term Net Zero Mean?
• Sprint
• Solutions
• Circular Economy and the 2030 Agenda.
• John Paul Toher