Microjourney documentation

In the Pega Express^™ delivery approach, the key building blocks, known as the three pillars of an application, include:

1. Microjourneys^™, cases, and strategies 
2. Personas and channels
3. Data and interfaces

Every Pega Platform^™ application is built on the three pillars, as shown in the following image.

Describing a Microjourney in the context of the three pillars ensures that project team members work through all of the key dependencies (such as integrations) before the project starts. That helps uncover any major roadblocks. Take a look at each of the three pillars and how they work.

Microjourneys, cases, and strategies

This pillar:

• Identifies the Microjourney that the Pega Platform application can configure
• Documents the overall journey for the customer that achieves all or a subset of their business outcomes
• Can be delivered as a solution in 60-90 days or less
• May be achieved by one or more case types in Pega Platform

Personas and channels

This pillar:

• Establishes the different user groups, roles, and personas, who will interact with the Microjourney (for example, an end customer and a call center agent)
• Identifies which channels the Microjourney touches, for example, mobile, web, or call center

Data and interfaces

This pillar:

• Identifies the data required to support the Microjourney
• Notes the sources of that data

These three pillars form the foundation of a Pega Platform application. Once the Microjourneys are identified, the next step is to capture key information for each Microjourney. 

Defining the three pillars allows you to articulate what the "to be" Microjourney is and what the solution may look like from a business perspective. By documenting the three pillars, the Pega Express project delivery team can pick up, interpret, and consider solutions. With this level of detail included, the Microjourney results in a higher quality definition of the scope to be delivered during the remainder of the project. 

Once the key building blocks of the application are clearly defined, your team can estimate the work effort so you know how quickly you can go live.

Using the Pega Express approach, you have two options for capturing information about each Microjourney. 

1. Using Pega application version 8.4 and above, you can directly capture the three pillars within Pega App Studio. 
2. Alternatively, you can capture key information in an estimation tool, called the Case Type Backlog.

The Case Type Backlog and other tools to support your Microjourney are available on the Pega Express Delivery Resources page.

With Pega version 8.4 and above, you can capture the three pillars directly into App Studio. For additional information on Pega App Studio, review the Pega Academy topic App Studio benefits. See the following image as an example:

If you are not yet using Pega version 8.4 or higher, you can capture the three pillars directly in the Case Type Backlog tool. The Case Type Backlog tool is Excel-based and can be found in the Prepare section of the Pega Express Delivery Resources page. 

Use the following steps to populate your Case Type Backlog:

Prepopulated Case Type Backlogs are available for Pega's Strategic Applications. You can use these and tailor them to your project. Ask your Pega representative for a copy.

Check your knowledge with the following interaction.