Skip to content
iSu Technologies iSu Technologies Documentation

🚨 Demo Backup Plan - Failure Recovery Guide

🚨 Demo Backup Plan - Failure Recovery Guide

Section titled “🚨 Demo Backup Plan - Failure Recovery Guide”

Quick Reference Card

Section titled “Quick Reference Card”

Print this and keep it visible during demo

⚡ Emergency Contacts

Section titled “⚡ Emergency Contacts”

🔥 Common Failures & Instant Fixes

Section titled “🔥 Common Failures & Instant Fixes”

1. Frontend Won’t Load (localhost:3000)

Section titled “1. Frontend Won’t Load (localhost:3000)”

Symptoms: White screen, connection refused, or infinite loading

Immediate Fix:

Terminal window
# Option A: Restart frontend
cd frontend && npm run dev


# Option B: Use Railway deployment
# Open browser: https://frontend-production-55e3.up.railway.app

Talking Point: “Let me show you our cloud deployment on Railway instead - same platform, production environment”

2. Backend API Not Responding (localhost:8000)

Section titled “2. Backend API Not Responding (localhost:8000)”

Symptoms: 500 errors, “Failed to fetch” messages

Immediate Fix:

Terminal window
# Option A: Restart backend
cd backend && uvicorn app.main:app --reload --host 0.0.0.0 --port 8000


# Option B: Show API docs offline
# Navigate to: /Users/nhla/Desktop/PROJECTS/2025/mathew-goniwe/docs/

Talking Point: “The backend is running robustly in production - let me show you the API documentation and architecture instead”

3. Login Failed / Auth Issues

Section titled “3. Login Failed / Auth Issues”

Symptoms: “Invalid password” or stuck at login screen

Immediate Fixes:

  1. Clear browser cache: Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows)
  2. Try password again: mgslg2025
  3. Use incognito window: Cmd+Shift+N

Last Resort:

Talking Point: “Authentication is working - let me refresh the session”

4. PDF Download Fails

Section titled “4. PDF Download Fails”

Symptoms: Error message, no download, or corrupted file

Immediate Fix:

  • Open pre-saved PDF from: /Users/nhla/Desktop/PROJECTS/2025/mathew-goniwe/DEMO_ASSETS/sample_executive_summary.pdf

Talking Point: “Here’s a sample report I generated earlier today with the same data”

Preventive:

  • Generate and save PDF before demo
  • Test download button 30 minutes before

5. Database Connection Issues

Section titled “5. Database Connection Issues”

Symptoms: Empty dashboards, “0 participants”, query errors

Immediate Check:

Terminal window
# Verify database
cd backend
python3 -c "from app.core.database import engine; print('DB OK')"

Immediate Fix:

8000/api/dashboard-mock/kpis
# Worst case: Use mock data endpoints

Talking Point: “Our fallback systems ensure continuous operation - let me show you the mock data mode”

6. Charts Not Rendering

Section titled “6. Charts Not Rendering”

Symptoms: Broken charts, empty visualizations

Immediate Fix:

  1. Refresh page: F5 or Cmd+R
  2. Check console: F12 → Console tab (look for errors)
  3. Use screenshots: /DEMO_ASSETS/screenshots/

Talking Point: “Let me show you these visualizations I prepared earlier”

7. Slow Network / Timeout

Section titled “7. Slow Network / Timeout”

Symptoms: Long loading times, timeout errors

Immediate Fix:

  1. Switch to localhost: If using Railway, switch to local
  2. Use screenshots: Navigate to backup folder
  3. Show architecture: Discuss technical design while waiting

Talking Point: “While this loads, let me walk you through the technical architecture that ensures sub-200ms response times in production”

8. Geographic Filtering Not Working

Section titled “8. Geographic Filtering Not Working”

Symptoms: Dropdown doesn’t filter, data doesn’t update

Immediate Fix:

  1. Refresh page: Clear filters and try again
  2. Show different demo section: Skip to ML analytics

Talking Point: “Let me show you the predictive analytics instead - equally impressive”

📂 Backup Materials Location

Section titled “📂 Backup Materials Location”

Create this folder structure before demo:

/Users/nhla/Desktop/DEMO_ASSETS/
├── screenshots/
│   ├── 01_login.png
│   ├── 02_main_dashboard.png
│   ├── 03_interactive_analytics.png
│   ├── 04_ml_predictions.png
│   ├── 05_geographic_filtering.png
│   └── 06_api_docs.png
├── videos/
│   └── full_demo_walkthrough.mp4 (optional)
├── reports/
│   └── sample_executive_summary.pdf
└── presentation/
    └── backup_slides.pptx

🎯 Graceful Degradation Strategy

Section titled “🎯 Graceful Degradation Strategy”

Priority 1: Core Demo Flow

Section titled “Priority 1: Core Demo Flow”
  • Login → Main Dashboard → Download PDF → Interactive Analytics

Priority 2: Advanced Features

Section titled “Priority 2: Advanced Features”
  • ML Predictions → District Filtering → API Docs

Priority 3: Technical Deep-Dive

