Blueprint overview
Pega Blueprint™ is an AI-driven design environment that transforms initial discovery into a structured model, with workflows, Personas, Data Objects, and decision points, all shaped in real time during discussion.
Blueprint bridges conversation and construction, turning stakeholder business problem descriptions into buildable solution designs.
When a Solution Designer creates a new blueprint, they don’t start from zero - every blueprint benefits from a comprehensive foundation of industry knowledge, best practices, and standards. Blueprint uses Pega's built-in industry templates and deep industry expertise to provide a draft model tailored to common workflows, Case Types, and Data Objects for that sector. The designer then enriches this starting point by incorporating assets, documents, and knowledge that are unique to the client organization. This collaborative process produces a draft design that combines best practices from the industry with the client's specific needs, and serves as the launchpad for further conversation and refinement, rather than the final product.
To access Blueprint, click the Dashboard link below:
| Marketing |
|---|
| Pega Customer Engagement Blueprint™ |
| Customer Engagement Blueprint dashboard |
The following video provides an overview and demonstration of the Pega Customer Engagement Blueprint.
| Operations and Customer Service |
|---|
| Pega Blueprint™ |
| Pega Blueprint dashboard |
|
|
Significance and implications
Historically, every enterprise delivery project contains a gap between what was agreed in a discovery conversation and what was actually built. Business intent is expressed in natural language; delivery happens in structured systems. At every translation point between the two - from conversation to document, from document to requirement, from requirement to code - fidelity degrades. By the time stakeholders review what was built, the original intent is frequently unrecognizable.
When a Solution Designer and stakeholders work through a problem in Blueprint, the design emerges from that discussion in real time. There is no separate document to write, no requirement set to maintain, and no translation layer to manage.
The process explained
Blueprint's design environment is structured around inputs that it ingests, along with synthesizing the client's own documents. Existing process maps, policy briefs, annual reports, and marketing materials, alongside Pega's enterprise delivery experience, partner ecosystem knowledge, and the broader knowledge available through large language models are all used by Blueprint's AI layer to analyze all of this information and design a solution.
Tip: The Solution Designer's role is to look at what Blueprint has generated and ask stakeholders, 'Does this reflect what actually happens today, or what you wish would happen?' The conversation moves through refinement from that point, giving stakeholders direct experience of what will be built from the very beginning. By doing this, issues are addressed early on, helping to mitigate potential rework later on.
What occurs in the Refinement phase differs a bit, depending on whether Pega Blueprint is being used, or Pega Customer Engagement Blueprint. Refinement in Pega Blueprint (for operations and Customer Service areas), involves work such as adding and removing Steps, naming data relationships, establishing the beginnings of decision logic, and assigning Personas to workflow stages. During Refinement for marketing in Customer Engagement Blueprint, items such as Personas can be modified or added, and brand voice and visual identity confirmed.
How Pega stands out
Before Blueprint, reimagining a business process required producing a series of intermediate artifacts - discovery notes, process diagrams, requirement documents, backlog items - each of which was adjacent to the development environment, rather than connected to it. Reimagination happened on whiteboards and in workshops, and then had to be reconstructed from scratch.
Blueprint makes reimagination an act of construction. The moment that stakeholders agree that a workflow in Blueprint reflects how their process should work, that agreement is encoded in a model that can be imported into Pega Infinity™, built, and run.
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?