Issue 01 : The Single Owner SOP System

In this section, we are talking about what the founder's thoughts were while writing the issue, what didn't make the final cut, and why we took some issue-specific decisions.

Overview

The SOP library failure was one of the most consistent patterns we observed across our research we had in the months before launch. What stood out was not the absence of documentation, but the presence of documentation that nobody used.

That distinction mattered. It felt like a real problem that needed to be explored further.

An issue about "you need to document your processes correctly" would have been easy to write and forget. An issue about why existing documentation fails, structurally, and what to do about it felt more useful.

We chose Maya Chen and Brightfield Commerce for Issue 1 because the DTC e-commerce context gave us a concrete example of failure. Cathy's seven-page SOP answered nothing without requiring domain-specific knowledge from the reader. The pattern translates universally across multiple industries and companies.

What Didn't Make The Final Cut

We originally had a section comparing Notion, Confluence, and Google Docs.

A 400-word section on documentation platform comparisons like Notion v/s Confluence v/s Google Docs. The more we worked on the issue, the more obvious it became that the platform wasn't the real problem.

A badly designed SOP is still a badly designed SOP regardless of where it lives.

We concluded that the platform is not the key variable. We removed it entirely.

The ownership model and the format are the variables. By including a platform section, we were answering a question that didn't matter while the questions that did matter were still unaddressed in the issue.

We also had a section on why people resist documentation in the first place and why experienced team members often avoid writing things down.

Our view was that when documentation is useful, clear, and owned by the right people, much of that resistance disappears on its own. Starting with psychology felt like we were looking at the effect rather than the cause.

We removed that as well in the end.

What We Were Thinking

Maya's decision to delete everything and start over was the counterintuitive editorial choice the issue was based on.

At first, it sounded extreme. But the more we thought about it, the more it made sense.

A documentation system that exists and is wrong is more dangerous than no documentation system. At least when nothing exists, people know they have a problem.

When the wrong documentation exists, everyone assumes the problem has already been solved, while in reality it still exists. This creates a sense of false confidence.

We wanted to highlight that. It was important to say it clearly, without trying to soften the message.