Defining and agreeing upon business outcomes
Defining an outcome turns the business’s intended change into a specific and measurable standard for the design. The Solution Designer evaluates stakeholder perspectives, establishes how progress will be measured, and builds agreement around the outcome that will guide the engagement.
What makes an outcome an outcome
Stakeholders describe outcomes in different ways. A Solution Designer recognizes three common patterns and determines what each statement still needs before it can guide the design:
Each statement provides useful insight into what matters to the stakeholder, but additional detail is needed before it can guide the design. A measurable outcome describes a specific change the business will recognize, one that can be measured and that has a clear beneficiary.
Note: An outcome that is measurable and agreed gives the business and the Solution Designer a shared standard for evaluating the design.
The anatomy of a measurable outcome
As illustrated in the figure below, a measurable outcome carries four components: what changes, for whom, by how much, and by when. Together, these components clarify the change the business wants to achieve and provide a shared standard for evaluating the design decisions that follow.
Tip: “Does this decision improve the likelihood of achieving the agreed outcome?” is a question the Solution Designer can apply to design choices from Blueprinting through Value Activation. A specific and measurable outcome provides the shared standard needed to answer it.
Establishing the baseline
A measurable outcome needs a clearly understood starting point. For example, a target of 30 percent booking growth can only be evaluated when the current booking volume is known and agreed. The baseline establishes that starting point and gives the business and the Solution Designer a shared reference for measuring progress.
Two practices make the baseline useful throughout the engagement:
- Establish the baseline using data from the business. Confirm the current measure with the stakeholders who own or use the data. If the current state is not yet clear, record it as an open item and identify who will establish the baseline before the outcome is finalized.
- Confirm the measurement mechanism. Document how the baseline was calculated and how the outcome will be evaluated later. For example, a booking-volume measure that excludes weather-canceled excursions may be appropriate for one purpose but not another. Using the same measurement approach for the baseline and the outcome allows the business to evaluate progress consistently.
Building and maintaining agreement
Different stakeholders may define success based on their responsibilities and perspectives. The following table shows how the Solution Designer helps make those perspectives visible, establish which outcome will guide the design, and maintain that agreement as the engagement progresses:
| Focus areas | What the Solution Designer does |
|---|---|
| Surface stakeholder perspectives | Ask stakeholders to describe what success looks like from their perspective, even when the group appears to agree. |
| Identify alignment and differences | Clarify where stakeholder priorities complement one another and where further discussion or a decision is needed. |
| Confirm the guiding outcome | Work with stakeholders to agree on a specific outcome, baseline, and measurement mechanism, with the executive sponsor resolving priorities that cannot be fully reconciled. |
| Use the outcome to guide decisions | Keep the outcome connected to the Blueprint and use it to evaluate proposed scope additions, delivery tradeoffs, and new stakeholder perspectives by asking how each may affect the likelihood of achieving the agreed outcome. |
| Maintain agreement as understanding develops | Confirm material changes with the sponsor and update the outcome, baseline, or measurement mechanism when new information supports a change. |
An agreed outcome provides a consistent reference point, but it can evolve as understanding develops. Keeping it connected to the Blueprint helps stakeholders distinguish between changes that support the intended outcome and changes that could redirect the design and scope.
Scenario: Developing an agreed outcome for U+ Travel
The Solution Designer returns to the candidate outcome for U+ Travel (30 percent booking growth without adding operators) and works with Elena and her regional director to develop it through the four components shown below:
| Component | As agreed for U+ Travel |
|---|---|
| What changes | Operators manage bookings through a shared operational view rather than personal spreadsheets, phone messages, and text threads. The shared view coordinates booking information across operators and reduces the manual reconciliation required. |
| For whom | Elena, her 15 operators, and U+ Travel's booking customers benefit from improved coordination and fewer reconciliation errors. |
| By how much | Elena proposed 30 percent booking growth without adding operators. Through discussion with her regional director, the agreed target becomes 25 percent growth in year one and a further 15 percent in year two, with reconciliation errors reduced from 11 per week to fewer than two. |
| By when | The year-one target will be evaluated after the following peak season. The baseline will be established at the end of the current peak season, using the same measurement approach that will be used to evaluate progress. |
The agreed outcome builds on what Elena described during discovery. Her initial growth target has been evaluated alongside the regional director’s perspective, while the reduction in reconciliation errors provides an operational measure connected to Elena’s experience.
The result is an outcome that is specific, measurable, supported by the sponsor, and grounded in a shared baseline.
Note: An outcome supported by stakeholder agreement, sponsorship, a baseline, and a consistent measurement mechanism provides a practical standard for guiding the design through Authoring.
In practice
Compare your approach to the practices below for defining and agreeing on business outcomes:
| Practice | Why it matters | Questions to ask |
|---|---|---|
| Develop aspirations into measurable outcomes | An outcome must define what will change, for whom, by how much, and by when before it can guide the design. |
What will be true a year from now that is not true today? Who will notice the change, and how will they notice it? When should the business expect to evaluate the outcome? |
| Establish the baseline and measurement mechanism | An outcome without a baseline is unverifiable. A consistent measurement mechanism allows the business to evaluate progress reliably. |
What measure describes the current state? How will we use that same measure to evaluate the outcome? |
| Test whether the target represents meaningful success | A meaningful target distinguishes an agreed commitment from an initial ambition. | If we achieved half of the improvement you described, how would the business evaluate that result? |
| Build stakeholder and sponsor agreement | Group agreement can mask different interpretations of success. An outcome the sponsor has not confirmed may be reopened later. |
What does success look like from your perspective? Who else needs to support this outcome for the business to consider it agreed? |
| Keep the outcome connected to the Blueprint | Documenting the outcome, baseline, measurement mechanism, and sponsorship alongside the Blueprint keeps the full agreement visible as the design develops. | How would this proposed change affect the likelihood of achieving the agreed outcome? |
The agreed outcome establishes the destination; scope determines what the first release must include to move toward it.
Knowledge check
Check your knowledge with the following interaction.
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?