Toolkit

In Practice

Net Positive Sprint Kit - Part 9 of 9

Part 9 of 9 · Reference

Use this tool

  • To see how the tools could play out across a sprint
  • To help get buy-in from stakeholders
  • To give facilitators concrete scenarios to talk through with teams

You'll get

  • Concrete, illustrative scenarios for each tool
  • A sense of how the kit fits into normal delivery work
  • Ideas to adapt for your own projects

These are illustrative scenarios, not case studies. They show the kind of outcome that becomes possible when a team builds the habit of asking better questions during normal delivery, from behaviour design to technical optimisation. Each one is small on its own. The point is the habit, not the single win.

Delivery examples

From practice

1. Delivery route consolidation in a logistics platform

Tool used: User + Planet Story Cards

For example, a team working on a logistics platform could use the User + Planet Story Card format to reframe delivery options. Where the original design optimised for speed per parcel, the rewritten story prioritises consolidated drop-offs and in-store collection. Across a fleet, that kind of change reduces the average number of stops per route and the total distance driven.

2. Right-sizing an AI feature

Tool used: Impact Tags

For example, during backlog refinement a team could tag a proposed feature Impact-inference-heavy because it calls a large model on every interaction. A follow-up review might find that a smaller, cached model meets the same need, cutting both inference cost and response time.

3. Trimming a heavy page in review

Tool used: Impact Scan

For example, an Impact Scan on a recent release might reveal a page loading a full charting library for a single sparkline. Swapping it for a lightweight inline chart would cut bundle size and improve load time, with no change to what the user sees.

4. Batching notifications

Tool used: Sprint Planning Prompts

For example, prompts about API calls and user experience could lead a team to batch notifications rather than send them individually. That reduces API calls and server load, and improves the experience by cutting interruptions.

← Previous Success Indicators Complete → Sprint Kit Overview

Want help running a net positive sprint?

We facilitate net positive sprints for teams who want to embed sustainability into their digital delivery.

Get in touch