Roadmap brief

What it does

Takes raw inputs, feature requests, strategic goals, constraints, and produces a structured roadmap brief ready for a client or team review.

When to use

• After a discovery phase, going into definition
• When you need to present a product direction without a full roadmap built yet
• Before a client workshop on prioritisation

The skill

I'm going to give you a set of inputs: strategic goals, feature requests, constraints, and anything else relevant. Produce a one-page roadmap brief.

Structure it as:

1. The goal this roadmap serves. One sentence. What are we trying to achieve in the timeframe?
2. Themes. 3–4 thematic areas of work, each with a name and two-sentence description. Not feature lists.
3. Rough sequencing. Which themes come first and why? What depends on what?
4. What we're not doing. At least three things explicitly excluded.
5. Open questions. What needs to be decided before the roadmap can be confirmed?

Don't write a feature list. Don't assign dates. Keep it to a page.

Here are my inputs:

Strategic goals: [paste] Feature requests or themes: [paste] Constraints (time, resource, technical): [paste] Anything else: [paste]