Example brief used for this template
Hypothetical creation brief for this authored edition, not a historical prompt transcript. The sample answers describe the actual example rendered here.
- Purpose and audience
- A roadmap snapshot with now/next/later work, outcomes, dependencies, and confidence.
- Working context
- This fictional handover product roadmap is a planning snapshot. The horizons express order and uncertainty; they are not public delivery commitments.
- Example records
- Horizon: Now · Work: Clarify entry ownership · Outcome: Receiving teams know who updates an item · Dependency: Role agreement
Horizon: Next · Work: Improve review reminders · Outcome: Owners notice stale content · Dependency: Review-date model
Horizon: Later · Work: Explore bulk import · Outcome: Reduce setup effort · Dependency: Evidence from larger libraries
- Content decisions
- Why this order: Ownership addresses the immediate handover problem. Reminder behavior depends on a meaningful review date. Bulk import is useful only if larger libraries are a verified need.
What can change: Research, delivery effort, and operational constraints may change the sequence. Record the reason for a change rather than silently moving an item between horizons.
Review the roadmap: At the next planning review, compare each item with evidence and capacity. Keep committed work distinct from exploratory ideas so the audience understands the confidence behind the plan.
- Format and interaction
- board layout; section navigation and expandable detail where useful; matching portrait document PDF.
- Sharing and provenance
- A hypothetical example informed by Claw Me’s small-team and Agent workflows. These are not Pete’s actual clients, finances, travel plans, research results, or commitments. Keep the real adaptation private until the owner chooses to share.