Identifying and setting key strategic business outcomes for your Pega application provides the direction for your transformation program, to ensure that all increments contribute to achieving the needs of your business and customers.

What are business outcomes?

Business outcomes are key, high-value business objectives that an application built with Pega Platform™ is designed to achieve. These outcomes are most likely tied to a company's strategic objectives and are heavily influenced by what customers experience and feel as they interact with the organization. Business outcomes might include, for example: 

• a new sales objective, 

• a customer retention objective, 

• an efficiency objective. 

The key performance indicators linked to a business outcome are the measures used by the business to track and analyze their performance towards achieving their objectives and outcomes. 

Why do Business Outcomes add value?

Business outcomes are the driving force that keep businesses focused on investing time, money, and effort on the right projects and operational activities to ensure growth and stability. Outcomes are also the guiding lights for directing your investment into solutions that deliver real value and ensure that your projects are focused on: 

• processes and functions that require improvement, 

• high-priority Microjourneys® that make a measurable difference, 

• applications that are directly aligned with company goals. 

When are Business Outcomes identified?

The concept of Business Outcomes and Key Performance Indicators are applicable throughout the Pega Express™ delivery approach, including at the following points: 

• During the initiation of a project, to help determine the right solutions to target and create a roadmap of Minimum Lovable Product releases.
• Before work starts, to help set expectations of the application about what 'good' looks like.
• During the design phase, when prioritizing features and attributes to ensure that they contribute to the business outcomes.
• During configuration, to ensure that the most valuable user stories are prioritized and implemented.
• After implementation, to ensure that the application has achieved what it set out to achieve at the beginning.