Workflow Domain 03 — Written Memory & Specifications

Keep Documents in Motion

A team wiki fails the moment contributors stop trusting that the page they found via search reflects current reality. Collaborative documentation requires lifecycle states just as rigorous as software code.

Separating transient drafts from durable knowledge

One of the most common sources of friction in remote organizations is mixing two distinct document types in the same folder hierarchy: transient working drafts (such as a Q3 feature pitch or a campaign brainstorm) and durable standard operating procedures (such as how to run a database migration or onboard a contractor).

When transient drafts and permanent policies sit side by side in Notion, Confluence, or Google Drive without metadata, search results return outdated assumptions from two years ago alongside active rules. New hires quickly learn they cannot trust the wiki and revert to pinging senior staff in chat.

Transient: The RFC / Spec

Has a clear author, a list of required approvers, a decision deadline, and a status badge (Draft, In Review, Approved, Superseded). Once implemented, it is frozen as historical context.

Durable: The Playbook

Describes how a recurring process works today. Requires an assigned "Steward" and an automated 90- or 180-day verification date to confirm accuracy.

Two colleagues reviewing an architectural decision record on a tablet and notebook in a bright studio — Documenting the rejected alternatives inside a specification prevents teams from relitigating settled questions months later.

Comparing document collaboration platforms

Every major document platform handles real-time multiplayer cursors well. The meaningful differences lie in how they structure relationships between documents, permissions, and external task trackers:

Platform	Core Architecture	Strength in Handoffs	Primary Failure Mode
Notion	Block-based pages combined with relational databases and filtered views.	Metadata properties (Status, Owner, Sprint Link) live directly at the top of every doc.	Over-engineered workspace templates that become slow and confusing to navigate.
Confluence	Hierarchical spaces with deep Jira integration and enterprise permission controls.	Highlighting text in a spec creates a linked Jira issue in two clicks with full trace back.	Stale nested page trees when space administrators do not enforce archival rules.
Google Docs / Drive	File-and-folder model with industry-standard suggestion mode and margin comments.	Low-friction external sharing with clients, legal counsel, and vendors; unmatched redlining.	Files scattered across personal drives unless Shared Drives and naming conventions are enforced.
Coda	Documents fused with spreadsheet formulas, interactive buttons, and two-way Packs.	Allows teams to build custom approval tables and trigger external API actions inside a doc.	Steeper learning curve for authors building complex relational doc schemas.

The Decision Log: Stopping circular debates

When a project changes hands from product discovery to engineering delivery, or from implementation to customer support, the receiving team inevitably asks: "Why did we build it this way?"

Adopting lightweight Architecture Decision Records (ADRs) or Decision Logs inside your document tool eliminates circular debates. Every significant decision entry needs only four short fields:

Context: What constraint or user problem forced us to make a choice?
Options Considered: What were the two or three viable paths we evaluated?
Decision & Owner: Which path did we commit to, who made the final call, and on what date?
Consequences: What trade-offs or follow-up tasks did we knowingly accept?

When this record is linked directly inside the parent epic in Linear, Jira, or Asana, any contributor joining the project months later inherits the full reasoning without scheduling a catch-up call. Next, see how to surface these states automatically in Evaluate Dashboards and Automation.