# Technology Roadmap Diagram Experiment

Task: DIAGRAM-ROADMAP-EXPERIMENT

## Source Inventory

- `roadmap-technology-component.pdf`: one-page technology component roadmap with a title band, legend, month columns, a left-side product lane, and rounded initiative cards positioned by time span.

## Element Contract

- Audience: delivery leads and technical stakeholders planning releases and dependencies.
- Reading flow: month grid left to right; cards occupy the months where work happens.
- Layout: single product lane with month columns January through June.
- Nodes: initiative cards with title, start/end date, dependency note, and component icons.
- Visual constraints: cards must align to month columns, legend must stay separate from the schedule, and card shadows should not imply grouping.

## Prompt Used

Create a technology component roadmap diagram as SVG.

Use a title block on the upper left, a compact legend on the upper right, and a
timeline grid below. The grid has a left lane label and six monthly columns:
January, February, March, April, May, June. Use rounded initiative cards placed
inside the grid by rough date span. Include these initiatives:

- Environment Set-Up, January 15 to February 1, dependency Environment.
- Account and Contact Management, February 5 to March 15, dependency Environment.
- Custom Lead Conversion Process, February 15 to April 10, dependency Leads.
- Opportunity and Quote Management, March 15 to April 15, dependency Accounts, Contacts, Leads.
- CPQ Integration, March 20 to April 25, dependency Environment.
- Forecasting, April 20 to May 15, dependency Accounts, Contacts, Leads.
- Territory Management, April 15 to May 10, dependency Accounts, Contacts, Leads.

Use icon dots inside each card to show component categories. Align every card to
the relevant month region. Re-evaluate text fit, timeline alignment, overlap,
and legend spacing after rendering.

## Evaluation Findings

- Roadmaps need column-grid fidelity more than connector fidelity; small card shifts can change perceived timing.
- Card density becomes a problem when initiatives overlap in the same months; vertical staggering must be part of the prompt.
- Icons work as metadata, but they need a legend and consistent spacing.
- A future master rule should require roadmap card start/end alignment checks against the declared time axis.