02 Operating Model

Organisational Structure

Purpose

This document provides an overview of the company’s organizational structure, including Guilds, Practices, Value Streams, and Products, along with key roles and responsibilities.

Organizational Model Overview

The company operates using a matrix organization model with two primary dimensions:

1. Functional Organization (Guilds & Practices): Domain expertise and capability development
2. Value Delivery (Value Streams & Products): End-to-end value creation and delivery

Guilds

Guilds are functional domains that own and govern related management practices.

Guild Structure

Guild Code	Guild Name	Primary Focus	Lead
GL01	Executive Guild	Strategy, Finance, Risk	[Name/TBD]
GL02	Sales Guild	Sales, Business Development	[Name/TBD]
GL03	Delivery Guild	Client Delivery, Solutions	[Name/TBD]
GL04	Technology Guild	Architecture, Engineering, Platforms	[Name/TBD]
GL05	Administration Guild	Talent, Operations, Enablement	[Name/TBD]

Guild Responsibilities

Guilds are responsible for:

• Defining and maintaining practices within their domain
• Ensuring practice artefacts (policies, processes, procedures) are current
• Developing domain expertise and capabilities
• Providing governance oversight for their practices
• Contributing expertise to Value Streams and Products

Guild Leadership

Guild Lead:

• Owns the guild’s strategic direction
• Governs all practices within the guild
• Approves changes to guild and practice content
• Represents guild interests to leadership
• Develops guild members’ capabilities

Role Ownership and Cross-Guild Criteria

Roles belong to a primary Guild that owns and governs the role definition. Other Guilds may contribute cross-guild criteria that define what they expect from that role.

How it works:

• Each role has a primary Guild that owns the overall role definition and its core competency criteria
• Other Guilds contribute cross-guild criteria defining expectations from their domain perspective
• All criteria are aggregated into Evaluation Workbooks by the HR Management Practice using the criteria-list rendering plugin

Example — Engineer Role:

Guild	Relationship	Criteria Focus
Technology Guild	Primary	Software engineering, solution and platform design
Sales Guild	Cross-Guild	Stakeholder engagement and client interaction
Delivery Guild	Cross-Guild	Consulting, project management, business analysis

Directory structure:

• Primary criteria: [Guild]/Roles/[Role Type]/[Level].md
• Cross-guild criteria: [Guild]/Roles/Cross-Guild/[Role Type]/[Level].md

This model enables each Guild to independently govern its own criteria while the HR Management Practice aggregates them into a unified evaluation framework.

Management Practices

For an overview of how Management Practices are structured, see Management Practice — Overview.

Value Streams

For an overview of how Value Streams are structured, see Value Stream — Overview.

Products

Products are solutions or platforms that the company develops and maintains.

Product Responsibilities

Products are responsible for:

• Product vision and strategy
• Roadmap planning and prioritization
• Technical architecture and implementation
• User experience and satisfaction
• Product-specific documentation and decisions

Product Leadership

Product Owner:

• Defines product vision and strategy
• Owns product roadmap and backlog
• Makes product decisions and trade-offs
• Ensures product meets customer needs
• Manages product team and resources

Technical Lead:

• Owns product technical architecture
• Guides technical decisions and implementation
• Ensures code quality and best practices
• Manages technical debt
• Supports development team

Leadership Team

The Leadership Team provides overall organizational governance and strategic direction.

Leadership Responsibilities

• Company strategy and vision
• Organizational design and structure
• Cross-functional prioritization and resource allocation
• Company-wide policies and standards
• Guild and Value Stream oversight

Governance Model

Decision Rights

Level	Scope	Decision Authority	Approval Required
Company	Company-wide policies, structure	Leadership Team	Leadership consensus
Guild	Guild structure, practices	Guild Lead	Leadership approval for major changes
Practice	Practice artefacts, standards	Practice Owner	Guild Lead approval for major changes
Value Stream	VS performance, coordination	VS Owner	Guild Leads for process changes
Product	Product strategy, roadmap	Product Owner	Leadership for major pivots

Escalation Paths

1. Practice → Guild: Practice Owner escalates to Guild Lead
2. Guild → Leadership: Guild Lead escalates to Leadership Team
3. Value Stream → Guilds: VS Owner escalates to involved Guild Leads
4. Product → Leadership: Product Owner escalates to Leadership Team

How This Structure Maps to Knowledge

The content structure mirrors this organizational model:

content/
├── 00 Governance/        # Leadership Team
├── 01 Value Streams/             # Value Stream coordination
│   └── [VS##] [Name]/            # Individual Value Streams
├── 02 Guilds/                    # Guild domains
│   └── [GL##] [Name]/            # Individual Guilds
│       ├── Practices/            # Practices within Guild
│       │   └── [Practice Name]/  # Individual Practices
│       │       ├── 01 Policies/
│       │       ├── 02 Processes/
│       │       ├── 03 Procedures/
│       │       ├── 04 Guides/
│       │       └── 05 Templates/
│       └── Roles/                # Role criteria owned by Guild
│           ├── [Role Type]/      # Primary roles (e.g., Engineer/)
│           └── Cross-Guild/      # Cross-guild criteria contributions
└── 03 Products/          # Product teams
    └── [Product Name]/           # Individual Products

Related Resources

• Guild Index
• Value Stream Index

---

Version: 1.0
Last Updated: 2026-02-11
Maintained By: Leadership Team