# Blueprint Delivered PartnerCast — The Quick Start

**URL:** <https://forums.pega.com/t/blueprint-delivered-partnercast-the-quick-start/11570>\
**Category:** Blueprint and App Design\
**Created:** [April 16, 2026, 11:37am UTC](https://forums.pega.com/t/blueprint-delivered-partnercast-the-quick-start/11570 "2026-04-16T11:37:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![BradTanner](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/bradtanner/32/23323_2.png) [@BradTanner](https://forums.pega.com/u/BradTanner)\
**Post date:** [April 16, 2026, 11:37am UTC](https://forums.pega.com/t/blueprint-delivered-partnercast-the-quick-start/11570/1 "2026-04-16T11:37:39Z")

</div>

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**

> **[Pega PartnerCast - Blueprint Delivered Series - The Quick Start | Pega](https://community.pega.com/event/pega-partnercast-blueprint-delivered-series-quick-start)**
>
> This fourth session in the Blueprint Delivered PartnerCast series marks the transition from design intent into execution. Building on the Texel Island Adventures scenario, the session demonstrates how a high‑fidelity Blueprint is imported into Pega...

---

<div class="post-metadata">

**Author:** ![currn](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/currn/32/14676_2.png) [@currn](https://forums.pega.com/u/currn)\
**Post date:** [April 23, 2026, 6:45pm UTC](https://forums.pega.com/t/blueprint-delivered-partnercast-the-quick-start/11570/2 "2026-04-23T18:45:10Z")

</div>

Hi Brad,

I am in a slightly different world than our customers when it comes to uploading a Blueprint. When importing, I am starting from scratch with a purpose of building customer demos, not working on existing applications and extending or tweaking existing workflows.

With demos, the pre-generated information like Data Objects, dummy data, etc.. help enormously to make the application look ‘lived in’ as opposed to needing to create bulk amounts of cases or create dashboards to show a view a user may really use.

I am curious to see how some of our customers respond here to their experience of what to import when uploading. I imagine there are some aspects that make sense to leave out when you are exporting from your app, editing in Blueprint and then re-importing.

Looking forward to continuing the conversation and learning from others!
