I used to walk into a design workshop with an empty canvas. Now I walk in with a Blueprint — and increasingly, a .PEGASIGN file.
For modernization engagements, the Application Signature Tool has become my first move. You install it into the legacy Pega app, run it from Dev Studio, and in minutes it extracts the full metadata — case types, lifecycle, data model, integrations — and packages it into a signature file. No tribal knowledge. No weeks of manual discovery. Just a real picture of what’s actually there.
That file goes straight into Blueprint as a code analysis document. Blueprint ingests it and generates the reimagined application structure — case types, life cycles, data objects, and personas — using that real-world context as the foundation.
The shift I didn’t expect: clients stop debating requirements and start reacting to design. And because Blueprint’s insights are driven by actual case volume data, not gut instinct, the whole conversation shifts from “what should we build?” to “here’s what we actually have to work with.”
A few things I’ve noticed in practice:
- App Signature → Blueprint closes the gap between discovery and dev (no handoff fumbling)
- Business stakeholders respond to a live preview way differently than a deck
- For orgs buried in tribal knowledge, you finally have something objective to start from
Curious how others are using it. Are you running Blueprint sessions solo, or collaborating live with business and IT in the room?