The easiest way to test written operating culture is not to count documents. Document volume may mean the company is serious. It may also mean the company has learned to turn ambiguity into text without turning text into decisions. The audit should ask whether writing improves operating quality.

Start with the decision surface. For the last five important decisions, can a capable person find the artifact that framed the choice? Does it name the decision clearly? Does it show options? Does it make tradeoffs visible? Does it name the decision owner? Does it record what changed after the call? If the answer is no, the company may be relying on memory more than it admits.

Next, inspect evidence quality. Do memos distinguish observed facts from assumptions? Do they link to source material? Do they name uncertainty? Do they explain why the current evidence is enough to act? If every memo reads as equally confident, the written layer is hiding risk.

Then review decision rights. Are memos clear about who decides, who recommends, who must be consulted, and who executes? Or do they circulate broadly until the strongest personality or most senior title wins? Ambiguous decision rights are one of the fastest ways for written culture to become political.

Look at comments and review behavior. Do comments improve the decision, or do they mostly perform intelligence? Are objections raised early enough to matter? Are blockers separated from preferences? Does the final artifact summarize unresolved dissent? Healthy review leaves a trail of better thinking. Unhealthy review leaves a trail of vague concerns and defensive replies.

Audit the decision log. Can the company find prior decisions by topic, owner, and date? Does the log include decisions not to act? Are assumptions and review dates recorded for major choices? Are old decisions updated when conditions change? If the log exists but nobody uses it, the company has archival decoration, not memory.

Inspect artifact choice. Are teams using the right format for the work? If everything becomes a memo, the system is too blunt. If everything becomes a meeting note, the system is too weak. Good written culture chooses the artifact that matches the job.

Check whether writing changes meetings. Do meetings start with shared context because the memo did its work? Do leaders spend live time on tradeoffs and judgment rather than background reconstruction? Are decisions faster after written review? If meetings remain just as foggy, the documents are not carrying enough operating load.

Look for portfolio overload. How many memos are active at once? How many require executive attention? How many decisions are waiting for review? AI and templates can increase throughput, but the organization still has finite judgment. A written culture that produces more decisions than the company can absorb will create a new bottleneck.

Review post-decision learning. Pick three decisions that had meaningful outcomes. Did the company compare expected and actual results? Did it update assumptions? Did it change a rule, metric, roadmap, or operating cadence? Written culture should make learning easier. If nobody returns to the artifact, the company is not closing the loop.

Pay attention to trust. Do people believe memos are used to think, or to justify decisions already made? Do they feel safe raising dissent in writing? Do leaders acknowledge uncertainty? Do decision owners take accountability after the call? Written culture depends on trust because the page makes reasoning visible. If visibility is punished, people will write defensively.

AI deserves its own audit line. Which artifacts were AI-assisted? Were sources preserved? Did a human owner verify claims? Did AI increase clarity or just volume? Are model-generated summaries hiding disagreement? The company should know where AI sits in the written operating layer before it becomes invisible.

A strong audit produces a short improvement list. Maybe the company needs a decision memo template. Maybe it needs fewer memos and better decision logs. Maybe it needs comment rules. Maybe it needs an artifact taxonomy. Maybe it needs leaders to stop asking for decks when they need decisions. The fix should target the bottleneck, not copy another company's writing culture.

The best written operating cultures feel lightweight because the discipline is well placed. They do not require a memo for everything. They require the right artifact when the decision deserves memory, debate, ownership, or review. They make it easier to decide, easier to execute, and easier to learn.

The final question is blunt: does writing make the company more honest? If it does, the operating culture is working. If it only makes the company sound more organized, it is probably another layer of theater.

For example, a failed audit might reveal that product decisions live in Slack threads. Pricing decisions are justified in decks but not logged. The CEO remembers why a segment was deprioritized, but the new sales leader does not. AI summaries circulate without source links. Comment threads contain objections, but no resolution note says what changed. The company has plenty of writing and very little operating memory.

A healthier audit looks different. Major decisions have owners and dates. Tradeoffs are findable. Old assumptions can be reviewed. Teams know when to use a memo versus an FAQ. Comments are labeled by risk and blocker status. AI-assisted documents preserve sources. Meetings spend less time reconstructing context. New leaders can read the decision trail and understand how the company thinks.

For example, a roadmap audit might find the memo that chose enterprise admin reporting over individual-user automation, the comments from sales and support, the assumption about renewal risk, and the review date for adoption. A pricing audit might find the decision owner, the migration options, the grandfathering rule, the FAQ used by account teams, and the post-launch churn review. That is what operating memory looks like in practice.

The audit should end with one or two repairs, not a cultural transformation program. Add a decision-rights block to every memo. Create a small decision log. Define five artifact types. Require evidence links in AI-assisted memos. Introduce a resolution note after review. Small standards, applied consistently, usually beat a grand writing initiative.

The scoring can stay simple: missing, inconsistent, or reliable. Missing means the artifact or rule does not exist. Inconsistent means it exists when a strong operator remembers. Reliable means the organization can count on it during normal work. That scale is enough to show where written culture is helping and where it is mostly vibes.

Evidence note: this post uses local content-system, executive-communication, and operating-cadence framing, plus public written operating examples including https://handbook.gitlab.com/, https://adr.github.io/, and https://www.aboutamazon.com/news/company-news/amazons-original-1997-letter-to-shareholders.

This is part 10 of 10 in Decision Memos and Written Operating Culture.