Collaboration in Blueprint

Effective Blueprinting begins with discovery - understanding business context, goals, and challenges through walkthroughs, interviews, and screenshares. This ensures that co-creation sessions are focused, relevant, and productive.

Collaboration means designing with your stakeholders, in Blueprint, in real time. Rather than circulating decks, you’ll co-capture the problem in business terms, create initial case types, tune stages and steps, and add essential data objects and personas. The session ends with a first-pass Blueprint that everyone can see, discuss, and improve.

How does Blueprint work?

In the following video, learn how to translate goals into build-ready designs by defining case types, stages, steps, data objects, and personas, then exporting the Blueprint to kickstart delivery:

To watch the video on Pega.com, see How does Blueprint work? | Pega

Why: Faster alignment, better decisions

When teams cocreate, they align faster, confront assumptions earlier, and leave with decisions instead of notes. Blueprint’s shared, clickable artifacts replace long document cycles and give you portable outputs (PDF and other formats) that keep strategy and delivery connected. Collaboration builds the trust and momentum that Solution Designers use to move from intent to evidence.

Key Stakeholder Roles in a Blueprint Workshop

Successful Blueprint workshops depend on clear alignment across business and technical perspectives. Each stakeholder brings unique authority, insights, and responsibilities that shape the quality and completeness of the solution. The table below outlines the primary roles, their contributions during the workshop, and the differentiators that make their involvement critical for driving transformation and ensuring enterprise-grade outcomes:

Business Sponsor	Ops Manager	BA/SME	IT
VP level or above Buying Authority Blueprint Approver Workshop Role Define business value Prioritize MLPs or features needed Provides definition of “good” or “done” Expresses what needs to be true to move forward	Voice of the Do-ers Workshop Role Provide feedback based on real-world experience Give logistical details to ensure Blueprint completeness Bubble up areas of opportunity for improvements or potential sticking points that may be unknown to management	Overlay between operations teams and technical teams Workshop Role Provides detailed process insights that include business and technical processes Translates requirements to Pega from business and IT stakeholders	Tech Team supporting the business unit Workshop Role Provide details about data availability or restrictions Surface potential sticking points or opportunities from a technical perspective Provide technical sign-off on approach and ability to fold Pega into existing ecosystem

Business Sponsor

Ops Manager

BA/SME

VP level or above
Buying Authority
Blueprint Approver

Workshop Role

Define business value
Prioritize MLPs or features needed
Provides definition of “good” or “done”
Expresses what needs to be true to move forward

Voice of the Do-ers

Workshop Role

Provide feedback based on real-world experience
Give logistical details to ensure Blueprint completeness
Bubble up areas of opportunity for improvements or potential sticking points that may be unknown to management

Overlay between operations teams and technical teams

Workshop Role

Provides detailed process insights that include business and technical processes
Translates requirements to Pega from business and IT stakeholders

Tech Team supporting the business unit

Workshop Role

Provide details about data availability or restrictions
Surface potential sticking points or opportunities from a technical perspective
Provide technical sign-off on approach and ability to fold Pega into existing ecosystem

How: Run a collaborative session

Once you’ve set the stage and explained why collaboration matters, it’s time to put it into practice. These steps guide you through running a hands‑on Blueprint session that turns ideas into a shared, tangible design.

Prepare the room
- Invite the business, IT, and operations stakeholders who own the outcomes.
- Clarify the use case and what “good” looks like for this session (for example, first-pass Blueprint + list of open questions).
Open with shared intent
- Frame the session as co-creation: “Let’s capture goals in your words and watch them take shape in Blueprint.”
- Establish facilitation norms (short turns, capture decisions in the tool, park deep dives).
Cocreate in the tool
- In Blueprint, set Industry / Function / Application purpose.
- Add/adjust case types; refine lifecycles (rename stages, insert steps, convert manual steps to Automations where appropriate).
- Add data objects and personas as they emerge from the discussion.
Ground with real inputs
- Gather relevant materials, such as SOPs, compliance rules, screenshots, and data definitions from internal sources and websites, then import them into Blueprint to improve design quality.
Close with tangible outputs
- Share the PDF of the first-pass Blueprint for broader review.
- Record owner-tagged next steps (what to validate, which assets to add, who else to include), and schedule the fidelity session.

In the following table, review the type of information you need for each screen in Blueprint:

Screen	Ask…
1 – Application Context	About their automation priorities What are your top automation priorities? What business problems or pain points are you aiming to solve? What outcomes will define success for this initiative? Are there regulatory, compliance, or strategic drivers shaping this effort?
2 – Workflows	About their overall customer journey What are the main processes or journeys this solution will support? Can you describe the start and end points for each case type? What triggers each process, and what are the desired results? Are there exceptions or alternate flows we should consider?
3 – Workflow Details	About their work What are the key stages and steps for each workflow? Who is responsible for each stage? Where do handoffs or approvals occur? Are there bottlenecks or pain points in the current lifecycle? Which steps could be automated or streamlined?
4 – Data & Integrations	About their data & systems Which systems or sources provide the data needed for these workflows? What data is required at each stage? Are there integration challenges or data quality concerns? Who owns or manages each data source? Are there privacy or security considerations?
5 – Personas	About who engages with these workflows Who are the users interacting with these workflows (roles, teams, external parties)? What are their goals, responsibilities, and pain points? How do their needs differ across stages or case types? Are there specific experiences or interfaces required for each persona? What KPIs or outcomes matter most to each persona?
6 – Summary	If they want to see more Are there areas we need to explore further or validate with other stakeholders? What open questions remain before we can move to a demo or prototype? What assets or documentation should be gathered for next steps? Who should be involved in the follow-up session to ensure completeness?

Definition of done — Collaboration

First-pass Blueprint created and shared
Open questions and asset list with owners and dates
Follow-on 'High-Fidelity' session booked

This Topic is available in the following Module:

Solution Designer skills: Discovery to delivery 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

Collaboration in Blueprint

How does Blueprint work?

Why: Faster alignment, better decisions

Key Stakeholder Roles in a Blueprint Workshop

How: Run a collaborative session

Definition of done — Collaboration

This Topic is available in the following Module:

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