Backup Demo Plan

When to Use This

Use the backup demo plan if:

• Cluster is not accessible
• UI is not loading
• Network issues prevent live demo
• Critical errors occur
• You need to demonstrate without infrastructure

Backup Demo Options

Option 1: Screenshots and Diagrams

Materials needed:

• Architecture diagrams
• UI screenshots
• Workflow execution screenshots
• Log outputs

Flow:

1. Present architecture diagram
2. Walk through screenshots
3. Explain what would happen live
4. Show workflow examples
5. Discuss deployment process

Advantages:

• No dependency on infrastructure
• Guaranteed to work
• Can be prepared in advance
• Professional presentation

Option 2: Pre-Recorded Video

Materials needed:

• Screen recording of demo
• Video editing (optional)
• Presentation software

Flow:

1. Introduce the video
2. Play recording
3. Pause for questions
4. Discuss key points
5. Q&A session

Advantages:

• Shows actual execution
• Can be paused/rewound
• Professional presentation
• Reusable for multiple audiences

Option 3: Architecture Discussion

Materials needed:

• Architecture diagrams
• Deployment documentation
• Technical specifications

Flow:

1. Present architecture
2. Discuss components
3. Explain deployment process
4. Show code examples
5. Discuss integration points

Advantages:

• Focuses on architecture
• No infrastructure needed
• Deep technical discussion
• Addresses design questions

Option 4: CLI Demonstration

Materials needed:

• Terminal access
• kubectl configured
• Workflow YAML files

Flow:

1. Show cluster status
2. Submit workflow via CLI
3. Show workflow status
4. Display logs
5. Explain what UI would show

Advantages:

• Shows technical depth
• Demonstrates automation
• No UI dependency
• Impresses technical audience

Preparation Checklist

Before the demo, prepare:

• [ ] Screenshots of all key workflows
• [ ] Architecture diagrams (high quality)
• [ ] Pre-recorded video (optional but recommended)
• [ ] CLI commands ready to run
• [ ] Documentation to share
• [ ] Backup presentation slides

Quick Reference: Key Screenshots

Must-Have Screenshots

1. Argo Workflows UI - Dashboard

   • Shows workflow list
   • Status indicators
   • Recent executions

2. Simple Workflow Execution

   • Workflow definition
   • Execution status
   • Output/logs

3. Multi-Step Workflow

   • Step-by-step view
   • Dependencies
   • Completion status

4. Parallel Workflow

   • Parallel execution view
   • Resource usage
   • Aggregation step

5. Architecture Diagram

   • Cluster overview
   • Component relationships
   • Network topology

Nice-to-Have Screenshots

• Error handling examples
• Scaling demonstrations
• Integration points
• Monitoring dashboards

Talking Points for Backup Demo

If Using Screenshots

Opening: "I've prepared some screenshots to show you how this works. In a live environment, you'd see this in real-time, but this gives you a good sense of the capabilities."

During:

• Explain what they're seeing
• Point out key features
• Compare to alternatives
• Address questions

Closing: "Would you like to schedule a live demo once we have the infrastructure ready?"

If Using Video

Opening: "I've recorded a demonstration of the system in action. Let me walk you through it..."

During:

• Pause for questions
• Explain what's happening
• Highlight key moments
• Replay if needed

Closing: "Any questions about what you saw? We can also do a live demo if you'd prefer."

If Using Architecture Discussion

Opening: "Let me walk you through the architecture and how this would work in your environment..."

During:

• Explain each component
• Discuss design decisions
• Address technical questions
• Show code/configurations

Closing: "Does this architecture align with your requirements? We can discuss deployment next steps."

Common Questions During Backup Demo

"Can we see it live?"

Response: "Absolutely. We can schedule a live demo. For now, let me show you [screenshots/video/architecture] to give you a sense of how it works."

"How long does deployment take?"

Response: "Deployment typically takes [X] minutes. The infrastructure is automated, so it's repeatable and reliable."

"What if something goes wrong?"

Response: "Great question. Let me show you the error handling and troubleshooting capabilities..."

"How does this compare to [alternative]?"

Response: "Here are the key differences... [explain based on your knowledge]"

Post-Backup Demo Follow-up

1. Schedule live demo (if requested)
2. Share materials (screenshots, diagrams, docs)
3. Answer questions (via email or call)
4. Provide access (if appropriate)
5. Next steps (based on their interest)

Notes

Use this space to note what worked, what didn't, and improvements for next time: