User + Planet Story Cards

Use this tool

When writing or refining user stories
In backlog refinement or sprint planning
When a feature could be delivered in more than one way

You'll get

A story format that captures user needs and environmental benefits in one place
A shared reference for impact-friendly design and development decisions
Acceptance criteria that make sustainability testable

The format

How to use

As a [user type]
I want to [do something]
So that [I meet my goal]
In a way that [reduces harm or adds benefit for the planet]

Fill in each part using real context from your product and users.
Add relevant acceptance criteria (see below).
Tag the story with Impact Tags if needed.

What to consider

Who is the user, and what is their goal
What behaviours, choices, or constraints affect environmental impact
How this story will scale if adopted widely
Any trade-offs between convenience, cost, and sustainability

In practice

Worked examples

As a frequent commuter
I want to see colleagues who travel the same route as me on the same days
So that I can arrange to share travel
In a way that reduces the number of cars on the road

As an online shopper
I want the option to collect my order from a nearby pickup point
So that I can reduce delivery trips to my home
In a way that cuts transport emissions and makes deliveries more efficient

More examples

User + Planet Story Examples

As a podcast listener, I want to download episodes so I can listen offline, in a way that offers quality options to manage file size.
As a team lead, I want to view usage stats by feature so I can spot and remove rarely used or high-load elements.
As a site editor, I want to see an alert when I upload large images so I can choose lighter alternatives.
As a field engineer, I want to access repair guides offline so I can troubleshoot without signal or extra downloads.
As a support agent, I want AI summaries of long threads so I can reduce screen time and resolve issues faster.
As a traveller, I want my tickets available offline so I can access them without signal or roaming charges.
As a shopper, I want to bundle orders into one delivery so I don't have to wait around for multiple packages.
As a reader, I want articles to load in low-data mode by default so I can browse on patchy connections.
As a user, I want AI-assisted search results so I can find relevant products faster, in a way that uses cached or lightweight inference where possible to avoid unnecessary compute.
As a delivery driver, I want routes optimised for shared drop-offs so I can reduce backtracking and fuel use.

Acceptance criteria

Suggested acceptance criteria

The lower-impact option is presented as the default or most prominent choice
The feature includes a way to measure whether users are choosing the lower-impact option
Works with minimal steps for the user
Supports offline use where possible
Uses event-driven updates instead of constant polling
Re-uses established patterns and components
Enables low-impact defaults (e.g. opt-in for heavier features)

Guidance

Tips

Keep the user benefit clear and avoid making it feel like a compromise.
Use this format alongside standard user stories if your team prefers, to make adoption easier.
Revisit stories during refinement to check for missed opportunities.
Check for trade-offs: ensure planet benefits do not compromise usability or introduce bias in the solution.

Output

User stories that build environmental impact into the core requirement, not as an afterthought.

Measurement & Validation

Count how many stories in a sprint include a planet benefit statement. For features delivered, assess uptake of the lower-impact option they enable.

← Previous Sprint Planning Prompts Next → Impact Tags