> ## Content Index > Fetch the complete content index at: https://www.theheadroomhq.com/llms.txt > Use this file to discover other available public pages before exploring further. # V-01 : The Single Owner SOP System - URL: https://www.theheadroomhq.com/the-single-owner-sop-system-verdict/ - Published: 2026-06-19T05:25:29.000Z - Updated: 2026-08-27T05:39:00.000Z - Description: A structured evaluation of the operational decisions explored in HQ Library Issue 01. - Author: Headroom Editorial Team - Tags: Verdict, C02 - Brightfield Commerce, D01 - Process Documentation Coverage, D09 - Onboarding Effectiveness, BC-01 : Maya Chen [**< All Verdicts**](https://www.theheadroomhq.com/verdict/) --- ### Hard Question --- Maya Chen spent three months rebuilding Brightfield's SOP library from scratch by deleting 83 documents nobody trusted and replacing them with a smaller, owned, tested set. Three months later, she discovers two of her most experienced coordinators have been quietly steering new hires away from the new documentation, telling them "the real process is different" and training them on informal methods instead. When she investigates, she finds the senior coordinators are not wrong. Several SOPs are genuinely incomplete, and two SOPs contain steps that no longer match how the team actually executes the process. The team has split: some follow the documentation, some follow the informal version, and neither group agrees on which is authoritative. **Should Maya address the undermining behavior or fix the documentation first?** --- ### Verdict --- ### Context This is the single most predictable failure point in any documentation rebuild, and it's predictable because the people causing it are usually right. Two experienced coordinators independently routing new hires around the same SOPs is not insubordination. It is the most efficient quality signal Maya is going to get on her new library — and it arrived at no cost, three months after launch, before a customer ever had to discover the gap the hard way. **The trap here is treating this as a behavioral problem because it looks like one.** People going around an official process, training others informally, and undermining a system that leadership spent three months building. Every instinct built for managing it points toward correcting the people and their behavior. Almost none of those instincts are correct in this case, because the behavior is downstream of an accuracy problem, not the cause of one. --- ### Our Position Fix the documentation first, but not silently, and not slowly. The two coordinators should be in a working session within the week, not a disciplinary one. Maya needs to walk through every disputed SOP against what they actually do on the floor, incorporate the corrections in real time, and republish with both coordinators named as contributing reviewers, not as people who got caught. It's the only sequence that actually fixes the underlying problem. If Maya disciplines the behavior before closing the gap, she teaches the team that compliance with the documentation matters more than the documentation being correct, which guarantees the next gap stays hidden instead of surfacing the way this one did. She also jeopardizes her relationship with two individuals who are most capable of identifying her remaining errors at the critical moment when she needs their assistance the most. The error to avoid here is treating "the SOPs are incomplete" and "the coordinators are undermining the system" as two separate problems requiring two separate responses. They are one problem with two visible symptoms. Fix the cause of incomplete, outdated documentation, and the symptom resolves itself because the coordinators' only reason to train informally was that the formal version was wrong. Once it isn't wrong anymore, the channel for the workaround disappears on its own, without Maya having to manage it as a behavioral issue at all. --- ### Operational Implication This week, Maya pulls the two coordinators into a structured review of every SOP, either of them has been informally overriding. She uses the new-hire test from the original rebuild — having someone unfamiliar with the process attempt to execute the corrected version using only the document, and watching where they stumble. Republish within five business days with both names attached as reviewers and the review date updated. Only after the revised versions are live does Maya have the second, separate conversation, not about being wrong, but about the process. During the correction period, Maya should tell the full team directly that the SOPs are under active review and that the corrected versions will be the authoritative standard once published — removing the ambiguity about which version to follow without requiring anyone to act on an outdated document in the interim. Going forward, gaps get raised and fixed through her directly and immediately, not absorbed into an informal parallel training track that nobody else can see. That second conversation lands differently once it's no longer attached to a correction the coordinators were right to make. --- ### Learn --- - [Issue 01: The Single Owner SOP System](https://www.theheadroomhq.com/issue-01-the-single-owner-sop-system/) --- ### Dimensions --- - [Dimension D01 - Process Documentation Coverage](https://www.theheadroomhq.com/dimension-1-process-documentation-coverage/)