How to Define a Project Outcome Before You Start a Project: A 5-Step Guide for Project Managers
Start With the Outcome, Not the Plan
Most project plans begin with tasks, dates and resources. Far fewer begin with a clear statement of what will be different when the project is finished.
That gap causes problems later. When the outcome is vague, people interpret it in different ways, scope grows to fill the space, and progress is reported as activity rather than result. A project can deliver everything in its plan and still fail to achieve what the organisation wanted.
Defining the outcome before you start gives you something to test every decision against. This guide explains what a project outcome is, a five-step method for defining one, a worked example and the mistakes to avoid. If your project is already approved, the same method works as a check before your kickoff. The Project Kickoff guide covers what happens next.
Outputs, Outcomes and Benefits
Three terms are often used as if they mean the same thing. They do not, and the difference is the starting point for a clear outcome.
Output: what the project produces, such as a new system, process, product or report.
Outcome: what changes because the output exists, such as faster processing, fewer errors or better customer service.
Benefit: the measurable value created by that change, such as cost saved, revenue gained or risk reduced.
A project outcome is the middle of those three. If you can only describe what the project will deliver, you have a list of outputs. If you can only describe the financial result, you have a benefit with no explanation of how it will be achieved. The outcome connects the two and tells everyone what the project is really for.
A Five-Step Method for Defining the Outcome
Work through these steps in order. Each one produces a short written statement that you can share and test.
Name the problem or opportunity. Write one or two sentences on what is wrong or what could be better today. Say who is affected and what it currently costs them in time, money, quality or risk.
Describe the change in plain terms. Complete this sentence: "When this project is finished, [who] will be able to [do what], which means [what changes]." If the sentence only names something the project builds, go back and describe the change instead.
Make it measurable. Choose one to three measures. For each one, record where it stands now, the target and the date by which you expect to reach it. Without a starting point, nobody can show that anything improved.
State what is out of scope. Write down what the outcome does not include. Doing this early brings hidden expectations into the open while they are still easy to discuss.
Confirm it in writing. Share the statement with the Project Sponsor and key stakeholders and ask for agreement or corrections. A disagreement found now costs far less than one found during delivery.
Before you move on, test the statement with four questions:
Could two people read it and picture the same result?
Does it describe a change rather than a deliverable?
Can you tell, with evidence, whether it has been achieved?
Has the person who owns the benefit agreed to it?
Worked Example: Replacing a Customer Records System
The table below compares a typical first draft with an outcome defined using the five steps. The figures are illustrative.
Element | First draft | Defined outcome |
Problem | Our customer system is old. | Staff spend an average of 6 minutes per enquiry searching across three systems for customer details, and complaints about repeated questions are rising. |
Outcome statement | Implement a new customer records system. | Customer service staff will see a full customer history on one screen, so customers do not have to repeat themselves. |
Measures | Go live by June. | Search time per enquiry falls from 6 minutes to 2 minutes by December, and repeat-contact complaints fall by 30% within six months of go-live. |
Out of scope | Not stated. | Marketing data migration and changes to the billing system. |
Agreed by | The Project Manager only. | The Project Sponsor and the Head of Customer Service, in writing. |
The first draft describes an output. The defined version tells the team what must improve, how much, by when, and what the project is not responsible for. Every later decision about features, suppliers or timing can be tested against it.
Common Mistakes When Defining a Project Outcome
Describing the deliverable instead of the change. "Launch a new website" is an output. What visitors will be able to do, and what that changes for the organisation, is the outcome.
Using vague words without a measure. Words such as improve, enhance and streamline mean different things to different people. Attach a number and a date.
Defining the outcome alone. An outcome written only by the Project Manager is a proposal. It needs the Sponsor and the people who own the benefit.
Setting too many outcomes. A project with seven outcomes has no priorities. Aim for one primary outcome and no more than two supporting ones.
Treating the outcome as fixed forever. If the business case or the context changes, revisit the outcome at your next stage gate and agree any changes openly.
If your project has already stalled because nobody can agree what it was meant to achieve, the Project Recovery Strategies guide explains how to restore clarity.
Put It Into Practice
Once you have written your outcome statement, give it a home where the whole team can see it. A one-page plan is a good place, because it keeps the purpose beside the timeline, risks and decisions.
Get your free Project Plan on a Page template from the Resource Library. Record your outcome statement in its Business Outcome section and your measures in its Success Measures section, so the reason for the project sits beside the plan for delivering it. Sign up once and you will receive every free template by email. For guidance on completing the template, read the Project Plan on a Page guide.
Final Thought for Project Professionals
A project that delivers on time and on budget has still failed if it did not change what it was meant to change. Define the outcome first, write it down, measure it and agree it with the people who matter.
Lead with clarity. Deliver with confidence.
Comments