Strategy Consulting Visualization

# Strategy Consulting Visualization

Use this to turn any content into a clear, professional visual: board slides, memo exhibits, market maps, benchmarks, performance bridges, timelines, process flows, reports, proposals, or training material. It aims for strategy-consulting clarity without implying affiliation with any firm.

Do not use it for decorative art, brand campaigns, or regulated financial, medical, or legal conclusions without source verification. If the user wants a final chart but has not supplied enough data to check labels and scales, ask first.

## Workflow
1. **Name the job.** What decision or question should this visual answer for its reader?
2. **Triage the input.** Map prose, data, a process, or a question to a pattern family.
3. **Pick a document profile.** Board deck, pre-read, one-pager, or training sets canvas, density, and tone.
4. **Write the insight headline.** One proposition that answers the reader's question. One answer or one tension, never several claims joined by "and".
5. **Choose the pattern.** Start from the comparison type: change over time (time series), parts to whole (waterfall, bridge), ranking (benchmark table), relationship (scatter, 2x2), flow (process, funnel), schedule (gantt), status (KPI scorecard). Covers, agendas, and dividers are connective slides; spend headline effort on content slides.
6. **Apply the style system.** Restrained colors, one highlight color for the point, a word budget per slide. If text does not fit, cut words or split the slide. Never shrink type.
7. **Produce the spec.** A structured spec, diagram-as-code, or an image prompt. Say clearly whether a pattern will render or is spec-only.
8. **Score it.** Check: headline is a claim, chart supports exactly that claim, labels and units are present, source line is present.
9. **Flag risk.** Missing data, unverifiable claims, source-sensitive assumptions, trademark-sensitive wording.
10. For high-stakes or broad-audience work, run one more pass for overclaims, jargon, and accessibility.

## Output contract
- Strategic question
- Insight headline
- Recommended pattern and why
- The spec (axes, series, labels, annotations, source line)
- Implication or "so what" line
- Open issues and assumptions

Adapted from @kgraph57: https://github.com/kgraph57/mckinsey-style-visualization-skill