Blueprint Ready or One More Tweak?

Blueprint and App Design
1

When working in Pega Blueprint, how do you decide it’s time to stop refining and start building?

  • What’s the minimum you make sure is solid before importing the Blueprint to avoid rework later (case types, key data, integrations, personas, etc.)?
  • What have you learned about over- or under-designing in Blueprint?

Looking forward to learning from your experiences.

2

My thoughts…

  • Review the Preview with the business team to confirm the workflow functions as expected and aligns with their vision.

  • Review the Preview with the business team to ensure the screens capture the majority of required data fields and data objects (at a high level).

  • Review the Integration with their technical team to confirm all required integrations are identified and documented.

1 Like
3

In addition to @RameshSangili ‘s comment. I think it’s really important to nail your Personas (access/etc settings) and ensure, to the extent possible, that your assignments are all routed to personas appropriately. On import this takes care of SOOO much of the work around creating access groups, workbaskets, etc. AND it reinforces our work-basket + “get next” approach to work distribution.

2 Likes
4

As a former business analyst, it’s easy for me to err on the overdesign side! I’ve been applying this “checklist” to determine if it’s time to import:

  • Shared clarity achieved – Outcomes, users, and success measures are agreed; no open “why” questions

  • Workflow is stable – End‑to‑end stages and exceptions are set; changes are no longer structural

  • Decisions & data are sufficient – Key decisions and core data objects are identified

  • Questions shift to build – Focus moves to integrations, rules, UI, security, and performance

  • Diminishing returns – Additional refinement yields little new insight

1 Like