How We Created a Product Loop Statement for ClimateScope
- Esuabom Dijemeni
- Jun 20
- 4 min read
Every product development journey starts with a question:
What exactly are we building, who are we building it for, and why does it matter?
Over the years, we've learned that one simple tool helps answer those questions better than anything else:
Before we write a single line of code, design a screen, or schedule a sprint, we create a Product Loop Statement. It gives our team a shared direction, aligns everyone around the same goal, and keeps us focused on delivering real customer value.
In this blog, I'll walk you through how we created a Product Loop Statement for ClimateScope, an AI-powered climate risk platform, and how you can use the same approach in your own product development journey.
Table of Content
Why Every Product Development Journey Needs a Product Loop Statement
It's easy for product teams to get distracted.
New ideas appear. Customer requests increase. Features pile up.
Before long, everyone is working hard, but not necessarily in the same direction.
A Product Loop Statement helps solve this problem by creating clarity around:
What you're building
Who is building it
How long you're working on it
The outcome you're trying to achieve
Think of it as a simple compass for your product development journey.
Product Loop Statement Step 1: Set the Start Date
The first step in creating a Product Loop Statement is deciding when the loop begins.
We like to keep this simple.
For ClimateScope, we used the date when the customer formally requested the work.
The customer request came through on:
✅ Start Date: 28/05/2026
This gave us a clear starting point and created alignment across the team.
Product Loop Statement Step 2: Define the Loop Number
Next, we identify which loop we're currently working on.
A loop represents a focused cycle of product development.
For ClimateScope, this wasn't our first time working with the client.
In fact, it was our third product loop together.
✅ Loop Number: 3
Tracking loop numbers helps us understand where we are in the product's evolution and provides valuable context for future decisions.
Product Loop Statement Step 3: Name the Team
Now comes a surprisingly important step.
Who is responsible for delivering the outcome?
During our first loop, we spent time creating a team identity.
After brainstorming more than 15 different names, we finally landed on:
✅ Team Name: Climate Innovator
At first glance, this might seem like a small detail.
But we've found that giving a team a shared identity strengthens ownership, accountability, and collaboration throughout the product development process.
Take your time with this step. A good team name often stays with you for many loops.
Product Loop Statement Step 4: Focus on One Product and One Feature
This is where many product teams get into trouble.
The temptation is to work on everything at once.
Instead, we force ourselves to focus on:
One product. One feature. One outcome.
For this loop, we were working on:
ClimateScope (MVP Version 03)
To decide what mattered most, we held two 90-minute planning sessions.
Session 1: Customer Discovery
Together with our customer, we explored:
Why this product mattered
How it would be used
What success would look like
Session 2: Feature Prioritisation
We reviewed potential features and identified the one with the highest impact.
The winning feature was:
Climate Risk Engine
An AI-enabled climate risk modelling tool designed to help investors assess climate-related investment risk faster and more accurately.
✅ Product & Feature: ClimateScope – Climate Risk Engine
This level of focus helped us avoid feature overload and concentrate on what would create the most value.
Product Loop Statement Step 5: Define the Duration
Every Product Loop Statement needs a clear time boundary.
Without a deadline, work expands endlessly.
For our MVP projects, we usually work within a timebox of:
1 week for low complexity
2–3 weeks for medium complexity
4 weeks for high complexity
Because the Climate Risk Engine involved AI modelling and climate risk calculations,
we classified it as high complexity.
✅ Duration: 4 Weeks
The timebox forced us to focus on delivering value rather than chasing perfection.
Product Loop Statement Step 6: Define the Key Benefit
This is the most important part of the entire Product Loop Statement.
What outcome are we trying to create?
To answer this question, we didn't guess.
Instead, we spoke with:
Our client
Five of their customers
We wanted to understand the real problem from the user's perspective.
What we discovered was eye-opening.
At the time, calculating climate investment risk typically required:
2–3 climate analysts
Approximately 5 working days
The process was slow, expensive, and difficult to scale.
Customers wanted something dramatically faster.
The key benefit became clear:
✅ Allow investors to calculate investment climate risk within 10 minutes
This single statement became the guiding outcome for the entire loop.
Every decision we made was evaluated against this goal.
Product Loop Statement Step 7: Create the Product Loop Statement
Now it's time to bring everything together.
We use the following Product Loop Statement template:
For Loop [Loop Number],
[Individual / Team Name] is working on [Product] – [Feature]
For [Duration] from [Start Date]
In order to [Key Benefit]
Using our ClimateScope example, the final Product Loop Statement became:
Product Loop Statement
For Loop 3,
Team Climate Innovator is working on ClimateScope – Climate Risk Engine
For 4 weeks from 28/05/2026
In order to allow investors to calculate investment climate risk within 10 minutes
✅ Created Product Loop Statement
Final Thoughts
Before building roadmaps, creating wireframes, or writing code, spend a few minutes creating a Product Loop Statement.
It will help your team stay focused, make better decisions, and align around a shared outcome.
Simple.
Clear.
Focused.
Aligned.
Exactly what a Product Loop Statement should be.
Your Turn
Before starting your next product development journey, create your own Product Loop Statement.
Ask yourself:
What are we building?
Who is building it?
How long will we work on it?
What outcome are we trying to achieve?
Write your Product Loop Statement and use it as the foundation for every decision that follows.
Comments