2026 · ARCHIVE
STRATEGIC OPERATING DOCUMENT ARCHITECTURE
A 12-type document system and AI prompting guide built so an entire organization could produce strategic documents in a consistent voice, without starting from a blank page every time.
A note on this entry. The organization name has been changed to "Cascade Industries." The initiative is real and currently active inside that organization, so identifying details have been altered to protect an ongoing client relationship. The system structure described is accurate.
CONTEXT
Cascade had a familiar problem: every leader writing a strategy document, a charter, or a board brief was starting from a different mental model of what that document should contain and sound like. As AI tools became part of how people drafted these documents internally, the inconsistency got worse, not better. A leader could prompt an AI tool to "write a strategy doc" and get something structurally fine but tonally and architecturally disconnected from how Cascade actually communicated internally.
APPROACH
Rather than write more templates, the work was to define the system underneath the templates. Twelve distinct document types were mapped, Doctrine, Strategy, Architecture, Charter, Scope, Framework, Performance, Executive Overview, Roadmap, Review, Communication, and Concept, each with a defined primary role, a clear trigger for when to use it over the others, and a specific prompt tone calibrated to that document's purpose. The types were also explicitly connected to each other: Doctrine defines why, Strategy sets what, Architecture builds how, Charter and Scope own who and what, Roadmap plans when, Performance measures results. One system, twelve interlocking parts.
The deliverable included a master AI prompt template anyone in the organization could fill in with their topic and audience, and a quick-reference matrix mapping common business situations directly to the right document type. The guide was built explicitly as a living document, meant to be updated and redistributed rather than filed away after one rollout.
OUTCOME
The immediate outcome was a shared vocabulary. Leaders across departments could now say "this needs to be a Charter, not a Strategy doc" and mean the same thing by it. That sounds small. In practice it eliminated a recurring source of friction: documents that were structurally confused because nobody had agreed in advance what kind of document they were supposed to be. The guide is in active use as the default reference whenever someone at Cascade sits down to draft a strategic document, AI-assisted or not.
LESSON
The temptation with AI writing tools is to solve the problem at the prompt level, better instructions, better examples. That helps, but it doesn't fix the deeper issue if the organization itself doesn't have a shared taxonomy of what it's trying to produce. The real leverage point wasn't the prompt template. It was the twelve-document map underneath it. Get the system right first, and the prompting layer becomes simple by comparison.