What makes a good outcome?

A well-crafted outcome doesn’t just define success; it creates the conditions for it. This post describes outcomes that drive clarity, alignment, and energy across your organisation.

“Outcome (noun): an outcome succinctly describes a desired change or impact”

In the world of digital and organisational change, being able to define and communicate a strong outcome is a leadership superpower. Whether you’re working on a product, service, or internal shift, a well-crafted outcome sets direction, aligns teams, and builds momentum. Here’s how to make your outcomes truly effective:

What makes an outcome “good”?

  1. Describes the desired change, not the solution. You don’t need to have the answer upfront. Instead, focus on the future state you want to see. Trust your teams to figure out the best path. Example: “Fewer debtors, in less debt, for less time” describes the change, not how to get there.

  2. Memorable and emotive. Embrace your inner tabloid journalist. Outcomes should be easy to recall and connect with emotionally. They should rally your team around a shared purpose. “Save £3m” is forgettable. “Give time back to colleagues” is relatable and motivating.

  3. Helps to tell the story of the work. If your outcome becomes the phrase people repeat to explain what the team is doing, you’re on the right track. Good outcomes explain the “why?” and should stand the test of time as your product, service or change initiative evolves.

  4. Enables everyday prioritisation - You've hit the sweet spot when a team can use the outcome to guide their next steps without a spreadsheet, framework, or approval. “Does this change give more time back to colleagues than the alternative?” That’s real-time prioritisation.

  5. Builds alignment across teams. Strong outcomes act like organisational glue. They align diverse teams across silos and reduce the need for constant coordination and reporting. If your product, service or platform has multiple outcomes statements or you're stuck in a soup of OKR’s — simplify! You can always break things down later. When everyone works toward the same outcome, leadership becomes lighter and more distributed.

  6. Looks far enough into the future. Aspirational outcomes keep teams motivated over time. Even if they’re never entirely “done,” they provide a north star for continuous improvement.

If you want to drive clarity, alignment, and energy across your organisation, lead with outcomes.

Real-world examples

  • Simpler, clearer, faster access to government information and services” GOV.UK, Government Digital Service

  • Fewer debtors, in less debt, for less time Welsh Revenue Authority, Debt Team

  • Planning data that is easy to use and trust Ministry of Housing, Communities and Local Government

  • “More people, in more work, more of the time, while supporting those who can’t work” Department for Work and Pensions, Universal Credit

  • Improve a claimant’s employment prospects so they can move towards financial independence from the state Department for Work and Pensions, Universal Credit Jobs

Tips for writing great outcomes

  • Start with verbs: e.g., “Reduce…”, “Improve…”, “Make…”

  • Avoid metrics at first: Focus on meaning, then add targets later.

  • Make it human: Frame the benefit for users, customers, or colleagues.

  • Test memorability: If people can’t remember it tomorrow, it’s too complex.

  • Outcomes come in many forms. They may be part of goal statements or objectives, or form part of a mission or vision statement. However you wrap them up, less is more. John Cutler’s Mandate Levels is mandatory reading!

  • Struggling to uncover the actual outcome of something? Try asking Emily Webber’s five questions (Miro template). It’s magic.


Five questions to measure outcomes

I co-created a workshop with the wonderful Emily Webber called Five Questions to Measure Outcomes. It’s a tool for teams and leaders wanting to describe and measure outcomes.

5 years ago I was running a workshop and struggling to get the participants to describe the desired impact of their work. Everything we wrote on our post-its came out as a solution (a feature or a thing delivered) and try as we might, we couldn’t get past this.

Emily popped some questions on the wall to help shift our brains into outcome-oriented thinking. They really worked, and I’ve been using them ever since. We’ve put them into a template and created a little workflow to help teams find the keywords and phrases that describe the impact and value of their products, services, projects and programmes.

It’s a simple exercise which you could use to set or recalibrate direction.  You could use it as part of your kick-off or part of your strategic planning rhythms.  Give it a go.

Benefits of working in the open


Working in the open is scary at first but then feels liberating. Publishing our team’s website and data landscape felt like a big deal at the time. Should the Welsh Revenue Authority be talking about land and property platforms? Will people outside the team understand why we’re doing this work?

And then people started to notice and say nice things.

It’s lovely to have plaudits but there are other benefits to working in the open.

Working in the open…

Improves alignment

We thought we were sure from the outset about our objectives and why we were doing the work but it turns out the jeopardy of making things public forced us to clarify these before we published. Everyone in and around the team is more aligned and clearer.

Reduces collective anxiety

Once we were out in the open you could feel the weight fall from our collective shoulders. It was safe to talk and collaborate with others from outside the organisation. Focus shifts to the work, rather than crafting the message.

Tests empowerment

There’s lots of organisations that say they trust you and ask you to bring yourself to work, but do they? When an organisation encourages a team to work in the open, they demonstrate that they trust you.

A fabulous calling card

The more we opened up, the more people turned up to the Show & Tell to ask us some good questions; People outside of the organisation have put their hands up to collaborate or offer advice; It is helping us hire a fantastic team.

The thing is, we don’t know who we don’t know. By being out there people can find us and help us join the dots. To give you a good example, we discovered that a team in the Netherlands is working on something similar. This would not have happened had discussions been limited to internal meetings and closed email distribution lists.

Allows others to build on existing work

We document our work and thinking on GitHub. It’s a public history of the work and our thinking. We have built on other people’s fantastic work and we hope others might take what we’ve done and build on it too. By working in the open the institutional knowledge doesn’t get lost or forgotten on an internal file system.

This way of working is, in many ways, familiar to WRA. The level of trust and tone of voice are already established aspects of the culture but it is not the norm for teams to share weeknotes and thinking-out-loud in the same way we have with this project. We can say it has honestly helped us and made it more enjoyable. We hope others give it a try.


This post was originally published on the Land and Property team’s website.

Ice cream sketch

I did a sketch for Public Digital’s Signals to help illustrate an article written by Heath Arensen on digital public goods.

The park is a metaphor for government investment; the ice cream store for a thriving eco-system of organisations that deliver additional public good (tasty treats for park visitors). It’s Heath’s metaphor, but I enjoyed thinking about it and sketching.

Sign up for copy and get a lovely Signals through the post.