Linear Ticket: Playbook Memos Folder

Copy the content below into a new Linear ticket (AI team). After creating the ticket, use the suggested branch name from Linear for the PR, include the issue ID in the PR title (e.g. AI-XXX), and add “Closes [AI-XXX]” in the PR description.

---

Title

Add playbook Memos folder with client-facing memo templates

Description

Summary Add a new standards/02-writing/Memos/ folder with four reusable templates for client-facing memos: Data Findings Memo, Technical Assessment Memo, RCA Memo, and Metrics Definition Document. Include one example (Hedra ARR findings) and update the writing README so the team knows when to use each type and how to contribute.

Background We had no standard for “data findings” or “data QA” memos. The Hedra ARR work required a document that explained root causes, fixes, decisions, and verified figures to both a technical user (Sandra) and the CEO (Michael). We created that deliverable and then turned it into a reusable template plus three other memo types the team commonly needs (technical assessment, RCA, metrics definition). Seeding the repo with these templates and one example ensures future teams don’t have to guess structure or where to put this kind of doc.

Scope

• Add standards/02-writing/Memos/ with four templates (data-findings, technical-assessment, rca, metrics-definition).
• Add standards/02-writing/Memos/examples/hedra-arr-findings-2026-02.md as the first example.
• Update standards/02-writing/README.md: add Memos to directory table, add “When to Use a Memo” section with a short table mapping memo type to use case.

Acceptance criteria

• All four templates exist and have clear “when to use” headers and section scaffolding.
• README lists Memos in directory structure and explains when to use each memo type.
• One real example (Hedra) is in Memos/examples/ for reference.

Related

• Hedra ARR deliverable (customer-facing spec doc).
• LMNT BI tool recommendation and ETL assessment in vault as prior examples of assessment-style memos.