I’m currently exploring how teams are using Pega Blueprint during collections transformation programmes… not just for early idea-building, but also to help support discovery, alignment, and delivery planning.
I’m particularly interested in is whether people are using Blueprint to help structure or visualise things like:
customer vulnerability handling
omni-channel collections journeys
prioritisation and decisioning
agent guidance
audit/compliance considerations
integration points with existing legacy debt systems
For teams working in regulated environments, how are you balancing:
the speed and flexibility of BP
governance and architecture control
reuse across different programmes or clients
Are people mainly using Blueprint as:
a discovery accelerator
a collaboration tool
a starting point for delivery
or more of an ongoing design reference throughout the programme?
Would be really interested to hear how others are approaching this in real delivery environments.
Really interesting discussion about Pega Blueprint. From what I’ve seen, many teams are using Pega Blueprint not only for early idea generation but also for discovery, collaboration, and delivery planning during collections transformation programmes. It helps teams quickly visualise customer vulnerability handling, omni-channel collections journeys, decisioning, agent guidance, compliance requirements, and integration points with legacy systems. In regulated environments, organisations are balancing the speed and flexibility of Pega Blueprint with proper governance, architecture reviews, and reusable standards to maintain compliance and control. It is also becoming a useful collaboration tool where business teams, architects, operations, and delivery teams can align early and reduce gaps during implementation. Overall, Pega Blueprint is evolving from just a discovery accelerator into an ongoing design and transformation support tool throughout the programme lifecycle.