Assessing the initial Blueprint

After shaping the initial Blueprint with business stakeholders and the Solution Builder, the Solution Designer assesses what the AI-generated design reveals about the emerging solution. The generated Case Types, Workflows, Data Objects, Personas, and integrations provide evidence that the team can examine before advancing into more detailed design.

Note: Upcoming modules will explore how to develop and assess fidelity in Case Types, Workflows, data, Personas, and integrations.

Reading what the Blueprint reveals

The AI-generated design may reveal useful patterns, relationships, and possibilities, as well as assumptions, missing information, or questions that require further examination.

The Solution Designer reviews the Blueprint for both what it contributes and what requires further attention:

Strengths: Elements and relationships that reflect the available business evidence and support the intended direction.
Useful suggestions: AI-generated possibilities that add value or help stakeholders consider an option that has not yet been discussed.
Assumptions: Plausible interpretations that require confirmation before the team relies on them.
Missing information: Business knowledge the available evidence does not yet provide.
Areas requiring attention: Elements that may need clarification, revision, stronger underlying evidence, or greater fidelity during later design work.

The presentation of the Blueprint can help stakeholders understand and examine the generated design, but presentation alone does not establish that its direction is appropriate. The Solution Designer considers what supports each generated element, discusses its significance with business stakeholders and the Solution Builder, and determines what should be examined more systematically.

Applying an assessment perspective

The Solution Designer considers several perspectives when assessing the initial Blueprint. The following perspectives help organize the review without prescribing a fixed sequence or replacing practitioner judgment:

Assessment perspective	Question to consider	What to examine
Business fidelity	Does the Blueprint reflect this business and its intended direction?	Business-specific operations, terminology, participants, constraints, and distinctive ways of working.
Outcome alignment	Does the emerging solution support the change required by the agreed outcome?	The relationship between the AI-generated design, the intended business change, and the initial journey selected for MLP 1.
Internal coherence	Do the major elements of the Blueprint relate to one another logically?	Connections among Case Types, Workflows, Personas, Data Objects, integrations, and the work they support.
Completeness against scope	Does the Blueprint represent the agreed scope and delivery focus?	Included capabilities, the initial journey for MLP 1, relevant dependencies, and the distinction between the current focus and deferred work.

An observation may relate to more than one assessment perspective and provides a starting point for examination rather than an automatic design defect. For example, a generated Persona that does not correspond to a known participant may raise a business-fidelity question. If the responsibilities of the Personas also do not connect logically to a Workflow, the observation may involve internal coherence.

The Solution Designer works with business stakeholders and the Solution Builder to establish the significance of the findings and determine whether it requires clarification, validation, revision, regeneration, or further attention during detailed design.

Determining what a finding requires

Once an observation warrants further attention, the Solution Designer determines what the resulting finding represents and what additional information or action it requires. Use the following table to consider an appropriate response to a finding in the initial Blueprint.

When a finding reflects	What to determine	Response to consider
Missing business information	Who holds the information, what decision depends on it, and whether the team can continue before it is established.	Clarify the information with the appropriate business or IT stakeholders before making the related design decision.
An unconfirmed assumption	How the assumption influences the emerging solution, who can validate it, and when confirmation is needed.	Record the assumption, assign ownership, and validate it with the appropriate stakeholders.
A focused issue in the Blueprint	Whether the issue is limited to one element and whether the surrounding design remains aligned with the available evidence.	Revise the affected area using the AI Assistant or manual editing tools, then review the change in relation to the surrounding design.
A broader issue with the underlying evidence	Whether a recurring pattern across the Blueprint can be traced to incomplete, unclear, or insufficiently specific application context or supporting assets.	Strengthen the underlying evidence and consider whether regeneration would provide a more useful starting point.
A need for additional design fidelity	Whether the initial direction is sound and what additional criteria are needed to develop or evaluate the affected Case Type, Workflow, Data Object, Persona, or integration.	Record the finding and carry it into the detailed design work where the appropriate criteria can be applied.

Consequential findings are best reviewed with business stakeholders and the Solution Builder in a hands-on working session using the Blueprint. The Solution Designer presents the observation, the supporting evidence, its potential significance, and a recommended response. The team can then examine the affected area, confirm what the finding represents, and agree on the next action. The Solution Designer records the finding, decision, owner, and any remaining open question in the Blueprint notes.

Determining readiness to advance

An initial Blueprint is ready to advance when the business is prepared to invest in the direction it represents. The Solution Designer considers whether:

