Facilitator Notes

Use this tool

Before running your first session with one of the tools
When explaining the kit to a new team or stakeholder
As a refresher if momentum has slowed

You'll get

A clear plan for introducing the kit without overwhelming the team
Language that works in organisations that have not adopted sustainability terminology
Confidence that you can adapt the tools to your context

Language

Finding the right framing

In organisations that have not adopted sustainability language, the word itself can feel abstract or ideological. Framing the work as "efficiency", "impact", or "future-proofing" is not a compromise. It is accurate. Reducing unnecessary API calls is an efficiency decision. Designing for low-bandwidth users is a resilience decision. Both happen to reduce environmental impact. Lead with whatever framing gets the team engaged, and let the sustainability conversation develop as the results speak for themselves.

Getting started

How to introduce the kit

Pick one tool that has clear relevance to work already underway. Use it inside an existing ceremony rather than creating a new meeting. Keep the setup light: explain the purpose in a sentence or two and get into the activity. Capture what comes out of it and share it with the team afterwards. At this stage you are building familiarity, not chasing results. If it surfaces one useful question or one concrete change, it has worked.

Guidance

Making it stick

Pick a moment when the team is already looking at work together: sprint planning, backlog refinement, or a retrospective.
Avoid adding more than 10-15 minutes to existing sessions at first.
Watch for signs of interest and adjust scope accordingly. If two prompts generate good discussion, that is enough for one session.
Check for trade-offs: some optimisations could affect accessibility, security, or user experience.
Share what you find. Circulate any useful changes, insights, or blockers so the work is visible beyond the room.

Handling resistance

If the team sees this as additional process overhead, start with the tool that delivers the most immediate, practical value. The Sprint Planning Prompts and Impact Scan tend to land well because they fit naturally into sessions that are already happening. Focus on outcomes the team already cares about, such as performance, page weight, or reduced complexity, and let the environmental framing follow. Behaviour design opportunities can also generate quick buy-in, because they often align with business goals like increased engagement or reduced operational cost.

In practice

Examples

For example, a facilitator might pick three Sprint Planning Prompts relevant to that week's work and slot them into normal backlog refinement. In under ten minutes, that kind of discussion can surface changes to image formats, content choices, and how a third-party library is used.

Or a team reviewing a booking flow could use a prompt to ask whether the feature might surface lower-impact alternatives, and decide to make click-and-collect the default over home delivery, cutting per-order transport emissions.

Output

The team has tried one tool in a real context and has a shared sense of whether and how to use more.

Measurement & Validation

Track participation: number of team members actively contributing during the first tool run-through. Capture any follow-up actions logged in the backlog as a result.

← Previous Why This Matters Next → Sprint Planning Prompts