Purpose

To track whether sustainability thinking is becoming part of how the team works and the product evolves over time.


<aside>

Use this tool:

You'll get:


Getting started

  1. Choose the indicators most relevant to your team from the table below.
  2. Review them regularly and record observations or scores.
  3. Discuss patterns and decide if any actions are needed.

Suggested indicators

Area Indicator
Team awareness Sustainability is discussed naturally in sprint planning.
Team awareness Alternative, lower‑impact solutions are raised and considered.
Development process Sustainability is mentioned in code reviews.
Development process Opportunities for optimisation are spotted during build.
Technical health Lighthouse or equivalent performance scores above agreed baseline.
Technical health Bundle sizes stable or reducing.
Technical health Image optimisation rate improving.
Technical health High caching hit rates.
User experience Product works well on slow connections and older devices.
Behavioural change Features assessed for real‑world environmental impact before build.
Behavioural change New features have measurably supported lower‑impact real‑world choices (e.g. reduced travel, energy savings, shared resources).

Tips