Data strategy service line - five-document playbook
Applies to: Every Brain Forge client engagement packaged as data strategy (discovery, warehouse / analytics delivery, exec communication).
Canonical CE plan: docs/plans/2026-05-07-data-strategy-five-documents-ce-plan.md
Markdown templates (iterate here first): templates/ — each includes exemplar links plus sample text for form and substance.
Why five documents
One combined memo mixes engineering depth, champion alignment, and executive narrative. Champions cannot filter or forward it; engineering still needs a PRD. Split into five audience-specific artifacts with explicit handoffs.
The five layers
| # | Artifact | Audience | Job to be done |
|---|---|---|---|
| 1 | Domain PRD / build | BF engineering / modeling | Sources, metrics, phased delivery plan; discovery through build |
| 2 | Champion synthesis | Client champion (e.g. Shivani-level) | Themes, open questions, alignment — no internal ticket noise for execs |
| 3 | VP / executive memo | Client VPs | Lightweight narrative, parallel workstreams, next steps |
| 4 | Deck prep | BF + champion before readout | Full bullets, chart intents, speaker notes before Slides |
| 5 | Google Slides | Same as Doc 3 audience | Visual delivery only; zero net-new facts vs Doc 4 |
Pilot exemplars (Element / LMNT): Linked from the CE plan — use as quality reference when filling templates for other clients.
Bridge (not a sixth Google Doc)
Before Doc 3 is final, engineering perspective + strategy perspective align with the champion on what reports upward. Record outcomes inside Doc 2 or Doc 3 draft, or short-lived working notes marked discard after merge.
Doc meta block (required on every copy)
Each initiative’s five files must cross-link:
- Client / domain, layer number (1-5), sibling URLs, owner, last reviewed, audience label.
GTM and marketing (MC plan)
Messaging for data strategy deals should reflect this playbook: five artifacts, not “the memo.” Case studies, outbound, and proposals reference:
- This README
- The CE plan
- Vault templates as the repeatable product
Sales and marketing: align language with Doc 2 (champion) vs Doc 3 (VP) naming when describing deliverables.
Updating templates from Google Docs
- Open the client’s or pilot Google Doc exemplar.
- Paste section body into the matching
templates/*.mdfile (preserve headings). - Replace client-specific names with placeholders:
{{client}},{{champion}},{{domain}}. - Open a PR; ship Google workspace template updates when the markdown stabilizes.
Files
| File | Purpose |
|---|---|
templates/README.md | Template index |
templates/01-domain-prd-template.md | Doc 1 |
templates/02-champion-synthesis-template.md | Doc 2 |
templates/03-vp-executive-memo-template.md | Doc 3 |
templates/04-deck-prep-template.md | Doc 4 |
templates/05-google-slides-checklist.md | Doc 5 handoff |
Execution checkpoint
- Current state: templates for layers 1-5 are live and include exemplar links + sample text.
- Remaining: set master Slides URL and continue syncing exemplar prose from Google Docs into markdown as it matures.