Ship the small things

Big product wins don’t only come from big launches.

Some of the most meaningful progress happens when teams consistently ship the smaller things. Minor improvements, long standing annoyances, and small fixes that make someone’s day just a little easier.

I’ve always believed that, over time, those small changes will compound. They’ll quietly improve customer trust and help signal that even if you can’t always prioritise their requests, that we are still paying attention. It shows memory. It shows that we care.

So how do you prioritise?

Big roadmap items should never consume 100% of a team’s capacity. When they do, small improvements either stall completely or end up disrupting the main work anyway. Protecting some capacity for small improvements helps both move faster.

For example, if you run a support rota, the on-support engineer can be well placed to focus on these smaller updates. Keeping them out of headline project work reduces context switching and allows reactive time to turn into tangible progress.

Ensuring you hold regular backlog reviews alongside your sprint planning also helps. Not everything needs to justify a roadmap slot, but smaller tasks still deserve intentional prioritisation.

Do a few small things every sprint and you quickly build a backlog of meaningful updates that genuinely delight customers. Individually they are small. Together, they say a lot about how you build.

We’ve recently started running this approach at Transpond, led by Jade and myself. It’s still early, but we’re already seeing the value of consistently making space for smaller improvements. We’ll keep iterating on the process, but so far it’s been a very positive shift.

Shipping small things consistently is not a distraction from strategy. Done well, it is part of it.