reph

Templates · Product

Roadmap template

Now / next / later themes with a timeline

Start with this template →Sign in

Opens on reph with the template ready to start. No account needed; sign in to keep your document.

Use it when

You need to show leadership and adjacent teams what this area is building now, next and later, and what it is not doing

Who it's for

Product managerExecutiveManager

Filled example

The template filled in for a made-up company, so you can see what good looks like.

Collaboration roadmap, 2027

Author: Grace Mwangi · Date: 2026-10-01

Vision

Arbor Docs becomes the place teams finish work together, not just where they store it: every review, approval and handoff happens inside the document instead of in email threads around it.

Themes

  • Review without leaving the doc: comments, suggestions and approvals people actually close
  • Know what changed: catch-up for people who were away
  • Trust at enterprise scale: permissions and audit that pass security review

Now

Initiative Outcome Owner Status
Approval workflows 30% of team docs that need sign-off get it in-app Kwame Asante In build, on track
Granular sharing roles Close the top security review objection for enterprise deals Sofia Ricci Design done, build starts Oct 14

Next

Initiative Outcome Owner Status
"What changed since you last looked" Returning readers catch up in under a minute Kwame Asante Scoped
Comment assignment and due dates Open comments older than 14 days drop by half Grace Mwangi Scoped

Later

Initiative Outcome Owner Status
Exportable audit log Pass SOC 2 customer audits without custom reports Unassigned Idea
Cross-doc review dashboards Managers see every pending approval in one place Unassigned Idea
Mermaid diagram (drawn as a picture in reph)
gantt
    title Collaboration roadmap 2027
    dateFormat  YYYY-MM-DD
    section Now
    Approval workflows     :active, a1, 2026-10-01, 60d
    Granular sharing roles :active, a2, 2026-10-14, 75d
    section Next
    What changed since you last looked :b1, after a1, 45d
    Comment assignment     :b2, after a2, 40d
    section Later
    Exportable audit log   :c1, after b1, 60d
    Review dashboards      :c2, after b2, 60d

Not doing

  • Real-time video inside documents: low demand, high cost, and good integrations already exist
  • A separate project management board: we link to the tools teams already use
  • Offline editing on web before 2027 H2

Dependencies & risks

  • Granular sharing depends on the Identity team's new permission service, due mid-November. A slip moves the Next column by the same amount.
  • One open senior engineer role; if unfilled by January, comment assignment slips a quarter.
  • Approval workflows need legal review of the e-signature wording before GA.

The template

Show the blank template

Roadmap

Author: [your name] · Date: [date]

Vision

Where this product/area is headed over the next year or two: the thing the themes below are all in service of.

Themes

The 3-5 problem areas the roadmap is organized around, not a list of features.

Now

In active development this quarter.

Initiative Outcome Owner Status

Next

Scoped and prioritized, starting once Now work lands.

Initiative Outcome Owner Status

Later

Directionally right, not yet scoped. Expect this section to change the most.

Initiative Outcome Owner Status
Mermaid diagram (drawn as a picture in reph)
gantt
    title Roadmap timeline
    dateFormat  YYYY-MM-DD
    section Now
    Initiative A :active, a1, 2026-01-01, 30d
    section Next
    Initiative B :b1, after a1, 45d
    section Later
    Initiative C :c1, after b1, 60d

Not doing

Explicitly declined ideas. This kills the "did you consider X" question before it's asked.

Dependencies & risks

What could slip this: other teams, platform work, hiring.

Questions

How far out should Later go?
Six to twelve months, and it is fine if it is vague
Are the dates commitments?
Only Now dates are. Next and Later are direction, not promises
How often should it change?
Review it monthly and rewrite it each quarter

Fill it with your agent

Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.

Find my reph doc "Roadmap" with search_docs, then read it with read_doc. Draft themes and the Now, Next and Later tables from the linked strategy doc, OKRs, sprint boards and top customer requests, each initiative an outcome rather than a feature name, and match the gantt dates. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (initiatives with no owner, cross-team dependencies) with add_comment quoting that section's heading line, then call request_review with a one-line summary.

Related templates

Analytics request

Brief for a data or analytics request: the decision it informs, the exact question, metric definitions, segments, timeframe, sources, due date and output format

Product managerResearcherMarketerExecutiveOperationsAnyone

Experiment (A/B) plan

Hypothesis, variants, metrics, sample size and decision rule

Product managerResearcherEngineer

Feature brief

Short brief aligning team on a feature before design

Product managerDesignerEngineer

Launch checklist

Everything to ship a feature: eng, docs, support, marketing

Product managerManager

One-pager

A single-page pitch for an idea: problem, solution, why now

Product managerFounderExecutive

PRD / requirements doc

Problem, users, requirements, success metrics and scope for a feature

Product managerEngineerDesigner

Start with this template →Sign in