Stacks / 8 workflow stages · v3.1.0 · reviewed 2026-09-05
Build an Executive Decision Deck
Move from evidence to a clear narrative, defensible charts, diagrams, and polished executive communication.
Best for
Operators turning research, analysis, strategy, or diligence into a presentation that has to support a decision.
Outcome
A concise executive narrative with source-backed analysis, appropriate visuals, and a consistent presentation system.
Not for
A highly cinematic brand campaign where persuasion depends more on creative production than analytical clarity.
Operator guidance
Best whenDecision-makers need a concise recommendation supported by auditable evidence and clear tradeoffs.
Avoid whenThe work is still exploratory and has no defined decision or audience.
CompatibilityLock source facts and chart data before visual assembly; keep links and notes attached through export.
Use this as a decision framework, not a mandatory shopping list. Swap or skip layers based on your existing stack, constraints, and risk profile.
1. Ground the story
Find supporting evidence and external context before designing slides around an unsupported narrative.
- Perplexity
Recommendation details
Why: Consider Perplexity as an alternative for 1. Ground the story; compare its documented capabilities and operating constraints with the primary recommendation.
Best when: Useful complementary answer/search engine.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Perplexity official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
Recommendation details
Best when: Search and retrieval API useful for Claude agents.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Exa official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
2. Choose the right chart
Match the analytical question to an appropriate chart type before styling it.
- The Data Visualisation Catalogue
Recommendation details
Why: Consider The Data Visualisation Catalogue as an alternative for 2. Choose the right chart; compare its documented capabilities and operating constraints with the primary recommendation.
Best when: Fast taxonomy of chart types, purposes and usage guidance.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: The Data Visualisation Catalogue official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
Recommendation details
Best when: Decision tree for choosing the right visualization based on the shape of the data.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Data to Viz official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
3. Build clear charts
Create clean, publication-quality charts without turning every visualization into a custom engineering task.
- Flourish
Recommendation details
Why: Consider Flourish as an alternative for 3. Build clear charts; compare its documented capabilities and operating constraints with the primary recommendation.
Best when: Interactive visual storytelling.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Flourish official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
- Observable Plot
Recommendation details
Why: Consider Observable Plot as an alternative for 3. Build clear charts; compare its documented capabilities and operating constraints with the primary recommendation.
Best when: Concise JavaScript visualization grammar.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Observable Plot official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
Recommendation details
Best when: Fast, publication-quality charts and maps.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Datawrapper official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
4. Explain systems visually
Turn processes, architectures, and relationships into structured diagrams that can be iterated quickly.
- Whimsical AI
Recommendation details
Why: Consider Whimsical AI as an alternative for 4. Explain systems visually; compare its documented capabilities and operating constraints with the primary recommendation.
Best when: AI-assisted diagrams and boards.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Whimsical AI official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
- Excalidraw
Recommendation details
Why: Consider Excalidraw as an alternative for 4. Explain systems visually; compare its documented capabilities and operating constraints with the primary recommendation.
Best when: Fast sketch-style diagrams.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Excalidraw official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
Recommendation details
Best when: Text-to-diagram syntax Claude can generate directly.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Mermaid official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
5. Create fast visual explanations
Generate simple explanatory visuals when a concept needs more than text but not a bespoke illustration.
- tldraw
Recommendation details
Why: Consider tldraw as an alternative for 5. Create fast visual explanations; compare its documented capabilities and operating constraints with the primary recommendation.
Best when: Programmable infinite canvas.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: tldraw official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
Recommendation details
Best when: Turn text into business visuals.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Napkin AI official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
6. Improve typography
Use stronger typography references so the deck feels intentional rather than template-driven.
- Fonts In Use
Recommendation details
Why: Consider Fonts In Use as an alternative for 6. Improve typography; compare its documented capabilities and operating constraints with the primary recommendation.
Best when: Real-world typography references.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Fonts In Use official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
Recommendation details
Best when: Typography inspiration and pairing references.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Typewolf official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
7. Standardize icons
Use a coherent icon family instead of mixing inconsistent symbols across slides.
Recommendation details
Best when: Flexible multi-weight icon family.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Phosphor Icons official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
8. Assemble and refine
Use a presentation-oriented workspace when speed of assembly matters, while keeping the underlying argument and evidence primary.
Recommendation details
Best when: Fast AI-assisted presentation creation.
Avoid when: Avoid when the current official source does not support your required deployment, data-handling, or integration constraints.
Compatibility: Validate interfaces, data formats, and operational handoffs with the adjacent stack stages.
Prerequisites:
- Review the current official source and implementation requirements.
Evidence: Gamma official source (2026-09-05)
Verified 2026-09-05 · Medium confidence
Need this workflow built and running, not just linked? EE Solutions implements agentic stacks like this one. EE Solutions is a senior technology team for private capital firms and their portfolio companies.
Talk to EE Solutions ↗