When working in Pega Blueprint, how do you decide it’s time to stop refining and start building?
Looking forward to learning from your experiences.
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.
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.
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
That’s a great answer. I think for me, an often overlooked part is fully following exception paths when a decision shape is put in. Also, the BP should also be used to size the implementation effort and therefore needs sufficient coverage to ensure the sizing has greater accuracy.
While downloading the Blueprint we can see the issues in the current Blueprint based on the defined best practices. This list can be a great guide to make sure we are having a high fidelity Blueprint. Here is an example with few open issues.
Also as we know blueprint is evolving. So a ready to import Blueprint today would not be as ready as a Blueprint tomorrow. For example, recent enhancements around business rules, SLAs, Embedded data means your workflow can have much more fidelity captured in terms of escalation actions and conditional processing and your views in the Blueprint can represent complex embedded data structures.
Hence it is important to ensure that the designers working on the Blueprint are aware of newer capabilities that have been added to the Blueprint and have ensured that those have been leveraged as appropriate while obtaining the business buy-in before the Blueprint is deemed ready for import at that specific point in time
