For the complete documentation index, see llms.txt. This page is also available as Markdown.

Blueprint Fundamentals

Build reusable structure for Projects using processes, systems, and segmentation.

Overview

Blueprints define reusable structure for delivery work. They reduce setup time and improve consistency across Projects.

Key Concepts

  • Blueprint: reusable structure applied to new Projects

  • Process: business workflow, phase, or workstream tracked in a Blueprint

  • System: application or platform linked to Processes

  • Segmentation: Segment Types and Segments used for scoping and reporting

How It’s Used

Create a Blueprint for a repeatable delivery method. Reuse the Blueprint to create multiple Projects with consistent structure.

Benefits

  • Faster Project setup with fewer early decisions

  • Consistent naming, hierarchy, and reporting fields

  • Cleaner governance through standard structures

Setup Steps

1

Create a Blueprint

2

Define Processes

3

Define Systems

4

Define segmentation (optional)

Best Practices

  • Start with a small set of Processes and expand over time.

  • Keep hierarchies shallow to improve navigation and reporting.

  • Avoid client-specific names in reusable Blueprints.

Summary

Blueprints standardize delivery structure across Projects. Processes, Systems, and Segmentation provide core building blocks.

Related:

Last updated