Roadmap alignment

# Roadmap alignment

Use when you want to know whether the work on your roadmap supports your goals and initiatives.

## Definitions

Use these meanings consistently in every step.

- **Strategy:** The goals and initiatives defined in the current workspace, including roll-up goals and initiatives inherited from a parent workspace line
- **Roadmap:** The current page, or a roadmap or list report the user links to
- **Roadmap item:** A record that appears on the roadmap, usually an epic or a feature. Roadmap items link to the strategy through their goal and initiative fields.

## Workflow

1. Confirm the input. You need a roadmap view or a list report that includes the release and status columns. You cannot assess timing risk without these columns, so ask for them before continuing.
2. Review the strategy. List the goals and initiatives you will measure against by reference number and name.
3. Review each roadmap item. Read its description, release, status, and its links to goals and initiatives.
4. Determine alignment. Decide whether each item has clear and direct alignment with the strategy or whether the link is nominal.
5. Flag the weak items. Call out roadmap items with unclear, weak, or absent alignment. A feature with no goal or initiative link is the clearest case.
6. Highlight risk. Name the areas of misalignment that could affect product success. Look for:
   - Initiatives with no supporting work scheduled
   - Effort concentrated on one goal while others are unfunded
   - Items in a release whose timing conflicts with the initiative time frame
   - Work that supports no strategic outcome at all

## Rules

- If the roadmap or the strategy is not specified, ask short follow-up questions before proceeding
- Write for product managers and leadership. Avoid jargon.
- Focus on actionable insight. Synthesize and interpret the data rather than restating it.
- Reference every record by reference number and name
- Do not change goal or initiative links. Recommend the change and let the user apply it.
- Headers use sentence case. No em dashes, en dashes, or curly quotes.

## Output

```
## Overall assessment  
<how well the roadmap matches the strategy, in two to four sentences>  
  
## Aligned items  
| Roadmap item | Goal or initiative | Strength of alignment |  
  
## Flagged items  
| Roadmap item | Issue | Recommended fix |  
  
## Risks  
- <risk and its consequence>  
  
## Recommendations  
1. <highest value action>
```

Save the report as an artifact and share the link so the team reviews it in one place.

## Quality checks

- Every roadmap item appears in either the aligned list or the flagged list
- Every flagged item names the specific field or link to add
- Every risk states a consequence, not just an observation