Skip to main content


Updated on August 6, 2020

At Pega, we apply design thinking techniques to our low-code applications using industry standard practices. The Pega approach is light, quick and guides the team to create applications from the simple to the sophisticated. Every situation is different and the approach to design can vary. During Discover you will have determined whether your project requires a Design Sprint, a shorter series of Ideation workshops or the problem is simple and defined well enough to go straight to DCO workshops.

A Design Sprint is a five-day design thinking process for answering critical business questions through design, prototyping, and testing ideas with customers. Design Thinking techniques help organizations:

-           Quickly frame a problem space and identify opportunities

-           Ideate and innovate solution approaches

-           Select the best approach to pursue

-           Prototype and test a solution

In this context a prototype is not a technical prototype; it needs to be something that enables a scenario to be tested with end users. This is not testing in the traditional software delivery sense. End users will validate a concept and give the team valuable insight into the end user experience, pre-build.

Designing the User Experience (UX) is also a critical activity to help achieve outcomes and adoption. The Pega Cosmos design system provides a Design System that leverages Pega out‑of‑the‑box experiences, promoting consistency and reuse. Using design templates, Pega allows UX designers to define, add, and govern standards throughout the delivery process.

During Prepare, you will also define the enterprise architecture and create your Stages and Steps model for each case type, within Pega. You will use what you have learned about the solution in preparation for DCO sessions. The objective during Prepare DCO sessions is to draft your MLP1 case types, personas and draft data objects, then gain approval from the Product Owner to ensure the application design is going in the right direction.

What happens next? Now that you have designed your solution, it’s time to create your backlog and elaborate/approve user stories in preparation for Sprint 1.

The related content links below provide methods and tools to help you.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us