We’ve just wrapped the fourth session of the Blueprint Delivered PartnerCast, where the focus moved decisively from readiness into execution.
This session marked the pivot point where Blueprint stops being theoretical and starts becoming tangible — as a real, running Pega application.
Using the Texel Island Adventures scenario, the session showed a live Blueprint import into Pega Infinity and explored what “quick start” really means in delivery terms.
Rather than treating import as a one-click shortcut, the discussion emphasized deliberate choices:
- What to import
- What to defer
- How solution architects and builders retain control while still moving fast
Speed vs governance
A recurring theme throughout the session was balancing speed with governance.
Partners saw how importing one outcome at a time:
- Simplifies validation
- Reduces risk
- Keeps teams aligned as Blueprint capabilities evolve
The demo also validated that high-fidelity design carries through — from workflows and data models to personas, access, decisions, and SLAs — when Blueprinting is done with delivery in mind.
Key delivery considerations
- Where should builders slow down during import — and where should they move quickly?
- How do you decide what belongs in the first import versus a later increment?
- How much architectural control should LSAs exercise during import?
- What signals tell you that a Blueprint is ready to become runnable, not just designed?
Continue the conversation
- How do you currently approach Blueprint import on real projects?
- Where have you seen teams struggle when moving from design intent into execution?
- What trade-offs do you consciously make between speed, control, and reuse?
Whether you joined live, watched the replay, or are actively applying Blueprint Delivered today — share your experience.
These peer discussions are where Blueprint Delivered gets tested against real delivery pressure.
Watch the session replay