The best idea goes first.
Ideas pile up in every store. We write each one as a test with a hypothesis and a number to judge it by, score it, and run the backlog from the top.
- Ads
- Pages
- Offers
- Ideas in the first backlog
- [40]+
- Number that judges each test
- 1
- Tests a week on Growth partner
- [2–3]
Backlog · week [2]Where it sits
- Growth sprintIn it
- Growth partnerIn it
- LaunchIn it
What is a test backlog?
A test backlog is the list of every change you could make, each written as a test: what we change, what we expect and the number that decides it. Ours is scored by expected impact and effort, so the next test is always the one most likely to pay.
- Written as
- Change, expected result, deciding number
- Ordered by
- Impact and effort
- Covers
- Ads, pages, email and offers
- Shared
- One live document you can read any time
- Logged
- Every result, winners and losers
A fit, or not yet.
Honest both ways: if it isn’t the right first step, we’ll say which one is.
A good fit if
- Your team has more ideas than time, and the loudest one ships first.
- You redesign pages and can’t tell what worked.
- You want every win to come with a reason.
Not the right fit if
- You want a one-off redesign rather than tests.
- Your store has too few orders to read a test yet: we’d fix tracking and speed first.
In every backlog.
Every idea, written down
Yours, ours and the audit’s, in one list.A number per test
Cost per order, conversion rate or revenue per recipient, chosen before it runs.Impact and effort scores
So the order is argued once, on paper, not in every meeting.Weekly batches
The top of the list ships every week.The test log
Every result kept, so nobody re-runs a test that already lost.
From idea to result.
Every test follows the same four steps, whichever channel it’s in.
- Week 1
Collect
Ideas from the audit, your team and ours, in one list.
Raw list
[Name] · Paid media lead - Week 2
Score
Each idea becomes a test with a hypothesis, scored by impact and effort.
Test backlog
[Name] · Paid social and CRO - Every Monday
Run and read
The next batch ships; last week’s results go in the log.
Monday report
[Name] · Analytics - Week 6
Re-score
What we learned changes the order of what’s left.
Updated backlog
Saimul Islam · Founder
Where it sits.
Growth sprint
Included[Price]per [6]-week sprint[3] live tests from the top of the list.
Start a sprintGrowth partner
Included[Price]per month · [3]-month start[2–3] tests a week, across every channel.
Book a callLaunch
Included[Price]per project[5] tests planned before launch day.
Plan a launch
Prices are per plan, not per service. Every plan includes the audit, the 90-day plan and the Monday report.
Questions about test backlog.
Not on the list? Ask on a call, or by email.
Yes. Every idea goes in, and gets scored the same way as ours.
Before it starts, we set the number that decides it and how many orders it needs. Ads need about [50] orders a week; page tests about [200] orders per variant.
They stay in the log with what we learned, so the same idea doesn’t come back in six months.
Still have questions?Saimul Islam answers every one.Works well with.
Your turn
Let’s grow.
[30] minutes, no slides. You leave with the first [3] tests from your backlog.
Or write to [hello@domain.com]
