Establish monthly workshop cadence and process

[blink-so]

Objective

Establish a monthly workshop cadence to continuously stress test the platform with real user load, surface optimization opportunities, and validate architectural changes.

Context

The Sept 30 workshop revealed issues that weren't caught during internal testing. Regular workshops with both internal and external users will help catch problems early and drive continuous improvement.

Requirements

Workshop Planning

• Define target audience mix (internal vs external users)
• Determine optimal concurrent user count for meaningful stress testing
• Create workshop scheduling process (recurring calendar invite, registration, etc.)
• Develop workshop content/agenda that exercises platform capabilities
• Define success metrics to track month-over-month improvements

Infrastructure Preparation

• Complete pre-workshop validation checklist before each event (Create pre-workshop validation checklist and runbook #4)
• Document capacity planning process based on expected attendance
• Create post-workshop feedback collection mechanism
• Establish process for tracking and prioritizing issues discovered during workshops

Documentation

• Workshop facilitation guide
• Participant onboarding documentation
• Post-workshop retrospective template
• Metrics dashboard for tracking platform stability across workshops

Success Criteria

• Monthly workshop scheduled and executed consistently
• Each workshop has 10+ concurrent users
• Issues discovered during workshops are tracked and addressed before next workshop
• Month-over-month improvement in stability metrics
• Zero critical incidents (data loss, prolonged downtime) during workshops

Related

Sept 30 Workshop Postmortem