In most Blueprint engagements: you feed the AI a description, it generates a tidy set of workflows and data models, everything looks reasonable, and you move forward. Clean. Logical.
Then Authoring starts, and you realize the design missed something crucial. Not something hard to see—something only a person who’s done the work would notice. And you’re retrofitting.
The gap isn’t the AI’s fault. It’s a design situation that requires human judgment.
AI is fast
AI is fast at generating first drafts. It can produce a workflow where underwriting happens after quality check, because the documents say so. But it won’t catch that the underwriter needs information from a completely different source than the quality checker is looking at. Or that quality check and risk review should happen in parallel. Or that there’s a whole class of exceptions your workflow doesn’t account for.
Those gaps surface when someone who knows the workflow looks at the generated design and thinks: “Wait, that’s not how this works.”
That moment—where you feel the design is missing something—is where your judgment as a Solution Designer is pivotal. Without human judgment, there is a risk of moving forward a design to the Solution Builder that will need rework later.
Hands-on tutorial
In the Designing the application challenge of the Pega Blueprint Design Experience mission, you generate an initial design twice: once with only a written description, then by enriching that description with supporting business documents. Each time, the AI produces something coherent.
The second pass is almost always better. But here’s the lesson: neither is done. Both have gaps—just different ones.
The mission shows you how to recognize those gaps. When you refine the workflows in later labs, you will notice moments where the generated design feels generic, or where it bundles distinct journeys together, or where it misses the choreography of who needs what information when. They’re examples of using your design judgment.
The AI showed you a reasonable first interpretation. Your job is to interrogate that interpretation against what the business stakeholders share with you. That’s when the Blueprint gets better.
How to apply human judgment in practice
When you hit a generated design that feels generic or incomplete, don’t accept it. Ask: What’s this design assuming about how the work happens? Then compare that assumption to reality. If they don’t match, the design needs to change. That’s not the AI failing—that’s you doing your job.
The designers who get the most out of Blueprint aren’t the ones who accept the AI’s output. They’re the ones who treat it as a starting conversation with the business. They use the AI Assistant strategically: more specific prompts produce more useful designs. They leverage Preview early, with the people who do the work. They edit ruthlessly when something doesn’t match reality.
What did you bring to a Blueprint that made the design better?
Share one insight, question, or change that came from your experience—or react with:
if your judgment helped clarify the design
if stakeholder input changed its direction
if preview led to a better solution
Even a quick example could help another Solution Designer recognize the value they bring to Blueprinting.