Blueprint Delivered PartnerCast — Accelerating the Build

Blueprint and App Design
1

We’ve just wrapped the final session of the Blueprint Delivered PartnerCast, where the focus moved beyond first execution to a challenge many teams face in practice:

How do you keep accelerating once a runnable application already exists — without losing architectural control or future reuse?

Building on the Texel Island Adventures scenario, this session showed — live — how teams can use the same Blueprint to introduce reuse and layered architecture deliberately, while preserving the original business intent.

Rather than redesigning the solution, the emphasis was on making a few intentional build decisions that enable sustained delivery velocity as applications evolve.

Clarity over shortcuts

A recurring theme was that acceleration comes from clarity, not shortcuts:

  • Understanding what should be reusable
  • Knowing what remains application-specific
  • Recognising when those decisions matter most

The demo showed how extracting reusable capabilities into a module — and rebuilding on top of it — leads to:

  • Cleaner architecture
  • Lower long-term delivery risk
  • No change to runtime behaviour

Key delivery questions

  • When does it make sense to introduce reuse — and when does it slow you down?
  • Which Blueprint assets are good candidates for modularisation?
  • How do designers and builders continue collaborating after import?
  • What changes when you rebuild on a reuse layer — and what should stay the same?

Continue the conversation

  • Where do you deliberately design for reuse in your projects today?
  • What signals tell you that a solution is ready to evolve beyond its first application?
  • How does this approach compare to how reuse typically happens in your delivery reality?

Whether you joined live, watched the replay, or followed the full series end to end — jump in and share your perspective.

This is where Blueprint Delivered gets tested against real delivery pressure.

:backhand_index_pointing_right: Watch the Accelerating the Build session replay

2

Hello Brad,
I have just watched the replay of the Partner Webcast series, I really liked the practical approach you have demonstrated on a real life scenario.
One question though on that last session: when and how is the Enterprise layer created? Seems to me it should be a preliminary step to any application building - instead of generating it after the fact.

Or does that imply Blueprint really works in a “proper Pega way” only for existing customers, which have their Enterprise Layer built?

Thanks a lot in advance
FYI @Riadh

3

You’re right, it should be a preliminary step and that is the recommended practice, build your reusable layers (enterprise, framework, module; whichever you like to call it) with your blueprint, importing the containers that should be in that layer (data, persona, or case).

You can also use Blueprint Import to extend an existing reusable layer (for existing customers, who already have one).

It gets quite complex, there are some create videos out there that go step by step on the complexities behind it.

  1. Import: Creating a New Application from Blueprint | Pega
  2. Import: Creating a New Application Built on Existing Assets
  3. Import: Extending an Existing Application with Inheritance (MLP 1)
  4. Import: Incrementally Extending with Blueprint‑Defined Workflows (MLP 2) | Pega

And others on Pega Community Videos.