Processes

Set up a reusable process map for a Blueprint.

Overview

Processes are the primary structure inside a Blueprint. They model workflows, phases, and workstreams for delivery tracking.

Key Concepts

• Process: reusable workflow, phase, or workstream
• Hierarchy: parent-child rollups for navigation and reporting
• Linking: relationships to Systems and Segments for traceability

How It’s Used

Use Processes to group Requirements and Tasks by business flow. Use hierarchy for rollups in reporting and reviews.

Processes defined in a Blueprint can be included in new Projects. Some UI labels may refer to Projects as Transformations.

Benefits

• Consistent structure across Projects
• Cleaner reporting by workflow and ownership
• Faster navigation for delivery teams

Setup Steps

1

Create a process

1. Navigate to Blueprints.
2. Open a Blueprint.
3. Open Processes.
4. Select Add process.

Define:

• Name
• Optional fields when enabled, such as Code, Owner, and Description

2

Build hierarchy (optional)

Create parent processes for rollups. Add child processes that represent real subsets.

See Process Hierarchy.

3

Link to Systems and Segments (optional)

Link processes to Systems to clarify technology scope. Link processes to Segments to support reporting by business dimension.

• Create Systems
• Segmentation

Best Practices

• Use one naming pattern across Blueprints.
• Keep hierarchies to 2–3 levels for most teams.
• Avoid creating processes for single tasks.

Summary

Processes define the Blueprint structure used for delivery tracking.

Hierarchy and linking improve navigation and reporting.

Related:

• Process Hierarchy
• Create Systems
• Systems Management
• Segmentation