The Feedback Loop: Why Measuring What You Change Actually Matters

You make a change. A new process, a new tool, a new page on the website, a different way of handling customer enquiries. Something that felt like the right call at the time. And then you move on to the next thing.

That's where most small businesses leave it. The change went in, nobody complained, so it must have worked. But did it? Did enquiries go up or down? Did the team find it easier or harder? Did the thing you were trying to fix actually get fixed, or did it just go quiet for a while?

Without measuring the result, you don't know. You're guessing. And when you're guessing, you're building everything that comes next on top of something you never confirmed was solid.

close the loop

A feedback loop is simple. You make a change, you measure what happened, and you decide what to do next. Did it work? Great, keep it. Did it half work? Adjust it. Did it make things worse? Roll it back and try something else. That's it.

The problem isn't that this is complicated. The problem is that most people skip step two. They make the change and assume. Assumptions compound. One untested change becomes the foundation for the next untested change, and before long you've got a process that nobody fully understands and everyone quietly works around.

the brief matters

You can't expect a team to deliver if you haven't given them a brief. That sounds obvious, but it happens constantly. A vague instruction goes out, the team interprets it however makes sense to them, and the result doesn't match what was expected. The feedback that follows is "that's not what I wanted" rather than "here's what I should have said more clearly."

A proper brief isn't a novel. It's clarity on what the outcome should look like, what success means, and how you'll know when you've got there. Without that, there's nothing to measure against. The feedback loop has nothing to close.

friction is information

When something feels clunky, slow, or awkward, that's data. When a customer asks a question your website should have answered, that's data. When your team keeps finding workarounds for a process you put in place, that's data. Friction tells you exactly where the path isn't smooth yet.

But you have to be looking for it. If you never go back and ask "did that actually work?", friction just becomes the new normal. People adapt to it, work around it, and stop mentioning it. The opportunity to fix it quietly disappears.

Every change you don't measure is a guess. Every guess that goes unchecked becomes an assumption. And assumptions are where things silently break.

make it a habit

You don't need dashboards and reports for this. You need the habit of going back. A week after a change, check in. A month later, check again. Ask the people doing the work whether it's better or worse. Look at the numbers if there are numbers to look at. If the answer is "it didn't help," that's not a failure. That's the loop working exactly as it should.

The businesses that run smoothly aren't the ones that get everything right first time. They're the ones that find out quickly when something isn't right and do something about it. That's the difference between carving out a frictionless path and hoping for the best.

I help small businesses get their IT and web presence running smoothly. If something's not working the way it should, let's have a chat.

→ get in touch → see what i do