The business recognizes and supports the intended direction represented in the Blueprint
The initial journey selected for MLP 1 addresses a challenge or experience the business is prepared to improve
The emerging solution supports the agreed outcome
The major elements relate coherently enough to support continued design
The agreed scope and delivery focus are represented appropriately
Consequential findings have an agreed response
Remaining assumptions, questions, owners, and next actions are recorded

Readiness is a shared judgment. The Solution Designer recommends whether the Blueprint provides a sound basis for continued design. Business stakeholders confirm their commitment to the intended direction and initial journey, while the Solution Builder considers whether the available information provides a practical foundation for the design and implementation work that follows.

A finding may remain open when its significance is visible and an appropriate response and owner have been established. Findings that affect the commitment of the business, the agreed outcome, the initial MLP focus, or the overall direction of the emerging solution require attention before the Blueprint advances.

Note: Readiness does not require every element to be fully developed or every open question to be resolved. It requires shared understanding of the challenge the business wants to address, the initial journey it intends to pursue, and what remains to be developed.

Scenario: Assessing the initial U+ Travel Blueprint

The Solution Designer assesses the initial Blueprint with Elena, other business stakeholders, and the Solution Builder. The team considers what the Blueprint reveals about the emerging solution and the Tour Booking journey selected for MLP 1.

Assessment finding	What it reveals	Recommended response
The initial journey supports the agreed outcome.	The Tour Booking journey provides a focused starting point for improving booking visibility and coordination while supporting growth.	Retain the direction and continue developing the journey.
The design elements work together to support the initial journey.	The relevant Case Type, Workflow, Personas, and business information are coherent enough to support continued design.	Preserve these relationships as the design gains fidelity.
Some operating details require additional fidelity.	The overall direction is sound, but some elements require further development and assessment during detailed design.	Record the findings and carry them into detailed design.

How would you respond?	The Tour Booking journey supports the agreed outcome and the major design elements are coherent enough to support continued work, but some operating details still require additional fidelity.

Would you recommend advancing the Blueprint, revising a focused area, or strengthening the underlying evidence before continuing?

Which findings must be addressed now, and which can be carried into detailed design?

What response, owner, and open question should be recorded for each unresolved finding?

Based on the assessment, the Solution Designer recommends advancing the Blueprint:

The initial Blueprint provides a sound basis for continued design. U+ Travel supports the direction and is prepared to invest in developing the Tour Booking journey for MLP 1. Some operating details and assumptions will require further attention as the design gains fidelity.

The remaining findings can be addressed within the current design because the business evidence and overall solution direction remain sound. The Solution Designer records each finding, the agreed response, its owner, and any remaining questions in the Blueprint Notes for continued work with business stakeholders and the Solution Builder.

In practice

The following practices help the Solution Designer assess an initial Blueprint, respond to findings, and determine whether it provides a sound basis for continued design.

Practice	Why it matters	Questions to ask
Read what the Blueprint reveals	The generated design can contribute useful possibilities while also surfacing assumptions, missing information, and areas requiring attention.	“What does the Blueprint contribute?” “What should the team examine further?”
Apply relevant assessment perspectives	Business fidelity, outcome alignment, internal coherence, and completeness against scope help the team examine an observation without replacing practitioner judgment.	“Which perspectives help us understand the significance of this observation?”
Determine what each finding requires	The source of the findings and significance shape the response and identify who should participate in the decision.	“What does this finding represent?” “Who should evaluate it?” “What response is appropriate?”
Establish readiness to advance	The Blueprint can advance when the direction is sound, the business is prepared to invest in it, and remaining findings have agreed responses and owners.	“Does the Blueprint provide a sound basis for continued design?” “Are we prepared to advance this direction?”

From initial Blueprint to detailed design

The initial Blueprint establishes the solution direction the team is prepared to advance. It reflects the available business evidence, supports the agreed outcome, focuses the initial journey for MLP 1, and makes remaining assumptions, questions, and design needs visible.

The Blueprint now provides the foundation for more detailed design. The Solution Designer continues working with business stakeholders and the Solution Builder to develop greater fidelity in the Case Types, Workflows, data, Personas, and integrations. Throughout that work, the team evaluates the design against the established business direction, agreed outcome, and decisions.

This Topic is available in the following Module:

Creating the initial Blueprint v1

Get help

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Yes

Want to help us improve this content?

Suggest an edit