Toolkit

In Practice

Net Positive Sprint Kit - Part 9 of 9

Part 9 of 9 · Reference

Use this tool

  • To see how the tools work in real delivery contexts
  • To help get buy-in from stakeholders
  • To give facilitators proof points to share with teams

You'll get

  • Concrete examples of the tools applied in practice
  • Evidence that the kit fits into normal delivery work
  • Ideas to adapt for your own projects

These examples are drawn from delivery work across different types of organisation and product team. They are not exceptional cases. They are the kind of outcome that becomes possible when teams build the habit of asking better questions during normal delivery, from behaviour design to technical optimisation.

Delivery examples

From practice

1. Delivery route consolidation in a logistics platform

Tool used: User + Planet Story Cards

During a project with a wholesale client, a team used the User + Planet Story Card format to reframe delivery options. The original design optimised for speed per individual parcel. The rewritten story prioritised consolidated in store collection or consolidated drop-offs. After rollout, the feature reduced the average number of stops per route and cut total distance driven across the fleet.

2. Library swap in a banking app

Tool used: Impact Tags

In backlog refinement, a planned feature was tagged Impact-review-needed because it required a large third-party library. A follow-up review found a smaller library with the same functionality, reducing bundle size and improving load times.

3. Media optimisation in a campaign microsite

Tool used: Impact Scan

A design agency used the Impact Scan on a new microsite and spotted that the default design included a looping hero video and uncompressed images. They replaced the video with a still on mobile and compressed the images. Page weight fell and mobile performance scores improved.

4. Notification batching in a banking product

Tool used: Sprint Planning Prompts

During planning, prompts about API calls and user experience led a team to batch notifications instead of sending them individually. This reduced API calls, lowered server load, and improved the user experience by reducing 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