AI is accelerating design cycles, which has moved the pressure earlier. There is less time to make the right call up front and less patience for “we’ll fix it later during authoring.”
So, it’s worth getting hands-on with Blueprint before your project depends on it.
Most design work is translation
Someone explains the problem, you structure it, and you play it back to them. The vaguer the request, the more rounds it takes.
Blueprint helps stakeholders define vague requests because you generate the design with stakeholders in the room. When someone says “this feels wrong,” you change it on the spot instead of sending a revised document weeks later.
Making changes in Blueprint, with stakeholders, only works if you know the tool well, including when the AI Assistant helps and when to slow down and think it through yourself. That’s the intent of the Pega Blueprint Design Experience Mission tutorial.
What You Will Do
In the tutorial, you will work through a realistic lending scenario: U+Bank wants to modernize its personal loan origination process, which today relies on manual work and disconnected tools. It is slow and error-prone.
Your job is to design a complete digital application, end-to-end, using Blueprint. You will:
- Turn a messy process into Case Types, stages, and steps
- Decide what data belongs where and which personas need it
- Use Preview to check the design with stakeholders before anything gets built
- Use the AI Assistant where it saves time, and override it when it’s wrong
- Practice versioning, collaboration, and recommendations
Getting Started
If you are new to Pega Blueprint, or Blueprint Delivered, this is a good place to practice. If you already use Blueprint, this gives you a scenario to hone your skills.
Head to Pega Academy and search for Pega Blueprint Design Experience. It takes about 2 hours start to finish, including the labs.
When you are done, I would like to hear: What surprised you about the design process? What felt most useful? What would you do differently on your next project?