Factory Automation Executive Slide Architecture Matrix
Structure industrial automation slide decks into a high-impact narrative and visual layout matrix for C-suite decision-makers.
Use this template when planning an executive presentation for modernizing factory infrastructure or deploying robotics. It provides a structured slide-by-slide visual strategy matrix balancing technical metrics with executive storytelling.
Role: Principal Industrial Presentation Designer specializing in C-suite manufacturing proposals.
Context
- Manufacturing facility: {{plant_type}}
- Proposed technology: {{automation_solution}}
- Key decision-makers: {{target_executive_audience}}
- Core operational metric: {{primary_operational_kpi}}
- Presentation duration: {{presentation_time_limit}}
Task
Generate a comprehensive slide architecture matrix that defines the narrative flow, visual composition, and data visualization strategy for an executive presentation on industrial automation.
Method
- Analyze {{plant_type}} operational bottlenecks and translate them into a high-level executive problem statement.
- Map the strategic benefits of {{automation_solution}} across operational, financial, and safety pillars.
- Calibrate the density and pacing of the presentation to fit {{presentation_time_limit}} without losing technical rigor.
- Tailor data points specifically to resonate with {{target_executive_audience}}.
- Establish visual hierarchies that highlight gains in {{primary_operational_kpi}} on every analytical slide.
- Assign layout templates, graphic types (e.g., schematics, telemetry dashboards), and scannable visual anchors for each slide.
- Formulate transition logic between current manufacturing friction points and future automated state.
Constraints
- MUST output the core slide architecture as a structured markdown matrix.
- MUST NOT use generic clip art recommendations; specify technical visualization types (e.g., Sankey diagrams, isometric floor plans, Pareto charts).
- Narrative MUST prioritize ROI and operational continuity over low-level software specifications.
- Limit matrix to between 8 and 12 distinct slide blueprints.
Output format
1. Presentation Strategy Summary
Brief 3-sentence summary of the deck narrative arc.
2. Slide Architecture Matrix
A markdown table with columns: | Slide # | Slide Objective | Core Content & Narrative | Visual Layout & Chart Type | Highlighted Metric | Cognitive Focus for {{target_executive_audience}} |
3. Visual Standard Guidelines
A bulleted list defining color coding for uptime/downtime, typography hierarchy, and diagram styling rules.
Self-review
- Does every row in the matrix directly connect to {{automation_solution}} and {{plant_type}}?
- Are the slide allocations realistic for {{presentation_time_limit}}?
- Is {{primary_operational_kpi}} visually anchored in the layout specifications?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.