Stakeholder updates fail when nobody owns the narrative. The agent can read every Asana task, Notion spec, Slack thread, and email faster than any PM, but tone and framing are judgment calls. Dock splits the work: the agent drafts from project signals, a named narrative owner reviews voice, and the row stores both the draft lineage and the reviewer decision. Stakeholders receive prose. The PMO sees who wrote which sentence and why.
Asana, Notion, Slack, and email 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 Stakeholder Updates surface
One row per cycle per project. The narrative owner column is a human name, never a role.
| Project | Cycle | Asana milestone | Slack risk thread | Draft narrative | Narrative owner | Tone review | Sent at |
|---|---|---|---|---|---|---|---|
| Atlas billing migration | 2026-W22 | asana://1207/m44 on track | #proj-atlas one blocker | "Migration is on track. One blocker resolved Tuesday." | Priya Shah | approved, softened "delay" to "shift" | 2026-05-29 16:02 |
| Helios mobile rewrite | 2026-W22 | asana://1211/m12 slipped 4d | #proj-helios scope debate | "We are pulling the iOS beta forward and deferring tablet." | Marcus Liu | rewrite: lead with customer impact | pending |
| Pegasus data platform | 2026-W22 | notion://specs/pegasus-v3 signed off | #proj-pegasus quiet | "Spec is locked. Build starts Monday." | Priya Shah | approved as drafted | 2026-05-29 09:14 |
The narrative owner is a Dock person, not a job title. When Priya rotates off, the row history shows every prior owner. See agent identity and agent identity lifecycle for how attribution survives reassignment.
Worked workflow: Atlas weekly update
Monday at 14:00 the PM agent runs the Atlas cycle. It re-fetches the Asana milestone, scans seven days of #proj-atlas for risk language, pulls Notion spec comments, and reads inbound email. It writes a 180-word draft and assigns Priya.
Priya opens the row, sees the source pointers, and clicks through to the Slack thread the agent flagged. She changes "delay" to "shift" because the pilot date did not move. She approves. The agent sends the email via the project distribution list and writes the send receipt back to the row.
If Priya rejects, the agent opens a comment on the row and waits. The pattern follows the agent collaboration primer: every handoff is a row, every decision has a name on it.
Why this matters
PMI's 2023 Pulse of the Profession rated communication a top power skill and tied stakeholder engagement to on-time delivery. Gartner's PMO research found 68 percent of stakeholders perceive their PMO as bureaucratic, and that generic status reports drive that perception. The fix is not more updates. It is updates with a named human voice and a visible trail to the source. Dock makes the trail part of the artifact. See Cloud 2.0 for product and the PM pillar for sales, ops, and exec-report variants.
The narrative owner pattern also closes the audit loop. When a stakeholder asks who decided to call this a shift instead of a delay, the row answers in one click. See Cloud 2.0 for product for the architectural shift this depends on.
Start a Dock workspace for your PMO
FAQ
Does the agent send updates without review? No. The send action is gated on narrative-owner approval. Unreviewed drafts stay in the row.
What if the narrative owner is out? The row stays open. Dock surfaces the pending review on the owner's backup queue, but the agent does not pick a new owner on its own.
Can the agent learn the owner's tone over time? It reads prior approved updates from the same row history. It does not train a model. The narrative owner still reviews every send.
Does this replace Asana or Notion? No. Those stay the source of truth for tasks and specs. Dock holds the interpretation layer, the narrative draft, the reviewer decision, and the send record.
