Being product-led isn't about delivering more. It's about making better decisions about what matters.

I've been reflecting on how often being product-led is misunderstood. It can be treated as a visible structural change: a new role, a roadmap, a different delivery rhythm or a set of ceremonies that show an organisation is "doing product". Those things can help, but they are not the shift that matters. The real test is whether product thinking improves the quality of decisions an organisation makes. That is the harder shift. And it is the one I think matters most.

From structure to decisions

At a UK Combined Authority, much of our work has been about helping a team move from a Target Operating Model on paper to something people can understand, use and shape in practice. The model gives the structure, but structure alone does not change outcomes. The more important question is how it changes everyday decisions: how priorities are set, how outcomes are defined and how learning flows back into strategy.

The same pattern appears across public services. Organisations rarely lack strategy, governance or plans. The challenge is keeping a clear connection between policy intent, operational reality, user need and delivery constraint. The further work moves from the original problem, the easier it is to focus on activity rather than outcomes.

The golden thread should not only run from strategy down into delivery. It should also allow learning from real services, operations and users to shape strategic choices over time.

In practice, the shift becomes real when the things around a team - communities, roadmaps, governance, funding and reusable assets - help people make good calls, not just coordinate more activity.

Making the work real

We see this in the work we are shaping with the combined authority via a Community of Practice. It is not just another meeting or governance forum. It is a practical space for people to build shared language, learn from live work and strengthen confidence in digital, product and delivery ways of working. The roadmap work serves a similar purpose. A roadmap is often treated as a plan of what will be delivered, but its real value lies in connecting intent to choices: what we know already, what we still need to learn, what should wait and what should stop.

Being product-led is not about saying yes to more work.

Sometimes it is about making the case to pause, reduce scope, change direction or stop. Not because people have failed, but because the evidence shows there is a better use of time, money or effort. For that to work, governance has to treat a well-evidenced decision to stop or reduce scope as responsible stewardship, not failed delivery.

One of the most useful questions leaders can ask is not simply whether work remains on track, but what teams have learned since the last decision was made. The answer should occasionally be uncomfortable.

Good evidence should challenge what we thought we knew. It should be able to change our minds. But evidence only matters if teams have the agency to act on it. If a team discovers the problem is different from what was assumed, can it adapt? If the evidence suggests a smaller intervention would achieve the same outcome, can scope be reduced? If learning shows the investment would be better directed elsewhere, can the work be stopped?

Those are product decisions as much as delivery decisions. Yet they are often where organisations find change most difficult.

Connecting evidence to outcomes

There is often a moment where a problem turns quickly into a proposed tool, process or platform. That is understandable: people want to make progress. They want to see a result. But the useful work often happens just before that point, when teams slow down enough to understand what is really happening now.

Product thinking and service design come together here. Product thinking gives focus on value, ownership, prioritisation and improvement. Service design keeps the wider journey, operational context and lived experience in view. Together, they move the conversation beyond "did we deliver the thing?" towards "is this improving the outcome?" In public services, that distinction matters.

A service can look successful on paper but still be difficult for people to use.

A project can deliver its agreed scope but still leave behind unresolved operational challenges.

A roadmap can be full but still not be focused on the things that will make the biggest difference.

Making learning reusable

Good evidence should occasionally make us uncomfortable. It should challenge what we thought we knew. It should be able to change our minds. But evidence only matters if teams have the agency to act on it.

The conversation about product-led working therefore has to include governance and decision rights. Teams need clarity about the outcome, the boundaries they are working within and the space they have to respond to what they learn.

This does not mean every decision moves to the team. It means people are clear about which calls they can make, which ones need escalation and what evidence is needed when a decision needs to change.

If the evidence shows something is not working, can the team change direction, make the bet smaller, recommend stopping or say “not yet”?

Those are product decisions as much as delivery decisions.

Across public service work, teams make better decisions when they can connect strategic intent to lived experience, service evidence and delivery constraints. The value is not in adopting product language for its own sake, but in creating repeatable habits that help people test assumptions and explain why a decision has changed.

When work stops, pauses or moves in a different direction, the important thing is understanding why: what changed, what evidence mattered and what should be preserved for the next team.

That is not just good handover. It is organisational learning.

It also changes how I think about playbooks, toolkits and reusable assets. Their job is not to standardise the answer. Their job is to give teams a stronger starting point: proven patterns, clearer prompts, practical governance, accessibility expectations and the lessons learned from previous work - while still leaving enough freedom to respond to the situation in front of them.

Making the shift stick

For Methods, this is where product, delivery and service design come together. The artefacts matter, but they are not the legacy. The legacy is whether the team carrying the work forward can make the next decision with more confidence: clearer outcomes, usable playbooks and live examples of decisions changing when the evidence changes.

That is why I increasingly think of product-led working as a question of organisational judgement. The roadmaps, communities, governance structures and delivery processes all have a role to play, but their value lies in whether they help people make better decisions over time.

Ultimately, the measure of success is not the roadmap, the community or the product role. It is whether an organisation becomes better at deciding what to start, what to stop, what to learn next and where to invest its effort - decisions grounded in what it knows, not what it hopes to be true. When that happens, product-led working moves beyond a way of organising teams and becomes a way of improving how an organisation decides.