Skip to content

Roadmap Stakeholder Update

Example prompt: "Every other Friday afternoon, summarise where we are on each item in our Linear roadmap — what shipped this fortnight, what slipped, what's coming next — and draft a stakeholder update in Notion with a short Slack heads-up to the #leadership channel saying it's ready to read."

The Problem

Leadership and the wider business want to know what the product team has shipped, what is in flight, and what is coming next. The honest answer changes meaningfully every two weeks. Writing the update is a 90-minute job — open Linear, click into each initiative in Now, Next, and Later, work out what has moved since the last update, decide which movements are worth raising, and write it in a register that a non-engineer will read. So it gets written in a hurry every other Friday, or it slips a fortnight, and the absence becomes a small drum the CEO eventually starts beating about.

How GloriaMundo Solves It

We build a workflow that runs every other Friday afternoon. An integration step reads the current state of every initiative in the Linear roadmap across Now, Next, and Later, including status, target date, and recent activity. A state step recalls the snapshot from the previous run so the workflow can diff and identify what has moved — shipped initiatives, slipped target dates, items promoted from Next into Now. An LLM step drafts the update in stakeholder-friendly language: a "Shipped" section with one line per completed initiative, a "Now" section with status colour and a sentence on each, a "Next" section with the working ETA, and an "On the horizon" section for Later. An integration step creates the draft as a new page in the "Roadmap Updates" Notion space. A second integration step posts a short Slack message to #leadership with the link and the headline counts. The state step then writes the current snapshot back for the next fortnight's diff. Glass Box preview shows the draft and the Slack message before either is sent.

Example Workflow Steps

  1. Trigger (scheduled): Runs at 16:00 every other Friday.
  2. Step 1 (integration): Read all initiatives from the Linear roadmap across Now, Next, and Later swimlanes with current status and target dates.
  3. Step 2 (state): Recall the snapshot saved at the previous run.
  4. Step 3 (code): Diff current against previous — produce shipped, slipped, promoted, new, and unchanged buckets.
  5. Step 4 (LLM): Draft the update in stakeholder-friendly prose with sections for Shipped, Now, Next, and On the horizon.
  6. Step 5 (integration): Create the draft as a new page in the "Roadmap Updates" Notion space.
  7. Step 6 (integration): Post a Slack message to #leadership with the link and headline counts.
  8. Step 7 (state): Write the current snapshot for next fortnight's diff.

Integrations Used

  • Linear — source of roadmap initiatives, statuses, and target dates
  • Notion — where the fortnightly stakeholder update is drafted for review
  • Slack — heads-up to the leadership channel that a fresh update is ready

Who This Is For

Heads of product and senior PMs at scale-up SaaS companies that run a public-to-the-business roadmap in Linear and owe leadership a regular written update. Especially useful where the product team is small and the update is one PM's job that competes with all their other Friday work.

Time & Cost Saved

A roadmap update written from scratch every other week is 60-90 minutes of clicking through Linear and rewriting status notes. Over a year that is 30-45 hours, plus the cost of the fortnights it skips because the PM was firefighting. The workflow assembles the diff and drafts the prose; the PM's time goes into the editorial pass on tone and the calls about what to do about anything red.