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

Key Concepts and Terminology

Glossary for Transform objects, work items, and common abbreviations.

Overview

This glossary standardizes Transform terminology across an Account. Consistent terminology improves reporting, search, and governance.

Key Concepts

Account, Organization, Project

  • Account: top-level container for all work

  • Organization: container for a client, department, or business unit

  • Project: delivery container for a single transformation initiative

Blueprint, Process, System

  • Blueprint: reusable structure applied to new Projects

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

  • System: application or platform that supports a Process

A System can be a business application, such as an ERP system or a CRM system.

Segment Types and Segments

  • Segment Type: a business dimension, such as Region or Department

  • Segment: a value inside a Segment Type

Segments and Segment Types are managed at the Organization level.

Start here: Segmentation

Work items

  • Requirement: statement of scope that must be delivered and validated

  • Task: executable work that implements scope

  • Test case: validation steps linked to a Requirement

  • Artifact: supporting file or reference linked to work items

How It’s Used

Use this glossary when defining Blueprints and reporting fields. Use it when standardizing naming across multiple Projects.

Benefits

  • Fewer reporting inconsistencies across Projects

  • Faster onboarding through shared vocabulary

  • Cleaner search results and less duplicated work

Setup Steps

  1. Adopt this page as the default glossary for an Account.

  2. Standardize page titles, field labels, and view names to match this glossary.

  3. Link related pages in onboarding documentation to reduce repeated explanations.

Best Practices

  • Avoid abbreviations for Organization and Project names.

  • Prefer dropdown fields over free text for reporting fields.

  • Use the term Save View for a stored view configuration.

  • Treat Segments as Organization-scoped structure, not tags.

Summary

This glossary defines the core Transform terms used across Account, Organization, and Project scopes.

Related:

Last updated