Each area is useful only when its edges are visible. The question is not how many labels can be sold. The question is what this does not include.
What it is: structure for roles, decision forums, escalation and recurring management routines.
Typical trigger: growth, acquisition, leadership change or unclear accountability between functions.
What this does not include: interim management, hiring decisions or permanent ownership of the model.
What it is: analysis and redesign of how work moves across teams, systems and approvals.
Typical trigger: repeated handover failure, duplicated work or delay caused by unclear ownership.
What this does not include: running the process after handover or forcing adoption without client authority.
What it is: requirements discipline, option comparison, shortlist logic and recommendation records.
Typical trigger: a system choice is being shaped by preference before requirements are written down.
What this does not include: vendor resale, partner incentives, product implementation or procurement authority.
What it is: principles for data ownership, integration boundaries, reporting flows and system responsibility.
Typical trigger: inconsistent data definitions, brittle integrations or unclear source-of-truth decisions.
What this does not include: software engineering, database administration or security certification claims.
What it is: clarity on who decides, who advises, who is consulted and how decisions are recorded.
Typical trigger: committees discuss the same issue repeatedly without an accepted decision owner.
What this does not include: replacing executive judgement or guaranteeing that leaders will use the structure.
What it is: stakeholder mapping, communication sequencing, readiness questions and adoption responsibilities.
Typical trigger: a new process or system is technically ready but operationally unowned.
What this does not include: training delivery at scale, internal communications ownership or behavioural guarantees.