---
title: "Dock for founders: roadmap-memo workflow with attributed CTO and product review"
excerpt: "An agent reads Linear, Notion, and Slack signals, drafts a narrative roadmap memo in Dock, and routes it to the CTO and Head of Product. Every edit is attributed."
author: mei
category: Use Cases
date: "2026-05-30"
---

Founders write roadmap memos by hand because the inputs are scattered: Linear has the engineering reality, Notion has the strategy doc, Slack has the customer voice. An agent can assemble the draft. The decision still belongs to the CTO and the Head of Product. Dock holds the memo as a structured artifact so the agent draft, the two reviewers, and the final version sit in one row with attribution intact. See [Dock for founders](/blog/dock-for-founders) for the full pillar.

Linear, Notion, and Slack stay the system of record for the raw data. Dock is the system of record for what the AGENT INTERPRETS. Each Dock row carries a pointer back to the platform record, agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state.

## The roadmap-memo surface

| Memo | Source signals | Agent draft | CTO review | Head of Product review | Status |
|---|---|---|---|---|---|
| Q3 platform memo | Linear PROJ-841, Notion strategy/v7, #cs-signals (47 msgs) | mei drafted 1,820 words, 3 bets | priya approved with edit to bet 2 | jordan approved as-is | Published 2026-05-29 |
| Pricing v2 memo | Linear PROJ-902, Notion pricing-research, #revenue (22 msgs) | mei drafted 1,140 words, 2 bets | priya requested rescope of bet 1 | jordan deferred to CTO | Revising |
| Mobile bet memo | Linear PROJ-915, Notion mobile-brief, #mobile-beta (88 msgs) | mei drafted 1,650 words, 4 bets | priya approved | jordan flagged bet 3 risk | In review |

Each row points back to the Linear project ID, the Notion page slug, and the Slack channel range the agent read. Reviewer identity is signed at edit time. The architecture is the same one we describe in [Cloud 2.0 for product](/blog/cloud-2-0-for-product).

## One worked workflow

The founder asks for a Q3 platform memo on Friday morning. The agent reads the active Linear project, the latest Notion strategy doc revision, and the last two weeks of `#cs-signals`. It drafts a memo with three bets, each tied back to the source IDs. The row enters CTO review. Priya edits bet 2 to tighten scope, signing the edit. The row advances to Head of Product. Jordan approves. The memo publishes to the Notion strategy space with a Dock-row backlink. If a Linear ticket changes after the draft, the agent re-fetches and flags drift in the row before publish. The pattern follows [agent collaboration primer](/blog/agent-collaboration-primer).

## Why it matters

Founders lose the audit trail when memos move through DMs and ad-hoc Google Docs. A roadmap bet that ships six months later is hard to trace back to the customer signals that motivated it. Dock keeps the chain visible: source IDs, agent draft, two reviewer signatures, publish event. Marty Cagan argues product teams should replace feature roadmaps with outcome narratives and supporting evidence ([SVPG](https://www.svpg.com/the-alternative-to-roadmaps/)). First Round Review documents how product roadmaps fail when founders cannot show the reasoning behind each bet ([First Round Review](https://review.firstround.com/articles/product-roadmap/)). Attributed memos solve both problems. Reviewer signatures rely on the identity model in [agent identity](/blog/agent-identity).

## Start the workflow

Open Dock, point the agent at one Linear project, one Notion strategy page, and one Slack channel, and ask for a draft. Review the row. Sign it. See how identity binds to each edit in [agent identity lifecycle](/blog/agent-identity-lifecycle).

## FAQ

**Does Dock replace Linear, Notion, or Slack?**
No. Linear holds tickets, Notion holds docs, Slack holds messages. Dock holds the memo the agent drafted, the source pointers, and the reviewer chain. The platforms stay the source of truth for their own data.

**What if the Linear project changes after the agent drafts?**
The agent re-fetches Linear via API before publish and flags any ticket whose state or scope changed since the draft. The reviewer decides whether to re-review or proceed.

**Who can approve a roadmap memo?**
The row defines two named reviewers, in this case the CTO and the Head of Product. Both signatures are required before status flips to published. Other readers can comment but cannot approve.

**How is agent attribution kept distinct from human edits?**
Every edit carries an identity. The agent edits land as mei, signed at draft time. CTO and Head of Product edits land under their own identities, signed at review time. The row history shows the full chain. See [Cloud 2.0 for product](/blog/cloud-2-0-for-product) for the underlying model.