♦In October, I started working on a side project, growing a small website for parents, Growing Wise: picture book guides, printable activity sheets, and a free game for children aged 4 to 8. It had about 10 visitors a day and had earned £0.22 in a month.
At that size, everything feels like it might be working. You change the homepage, two people click a button the next morning, and it’s very tempting to call that a win.
So I made one rule before making any changes: every change gets a row in a decision log. This is something I have seen great Software architects do, when everything is hypothesis you need evidence to prove the decision worked.
Eight weeks later, the log has 89 rows. It has taught me more about how I make decisions than about the website itself.
The format: one row per decisionEach row has six columns. None of them is optional.
♦The verdicts matter more than they might seem.
Too early stops me from declaring victory on day two.
Enabler is for work that doesn’t directly generate growth but makes other things measurable, such as tracking where visitors drop off.
Without that label, measurement work can look like wasted time. With it, the log makes it clear that every other verdict depends on having reliable data.
Writing the Why before shipping is the most useful habit of all.
If I can’t name the problem and the number that shows it, I’m not ready to make the change.
The rules that keep it honestA log is only as useful as the rules defining what counts as evidence. I wrote four at the top, before any results came in.
1. One day proves nothing.
At 10 visitors a day, a verdict needs at least a week of data, unless the effect is obvious. Even then, a small sample means conclusions should remain cautious.
2. Every open decision has a check date.
When I make a change, I write down when I’ll judge it, usually two to four weeks later. That stops me from re-evaluating the same decision every morning.
3. The evidence column quotes a number and its source.
“Seems better” is not evidence.
“Bounce rate 63% → 50% the next day (Vercel)” is an observation I can verify, even if it doesn’t prove what caused the change.
The log also starts with a baseline: what the site looked like before any decisions were made.
Mine was £0.22 in Amazon fees for the month, 0 to 3 real Amazon clicks a day, and about 10 visitors a day.
Every later verdict is measured against that baseline and the relevant before-and-after data, not against how I feel about the website that week.
What the log caughtThree rows show why the effort was worth it.
1. The email gate I removed after four daysOn 10 October, I locked the site until visitors provided an email address.
The Why was simple: capture more emails.
The number to watch was signups compared with the number of people leaving at the gate.
Four days later, the row read:
- 3 signups
- 8 visitors leaving with the gate open
- 0 Amazon clicks
Verdict: Hurt.
I replaced the gate with a popup that visitors could close.
The next day, bounce rate fell from 63% to 50%, and page views increased by 88%.
That was encouraging, although one day’s improvement wasn’t enough to establish causation.
Without the log, I might have looked at “3 new subscribers” and kept the gate.
The row made me look at the cost alongside the gain.
2. The popup that was quietly blocking the real trafficBy mid-October, Google was sending 18 to 21 visitors a day, almost all to book guide pages.
The log showed that 0 out of 60 visitors clicked through to Amazon.
A logging change I had marked Enabler a week earlier helped explain why: 40 of 50 book-guide landings ended at the popup.
Most people closed it within 1 to 3 seconds and left the website 10 to 20 seconds later.
The fix was to stop showing the popup on the first page of a visit and to place a clear “See it on Amazon” button after the activities.
Over the next 30 days, the UK Amazon Associates report showed 40 clicks and the site’s first 3 orders.
That row is still marked Too early, because the sample is small, some clicks may be mine, and I can’t confidently attribute the improvement to those changes alone.
3. My own testing, twiceAmazon showed click spikes of 15 on 15 October and about 27 on 21 October.
Both looked like breakthroughs.
Both were me, testing links.
♦The lesson went into the log as a rule: test Amazon links without the affiliate tracking tag, and check every unusual spike against the tracking sheet that excludes my IP.
It’s a small rule, but it prevents me from mistaking my own activity for genuine growth.
What it changed about how I decideThe log has a summary at the top.
As of end-October:
- 5 decisions helped
- 3 decisions hurt
- Most of the rest were too early to judge
- None had yet produced a sale that I could confidently attribute to a specific decision
♦Writing that down is uncomfortable, and that’s the point.
It’s much harder to fool yourself when your own scoreboard is in front of you.
The log changed four things for me.
I ship smaller.
A change I can’t describe in one row is usually two changes. When I make several changes at once, it becomes harder to tell which one moved the number.
I decide what success looks like before I start.
The number to watch is chosen up front, not picked afterwards from whichever chart happens to go up.
I value measurement work.
The Enabler rows, including visit tracking, drop-off logging, and filtering out Google’s page checker, grew nothing directly.
Yet every verdict in the log depends on having trustworthy measurements.
I can reverse decisions without drama.
“Hurt” is a normal outcome, not a failure.
The email gate was gone in four days because the row made the reasoning for reversing it clear.
I built this alone, but the same log could work for a team, to help them understand the whys without having to ask anyone.
Why did we do this?
Did it work?
Who decided?
A new person could read 89 rows and understand much of the product’s decision history in an afternoon.
I because I was leading could see at a glance which bets are still open, when each will be judged, and which assumptions turned out to be wrong.
I think they’re just as useful for product and growth decisions, where the temptation to rewrite history can be even stronger.
Try itYou don’t need a special tool. A table in any document or spreadsheet works.
Start with these columns and fill in the first row before your next change goes live.
♦Then add three things at the top.
A baseline: What things look like today, with numbers and sources.
Your rules for evidence: How long you’ll wait, what you’ll exclude, and which sources you’ll trust.
A running summary: How many decisions helped, hurt, or are still open.
The website is still small, and the honest verdict on most of my recent work is still Too early.
But I know exactly what I’m waiting for, and when I’ll review it.
That’s what the log gives you.
Not better luck, but fewer stories you tell yourself.
Happy Chai and Decision making.
♦Using Software Architectural Decision Making for Product Engineering was originally published in Code Like A Girl on Medium, where people are continuing the conversation by highlighting and responding to this story.