Skip to content

Practice Template

Why This Exists

This document defines the mandatory structure for every future Practice in the Algosure Digital Procurement Company.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

A standard Practice template ensures every Practice is documented consistently, aligned to DDD ownership boundaries, measurable through KPIs, executable through SOPs, and understandable to product, engineering, operations, and AI design teams.

Mandatory File Structure

Every Practice folder must contain:

docs/02-Practices/<Practice-Name>/
  README.md
  Mission.md
  Responsibilities.md
  Business-Capabilities.md
  Digital-Professionals.md
  Governance.md
  Meetings.md
  KPIs.md
  SOPs.md
  Reports.md
  Relationships.md
  Glossary.md

Mandatory Operating Sections

Section Required purpose
Overview Defines why the Practice exists, who owns it, and what business value it creates.
Mission Defines the Practice mission and boundary.
Responsibilities Defines what the Practice is accountable for.
Business Capabilities Lists capabilities owned by the Practice.
Digital Professionals Defines the Digital Professionals that execute Practice work.
Governance Defines rules, decisions, controls, and ownership boundaries.
Meetings Defines operating cadence, reviews, and coordination forums.
KPIs Defines performance measures and source boundaries.
SOPs Defines repeatable operating procedures.
Reports Defines Practice reports and management outputs.
Relationships Defines dependencies and collaboration with domains and Practices.
Glossary Defines Practice-specific terms.

Required Front Matter

Every Practice document must use YAML front matter:

---
title: <Document Title>
version: 0.1.0
status: draft
owner: Chief Product Officer and Enterprise Architect
classification: Practices
practice: <Practice Name>
last_updated: 2026-06-29
---

Top-level Practice standards may omit practice when the document applies to all Practices.

Required Ownership Statements

Every Practice must explicitly state:

  • Practices own capabilities.
  • Domains own business facts.
  • Digital Professionals execute work.
  • SOPs govern repeatable work.
  • KPIs measure performance.
  • Executive Office coordinates cross-Practice priorities, approvals, escalations, and executive reporting.

Required Model Diagram

Every Practice overview should include a Mermaid diagram showing how the Practice relates to capabilities, Digital Professionals, SOPs, KPIs, domains, and Executive Office coordination.

flowchart TD
    Practice[Practice]
    Capability[Business Capabilities]
    Professional[Digital Professionals]
    SOP[SOPs]
    Domain[Domains own facts]
    KPI[KPIs]
    Exec[Executive Office]

    Practice --> Capability
    Professional --> Capability
    SOP --> Capability
    Domain --> Capability
    Capability --> KPI
    Exec --> Practice

Mandatory Quality Rules

  • Use professional enterprise language.
  • Avoid gamified or childish metaphors.
  • Avoid duplicating source-domain fact ownership.
  • Keep the Practice aligned to the Architecture Mirror Principle.
  • Keep the Practice aligned to One Concept, One Owner.
  • Use Mermaid diagrams where useful.
  • Keep MkDocs-compatible Markdown.