Introduction

If you have worked in product for any length of time, you will know the feeling. Release day is on the horizon. The team gathers. Everyone waits to see what is ready, what is almost there, and what is still somewhere in build.

It has all the energy of Christmas morning, complete with surprises, mixed emotions, and the hope that at least some of the presents match what you were expecting. Some features are the perfect gifts. They arrive on time, neatly wrapped, and they work exactly as planned. These are the moments every product manager looks forward to. They show the impact of strong planning, solid teamwork, and clear understanding of customer needs.

Some features feel more like the slightly dented presents. Still valuable and full of potential, but not quite ready to be enjoyed. The decision is whether to unwrap them now or save them and improve them for the next release cycle (even if it might be a year away!)

And of course, there are the presents that never made it under the tree. Features that were planned but fell by the wayside. Ideas that needed more refinement. Work that was simply not ready for prime time. None of this is unusual. It is simply the reality of building products in fast moving environments.

This is exactly why strong feature prioritisation matters. When you know that not everything will be ready, you need a clear way to decide what should make it into the release and what can safely wait. If you want some practical methods for doing this well, take a look at our guide to six ways to prioritise user stories.

Release day will always bring a mix of delight, tough choices, and the unexpected. The goal is to stay focused on value, manage surprises with confidence, and help your team deliver work they can be proud of.

Here’s Louise to break this down…