Section titled “Priority 3: Technical Deep-Dive”
  • Database Architecture → Performance Metrics → Scalability

If Priority 1 fails, pivot to Priority 2. If that fails, pivot to Priority 3.

🗣️ Failure Response Templates

Section titled “🗣️ Failure Response Templates”

Template 1: Technical Glitch

Section titled “Template 1: Technical Glitch”

“Looks like we’re experiencing a momentary network issue - let me show you [backup]. This actually demonstrates why we build redundancy into production systems.”

Template 2: Own The Issue

Section titled “Template 2: Own The Issue”

“I apologize for this technical hiccup. The good news is, this gives me a chance to show you our backup systems and talk through the architecture.”

Template 3: Pivot To Strength

Section titled “Template 3: Pivot To Strength”

“While this loads, let me share something even more impressive - [show alternative feature]“

Template 4: Confidence Builder

Section titled “Template 4: Confidence Builder”

“In production, we have automatic failover and retry logic. Let me demonstrate our monitoring dashboard instead.”

⏱️ Time Management During Failures

Section titled “⏱️ Time Management During Failures”
  • Don’t panic: You have 10-12 minutes planned
  • Quick recovery: Spend max 30 seconds troubleshooting
  • Pivot fast: If 30 seconds doesn’t fix it, move to backup
  • Stay confident: Technical glitches happen; recovery shows professionalism

📞 During-Demo Checklist

Section titled “📞 During-Demo Checklist”

Every 2 Minutes, Verify:

Section titled “Every 2 Minutes, Verify:”
  • Stakeholders still engaged (eye contact, nodding)
  • Demo pace appropriate (not too fast/slow)
  • Technical features working
  • Time remaining

If Losing Engagement:

Section titled “If Losing Engagement:”
  1. Ask a question: “What’s most important for your workflow?”
  2. Show something interactive: “Try filtering by your region”
  3. Relate to their pain: “I know manual reporting takes hours - watch this”

🎬 Pre-Demo Final Check (30 min before)

Section titled “🎬 Pre-Demo Final Check (30 min before)”

Test Sequence:

Section titled “Test Sequence:”
  1. Open frontend: http://localhost:3000
  2. Login with: mgslg2025
  3. Verify dashboard loads (4 KPIs visible)
  4. Download PDF successfully
  5. Navigate to /dashboard
  6. Filter by Gauteng → verify 679 participants
  7. Select district → verify filtering works
  8. Navigate to /ml-analytics
  9. Verify predictions load
  10. Open API docs: http://localhost:8000/docs
  11. Make test API call

If ANY step fails, investigate and fix BEFORE demo starts

💾 Emergency Backup Commands

Section titled “💾 Emergency Backup Commands”

Save These In Notes App:

Section titled “Save These In Notes App:”
Terminal window
# Restart everything
cd /Users/nhla/Desktop/PROJECTS/2025/mathew-goniwe
cd backend && uvicorn app.main:app --reload --host 0.0.0.0 --port 8000 &
cd frontend && npm run dev &


# Check backend health
curl http://localhost:8000/api/health


# Check frontend
open http://localhost:3000


# Emergency database check
cd backend && python3 -m app.core.database


# Kill all processes if needed
killall node python3 uvicorn

🧘 Mental Preparation

Section titled “🧘 Mental Preparation”

Remember:

Section titled “Remember:”
  1. You built working software - that’s 90% of the battle
  2. Failures are opportunities to show problem-solving
  3. Stakeholders are human - they understand glitches
  4. You have backups - you’re prepared
  5. Confidence is key - you know this system inside out

If Demo Goes Perfect:

Section titled “If Demo Goes Perfect:”

Great! You prepared well.

If Demo Has Issues:

Section titled “If Demo Has Issues:”

Even better! You handled pressure gracefully and demonstrated recovery.

📊 Post-Demo Recovery

Section titled “📊 Post-Demo Recovery”

If demo had significant failures:

Email Follow-Up (send within 2 hours):

Section titled “Email Follow-Up (send within 2 hours):”
Subject: MGSLG Analytics Demo - Follow-Up


Dear [Stakeholder],


Thank you for your time today. I apologize for the [specific issue] during the demonstration. I've identified the cause (network latency) and wanted to share:


1. Video recording of full demo working perfectly: [link]
2. Sample executive summary PDF: [attached]
3. Access to staging environment for your team to explore: [link]


The platform you saw represents 60% of development work already complete. I'm confident in our ability to deliver a production-ready system in 8 weeks.


Available for any questions or a follow-up demo.


Best regards,
[Your Name]

✅ Success Metrics

Section titled “✅ Success Metrics”

Demo = Success If:

Section titled “Demo = Success If:”
  • Stakeholders saw working software (even partially)
  • You maintained composure during issues
  • You demonstrated technical competence
  • You differentiated from competitors
  • You secured next steps (meeting, proposal request)

A perfect demo is impressive. A flawed demo recovered gracefully is memorable.

Printed on: [Demo Date] Keep this visible during entire presentation

🚀 You’ve got this. Failures are expected. Recovery is what matters.