Skip to main content

Pega Express delivery approach

Pega Platform™ applications drive and facilitate customer interactions. These interactions are referred to as customer journeys, which start when clients first hear about a product offering and continue throughout their relationship with Pega.

Pega Express is an agile approach that uses design thinking practices to capture the customer journey and quickly deliver a Minimum Lovable Product (MLP) release. With Pega Express, you break the customer journey into smaller pieces, called Microjourneys™, which drive the organization to achieve a specific goal. An MLP release is a value-added solution that addresses a business need or pain point and is a quick deliverable. The MLP release delivers a lovable solution that end users eagerly adopt.

Pega Express focuses on delivering one goal at a time rather than developing the entire customer journey at the start. To define an MLP release, you focus on three core elements, or pillars, of a great application: (1) Microjourneys, (2) Personas and Channels, and (3) data and interfaces.

Three pillars of an application

Microjourneys

A Microjourney is a small part of the overall customer journey and focuses on accomplishing a specific goal. For example, a customer wants to change their address. This scenario is a Microjourney that starts with the customer's request and results in an outcome where the customer address is updated in the company's records.

Note: To learn more about Microjourneys, see the Pega Academy topic Microjourney defined.

Personas and Channels

Personas determine who interacts with the application. Personas align the application user's specific needs with the desired business outcomes. Channels determine how a Persona interacts with the application. For example, a Persona is a customer or a company employee, and a Channel is a Web Portal or a chatbot. An application can have multiple Personas and multiple Channels.

Check your knowledge with the following interaction:

Data and interfaces

Data is the information that the Microjourney interacts with to accomplish the customer's goal, and the interface defines where the data comes from or where it is persisted. An application can interact with multiple types of data, and data can employ multiple interfaces.   

In the address change example, the customer's address is data, and the system in which the information resides is the interface. In the MLP release, this information might reside in Pega Platform as the system of record. However, in a subsequent release, the interface might change to another system where customer data is persisted. Using Pega Express, you capture data objects with their appropriate interfaces and align them to the appropriate MLP release.

Microjourney configuration

You configure Microjourneys in the Case Designer of App Studio. 

In the following image, click the + icons to learn more about the Case Designer's three-layer support:

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.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice