Zeta enforces complete operational transparency by organizing its metrics into a unified, non-overlapping hierarchy mapped directly to the four core governance dimensions. This chapter details our telemetry taxonomy and authoritative systems of record.
1. The C3M Telemetry Taxonomy
Operational metrics are categorized across the four C3M dimensions to ensure absolute clarity of ownership:
1.1 Capability Metrics (Governing Entity: Product Owners & PAC)
These metrics quantify the compounding leverage of Zeta's product platforms and measure our defense against custom engineering drift:
- Asset Leverage Multiplier (\(\lambda\)): Measures the scaling efficiency of the Product Line Engineering (PLE) model by comparing the equivalent labor value of standard platform-provided capabilities to the manual custom labor required to assemble them: $$\lambda = \frac{\text{Standard Capability Value Consumed (Equivalent FTE-hours)}}{\text{Custom Delivery Capacity Expended (Actual FTE-hours)}}$$
- Configuration-to-Customization Ratio (CCR): Monitors the percentage of customer deployments completed entirely via standard configuration parameters: $$\text{CCR} = \frac{\text{Deployments completed via standard parameters}}{\text{Total Customer Deployments}}$$
1.2 Capacity Metrics (Governing Entity: EF PPM & Outcomes CoEs)
These metrics monitor resourcing velocity and ensure unassigned capacity is programmatically visible:
- Onboarding Velocity (OV): Tracks the average time required to transition a staffed practitioner or HAT onto an active client squad until they achieve full productive throughput.
- Portfolio Allocation Accuracy (PAA): Measures the variance between forecasted staffing capacity and actual hours billed on active customer SOWs.
1.3 Competency Metrics (Governing Entity: Chapter Stewards & Academy)
These metrics evaluate craft excellence, work automation, and certification coverage:
- Chapter Self-Automation Rate (CSAR): Tracks the percentage of routine chapter workflows (e.g., code linting, environment bootstrap) that have been fully automated.
- Zero-Defect Quality Index (ZDQ): Measures the stability of code delivered by chapter members, tracking the frequency of post-release regressions.
- Talent Acquisition & Onboarding Velocity (TAOV): Tracks recruiting pipeline efficiency and time-to-certification.
- Chapter Up-Skilling & Continuous Training Rate (CUCR): Evaluates ongoing practitioner education and platform capability certification coverage.
2. Authoritative Systems of Record
To prevent "data massaging" and ensure complete objectivity, telemetry must be compiled programmatically from designated, immutable systems of record:
- Jira & Git Telemetry (Code & Work logs): Used to extract time-logging, task metadata, and code-contribution metrics to calculate \(\lambda\) and CSAR.
- SRE Monitoring Platforms (Uptime & Performance): Centralized systems (e.g., Datadog, Prometheus) that track API response times, defect SLA adherence, and production uptime metrics.
- The Academy Registry (Certifications): The immutable ledger tracking practitioner role-readiness and platform competence certifications.
- HR Information Systems (Staffing & Retention): Track staffing schedules, onboarding latency, and chapter headcount velocity.