The Canon Framework
Dirty data is a vocabulary problem, not a math problem. Companies that cannot share a language cannot decide together. The cost is not bad math. The cost is lost focus.
The default response is technical. New CRM. New dashboard. Master Data Management. A Chief Data Officer hired to fix it. Every fix fails because the problem was never technical.
The Diagnosis: The Canon Void
The Canon Void is not a missing document. It is a missing institution.
Definitions exist everywhere. Authority over them lives nowhere. Sales calls "Enterprise" one thing. Finance defines it differently in their ERP. Product tracks it by usage tier. Marketing maps it by industry vertical. All four claim to measure Enterprise revenue. Nobody has ratified the canonical answer.
The Canon Void hits companies at their peak. Exactly when they need discipline to scale fast and room for innovation, they discover their teams are operating in parallel realities.
The Architecture: The Canon
The fix is institutional, not technical.
Institutional language design has worked at scale before. The Academy of the Hebrew Language successfully ratified vocabulary for a language community that grew from near-dormancy to operational use within two to three generations. The mechanism was the same: a governing body, ratification through deliberation, schools and government as enforcement. Welsh and Catalan show similar patterns at smaller scale. The Canon Framework is the corporate application of this institutional design.
Components
The Canon
A versioned, ratified body of cross-functional definitions. The single source of truth for present and future operations. Evolves through ratification, not silent drift.
Canon (the role)
A full-time chair reporting directly to the CEO. Sits above all functions because the Canon spans Sales, Finance, Product, Marketing, and CS. Not RevOps, which lives inside the void it would need to close.
The Canon Council
A small cross-functional ratifying body. Six to eight people. Subject matter experts representing each major function. Finance holds a permanent seat because they cannot be excluded from definitions they will be measured against.
The Collapse
The dated, deterministic moment when the canonical dashboard goes live and the legacy dashboard becomes the Archive. Many parallel timelines collapse into one observed reality. Triggered by a business forcing function: board reporting cutover, comp cycle cutover, or QBR cutover.
The Archive
Legacy data, read-only. Preserved as historical record. Never normalized, never used for forward decisions. Comparability across the Collapse is broken by design. That is the price of a clean future.
Compensation as positive lever
Canon-conformance ties to variable comp across functions. Sales rewarded for entering deals using canon segmentation. Finance for forecast variance against canon-defined segments. Behavior follows comp.
Case law for definitions
Disputes file into the Council, get ruled on, and the rulings become canon. Future arguments reference the precedent. Definitions accumulate case law.
Success metric
Argument absence in offsites. Prep hours per department dropping by half. Finance attendance becoming structural.
The Hard Rules
- 01
Never normalize the past. The Archive is sacred. Comparability across the Collapse is broken by design.
- 02
Reject at ingest. Non-conforming inputs are blocked before becoming data, not cleaned at use.
- 03
The Collapse is total. Partial enforcement teaches that exceptions are negotiable, which becomes the new norm within a quarter.
Companion Series
The Canon Framework is the architecture. The Canon Void Series is the narrative: three posts on the diagnosis, the failed fixes, and the design.
Read the Canon Void Series