Creating Blueprints

Create a Blueprint and define the reusable structure for new Projects.

Overview

Creating a Blueprint establishes reusable delivery structure. Blueprints are typically created before creating many Projects.

Key Concepts

• Blueprint scope: reusable structure for future Projects
• Processes and Systems: primary structure used for traceability and reporting
• Segmentation: optional Organization-level structure for consistent reporting

How It’s Used

Use this workflow during initial rollout. Use it again when a new delivery method is introduced.

Benefits

• Faster onboarding for new Projects
• More consistent naming and reporting across initiatives
• Reduced rework from inconsistent structure

Setup Steps

1

Create the Blueprint

1. Navigate to Blueprints.
2. Select New Blueprint.
3. Set the name and description.

Use a stable naming pattern, such as {method} Blueprint.

2

Define Processes

Define Processes to represent workflows, phases, or workstreams.

• Processes
• Process Hierarchy

3

Add Systems

Add Systems that support delivery scope.

• Create Systems
• System Types

4

Define segmentation (optional)

Define Segment Types and Segments when reporting needs consistent structure.

• Segmentation

Best Practices

• Keep the first Blueprint minimal and expand after use.
• Standardize naming before creating many Processes and Systems.
• Treat Blueprint changes as governed updates.

Summary

Creating a Blueprint establishes reusable structure for Projects. Processes and Systems are the primary building blocks.