3.1 System of Record: Async + Written Culture

Writing is not an administrative task; it is the primary tool for clear thinking. In a complex manufacturing environment, relying on casual verbal communication creates systemic reliability issues. Spoken words vanish; written text is permanent and actionable.

This standard merges an Async-First workflow (respecting focus time) with a Written Culture (ensuring operational transparency). It defines how critical information moves across the organization without breaking flow.

The Core Principle: “Write it Down”

Casual verbal agreements, hallway decisions, and fragmented chat threads are ephemeral. They are not standard operating procedure, and they do not constitute an official corporate decision.

The Standard: A business or engineering decision becomes valid once it is formally documented in the System of Record (Corporate Handbook, Task Manager, or ERP).
The Logic: The act of writing prompts intellectual clarity. Vague instructions cannot be precisely written. If a problem cannot be written down clearly, it indicates the problem is not yet fully understood.

The Decision Matrix: Write vs. Talk

Communication defaults heavily to Async (Written). Sync (Meetings) is used as an intentional channel for specific interactions.

The Context	The Mode	The Channel	The Reason
Status Update	Async	Task Manager / Live Dashboard	Reading is significantly faster than listening to a spoken update.
Information Sharing	Async	Formal Memo / Wiki	Sharing formal documents is more efficient than a slide presentation in a room.
Simple Decision	Async	Project Comments	Reversible actions need immediate speed.
Complex Debate	Sync	Video / In-Person	Nuance is quickly lost in text. Debate live, decide, then immediately write it down.
Emotional / Personnel	Sync	Video / In-Person	Always give sensitive personal feedback face-to-face.
Emergency (Line Down)	Sync	Phone	Immediate, high-stakes intervention is required.

Channel Hygiene: The 4-Layer Protocol

Misplaced information creates operational noise. Utilizing the appropriate channel for the right content ensures clarity. Communication is organized into four layers.

1. The Knowledge Base (The Library)

Content: Policies, SOPs, Incident Post-Mortems, and Strategic Plans.
Lifespan: Permanent.
The Protocol: This is the Source of Truth. When an operational policy is not written here, it does not exist and cannot be followed.

2. The Task Manager (The Engine)

Content: Action items, engineering bug reports, active project status, “Exactly Who does What by exactly When.”
Lifespan: Until the specific task is definitively Done.
The Protocol: Internal Work = A Ticket. Critical corporate projects must not be managed via email. Email threads obscure accountability; organized tickets track it clearly.

3. Email (The External Bridge)

Content:
- External: Formal communication with Suppliers, Customers, Auditors, and Legal counsel.
- Formal: HR job offers, Resignations, Board Resolutions.
Lifespan: Long-term archival (The Legal Audit Trail).
The “Forward-to-Task” Workflow: When a client emails a tactical request (e.g., “Change the Gerber file tolerances”), that email must be forwarded to the Task Manager to create a ticket. An email in a personal inbox is a task visible only to one person; a tracked ticket is visible to the entire system.

4. Instant Messenger (The Shop Floor)

Content: Rapid coordination, quick unblocking of minor issues, social touchpoints.
Lifespan: Ephemeral (Disappears functionally in days/weeks).
The Protocol: A messenger app must not be used for architectural decisions or policy changes. It is used for pointing to the work, not for storing the work.

The “Where to Write” Matrix

Communication Type	The Channel	Why?
Project Update / Execution Task	Task Manager	Clear accountability, deadlines, transparent history.
Client / Supplier Communication	Email	Universal standard, clear legal audit trail.
Formal / Legal Notice	Email	Official corporate record.
Core Policy / SOP	Wiki	Single source of truth. Clear version control.
”Quick Question”	Messenger	Tactical speed. Low barrier to entry.
Crisis / Line Down	Phone	Interrupt-driven. Fast response required.

The Definition of Done for Communication

A message is considered complete when it clearly triggers an action. Vague requests generate operational delays.

The “DoD” (Definition of Done) Checklist for Internal Requests:

Direct Responsible Individual (DRI): Is explicitly named (@Name).
The Action: Uses a specific verb (Approve, Review, Fix, Ship).
The Deadline: States a specific date and time.
The Source: Contains a direct hyperlink to the relevant document or ticket.

Examples:

❌ Poor (The “Ping”): “Can someone look at the inventory file? It looks wrong.”
- The Result: Unclear ownership. The Bystander Effect takes over.
✅ Required (The Request): “@John, please audit the ‘Q3 Capacitor Inventory’ (Link) for discrepancies. Please update cell C4. Due by 14:00 today.”
- The Result: Clear owner, clear action, clear deadline.

Writing Standards: Low Context vs. High Context

Operations exist in a “Low Context” culture. The reader must never be assumed to inherently know the background of a request.

BLUF (Bottom Line Up Front): The exact “Ask” or conclusion must be placed in the very first sentence.
No “Hello” Loops: Messaging “Hi” and waiting for a reply is prohibited. The entire request must be sent immediately.
Structural Formatting: Use bullet points and bold text to highlight key information. Formatted text is much easier to parse.

The Standard Artifact: The One-Page Proposal

When proposing a new idea, a formal 1-Pager must be written. If the idea cannot be clearly articulated on a single page, the concept requires further thought before presentation.

The Proposal Template:

Title: [Project Name]

Owner: [Name] | Date: [Date]

1. The Problem (The “Why”):

Current State: (Must be data-backed).
Operational Impact: (Hard Cost / Specific Risk).

2. The Solution (The “What”):

Proposal: (Brief, technical description).
Scope Boundaries: (Exactly what is in scope / Exactly what is out of scope).

3. The Cost & Risk:

Resources Required: (Capital Budget / Headcount).
Downsides: (What are the immediate risks?).

4. The Executive Ask:

[Approve / Reject / Require Immediate Feedback]

The “24-Hour” Etiquette

Async does not permit continually ignoring requests. It dictates that responses are provided efficiently on a managed schedule.

The Standard SLA: A direct message or mention must be acknowledged within 24 hours (Business Days).
The Acknowledgment: A simple emoji reaction (👀 or ✅) is perfectly sufficient to communicate that the request has been seen and added to the queue.

Final Checkout: System of record: async + written culture

The Requirement	The Standard
No “Ghost” Decisions	When a major decision happens in a Sync meeting, it must be posted to the Knowledge Base or Task Manager.
No “Hello”	Send the full, detailed request in the very first message.
Link, Do Not Attach	Send direct links to live cloud docs, not static file attachments (to preserve version control).
The “BLUF” Rule	The specific “Ask” is always the first sentence.
Proposal Format	All new initiatives follow the 1-Page Template.