Brainforge Knowledge

data-source-memo-executive-style-playbook

3 min read

Playbook: Data Source Memo (Executive Human Style)

Version: 0.5
Last updated: 2026-04-08
Audience: LLM agents and humans creating client-facing or leadership-ready data source memos.

Purpose

Create a one-page memo that reads like a human executive wrote it. The output should be simple, clean, and easy to scan.

When to use

Use this playbook when:

  • someone asks for a data source memo
  • someone asks for a one-pager on what a schema or share contains
  • someone asks what a new source unlocks and what questions it can answer

Do not use this playbook when:

  • the user asks for a detailed schema audit or table-by-table technical inventory

Service line / subservice

FieldValue
Service lineData Platform
Primary subserviceAnalytics and BI
NotesWriting standard for source-overview memos

Approval-before-execution pipeline

No approval gate is required for drafting. If publishing externally, ask the owner for final sign-off.

Scope

In scope

  • one-page narrative memo
  • executive context, business value, and practical questions
  • simple structure with headings and plain text

Out of scope

  • SQL snippets
  • code-style formatting
  • long link sections and depth-reference blocks
  • table-by-table field dictionaries

Prerequisites

RequirementNotes
Source understandingMust know the major domains covered by the source
Confirmed factsDo not guess counts, entities, or definitions

Inputs

InputExampleNotes
Client nameLMNTRequired
Source nameEmerson LMNT shareRequired
Coverage by domainRetailer order-to-cash (B2B), 3PL, Walmart, TargetRequired
Key business outcomesPipeline, fulfillment, AR, sell-throughRequired

Workflow

Step 1 - Set the memo frame

Start with a title, then one compact metadata line, then a short summary paragraph. Use this format for metadata: “Client: | Data source: | Date: ”.

Step 2 - Separate old vs new

State what is already documented in one short section. Then describe newly available coverage by business domain. Include one plain-language qualifier line under “What is newly available” to clarify that this means newly available in the Snowflake warehouse from the latest ingestion, not newly created in source systems.

Step 3 - Explain value in plain language

Write a short section on what the source unlocks for decisions and reporting.

Terminology

Use terms consistently:

  • Retailer order-to-cash (B2B): orders, invoices, shipments, and receivables with retailers.
  • Retail sell-through: retailer sales and inventory performance to end customers.

Step 4 - Add practical business questions

Include five to eight real questions the source can answer. Keep them direct and business-facing. Format this section as bullet points for executive scanability.

Step 5 - Close with next step

End with one recommended next action. Add one short implementation line with owner and timing.

Style rules (required)

  • Use heading, subheading, and plain text only.
  • Avoid code formatting, inline backticks, and technical markup unless explicitly requested.
  • Avoid depth-reference sections and extra links unless explicitly requested.
  • Keep tone direct, neutral, and human.
  • Do not use filler language, hype language, or AI-style phrasing.
  • Keep total length close to one page.
  • Keep top metadata compact in one plain-text line; do not use separate metadata headings.
  • Use bullet points for “Questions we can now answer.”
  • Add a one-line scope qualifier under “What is newly available” if there is any ambiguity.
  • Add owner and timing in the final next-step section.
  • Prefer “retailer order-to-cash (B2B)” over “wholesale commercial” unless the user explicitly requests wholesale wording.

Failure modes / gotchas

  • Overly technical language makes the memo hard for executives to use.
  • Too many references and links make the memo feel machine-generated.
  • Per-table inventory on the one-pager makes the document noisy.
  • Vague claims without concrete business questions reduce trust.

Example implementation

  • knowledge/clients/lmnt/resources/DATA_SOURCE_MEMO_EMERSON_LMNT_425.md
  • knowledge/standards/02-writing/data-source-discovery-memo-new-share-playbook.md — longer table-level discovery memo (not a one-pager)
  • knowledge/standards/02-writing/data-source-discovery-memo-update-playbook.md — additive updates to an existing discovery memo
  • knowledge/clients/lmnt/resources/data-source-immersion-one-pager-template.md
  • knowledge/standards/02-writing/PLAYBOOK_SCAFFOLD.md

Graph View