/mckinsey-style-visualization-skill

name: strategy-consulting-visualization
description: Use when turning content into clear strategy-consulting visualizations, including board slides, reports, diagrams, quiet animated decks, or explicit dynamic and interactive decks with clickable evidence, scenario controls, what-if sliders, and deterministic presenter demos.

Strategy Consulting Visualization

Purpose

Use this skill to turn any content into professional visualization specs with strategy-consulting clarity: insight-led headlines, disciplined layout, accurate data, restrained design, and explicit implications. It covers board slides first, and generalizes to reports, proposals, training materials, technical diagrams, infographics, and any input that benefits from visual structure.

Fast Path

Skip the pattern-by-pattern build when the user just wants a complete, real deck or document immediately.

**Full deck** — scaffold a ready-made archetype from `templates/decks/`, then fill in the illustrative placeholders with real data:

python3 scripts/scaffold_deck.py --list                       # 6 archetypes with slide counts
python3 scripts/scaffold_deck.py board-update -o my-deck       # copies deck.json + specs/
# edit my-deck/specs/*.json with real data, keeping the pattern shapes intact
python3 scripts/build_html_deck.py --manifest my-deck/deck.json -o my-deck/deck.html

**Click-through motion presentation** — when the reader should enter a page from an overview, press the exhibit or its main number for supporting detail, and verify the claim through an operation, use the story-led presentation route. This is the preferred route for a reference-led request for うちた-style 動く資料 or クリックで深掘り. Read `references/motion-story.md` and author a small `motion.json`; the six-page Japanese example demonstrates the components:

python3 scripts/build_motion_deck.py --manifest examples/interactive-deck/motion.json -o deck.motion.html
python3 scripts/build_motion_deck.py --manifest examples/interactive-deck/motion.json --static -o deck.motion.static.html

The opening is a navigable argument, followed by evidence-led pages with one primary operation each. Exhibits and prominent numbers open a source-bearing drawer; classification sorts, comparison retains the prior shape, a slider recalculates the displayed formula, actions fill a gap, and a timeline advances through real decisions. Review the entire flow and run the visible cursor demo through its ending in the page overview. A single redesigned comparison page does not satisfy a request for this whole-deck experience.

**Contract-backed interactive companion** — “animated” alone keeps the classic quiet- reveal path above. An explicit request for an interactive/dynamic deck, 動く・ 動的スライド, clickable evidence, what-if recalculation, a slider, drill-down, or auto-demo builds the classic artifact first and then a companion from the same manifest:

python3 scripts/build_html_deck.py --manifest my-deck/deck.json -o my-deck/deck.html
python3 scripts/build_interactive_deck.py --manifest my-deck/deck.json -o my-deck/deck.interactive.html

Before adding a scene, use `references/interaction-selection.md`. Author the closed scene contract with `references/interactive-scene-schema.md`, review `references/interactive-accessibility.md`, and hand off with `references/presenter-operation.md`. Always report both paths. The interactive artifact never replaces the static/print baseline.

**Document** — write Markdown (with `spec:`/`svg:` exhibit references where a chart belongs) and build it straight to a browser-ready, print-to-A4 HTML report:

python3 scripts/build_html_report.py my-report.md -o my-report.html --lang en

`templates/reports/` has three starting points (board pre-read, one-pager, proposal memo).

**Speaker script** — the podium version of any deck: add a top-level `"notes"` field (a string, or a list of paragraph strings) to the slides that need narration, then build a print-first, one-slide-per-page HTML script with the narration set below each slide. The renderer ignores `notes` entirely, so adding it never changes the rendered slide, and a slide with no notes still gets its own page with a muted "no script" marker.

python3 scripts/build_speaker_script.py --manifest my-deck/deck.json -o my-deck/script.html --lang en

**Deck as an article** — the same deck read top-to-bottom on a single 680px reading column instead of click-through slides or a side-nav document: a paper-first hero (kicker/lead from the manifest's optional `series`/`lead` keys), then each slide's SVG followed by its `notes` as reading prose, with optional per-slide `label`/`refs` fields adding a section tag and a "Links" aside that rolls up into an end-of-article links section.

python3 scripts/build_html_article.py --manifest my-deck/deck.json -o my-deck/article.html --lang en

All classic fast paths and the optional interactive companion still obey the style system and quality rubric below — they only skip writing specs from a blank page. Fall back to the full workflow for anything the templates don't already cover.

Use When

• The user needs a board slide, executive memo visual, market map, competitor benchmark, investment view, performance bridge, or strategic timeline.
• The user needs visuals for any other document: internal reports, research summaries, sales proposals, project status updates, training or education materials, technical documentation, one-pagers, infographics, or study notes.
• The user has raw data, prose, notes, a process description, or a question and needs a visual direction — even if they only say "visualize this".
• The user asks for McKinsey-style, BCG-style, Bain-style, consulting-style, boardroom-ready, executive-ready, or strategy-deck visuals.
• The output should feel like a top-tier professional deliverable without implying affiliation with any consulting firm.

Do Not Use When

• The user wants dec