Expo Dress Rehearsal & Showcase Evidence
本页目录· 7 条
Rehearsal objective
The dress rehearsal should reveal problems in the complete experience before Expo: setup, story, hand-offs, demo reliability, audience interaction and recovery.
Before the rehearsal
- Expo logistics and session details are confirmed.
- Stable build/version is frozen and linked.
- Device, network, accounts, permissions, cables/power and display are checked.
- Offline/backup demo path is available.
- Demo data is realistic, ethical and resettable.
- Team roles and hand-offs are timed.
- Product Video plays from the final PGP/ePortfolio link.
- Product / Support / Maintenance evidence is accessible to mentors.
- Known limitations and safety/privacy boundaries can be stated honestly.
Showcase flow
- Opening: audience-relevant problem and why it matters.
- Evidence: user/community insight and design decision.
- Live outcome: demonstrate the critical journey.
- Value: show benefit and evidence, not only features.
- Trust: mention quality, security, accessibility and limitations.
- Future: what sponsorship/continuation would enable.
- Conversation: invite questions and record feedback.
Role plan
- Opener / pitch:
- Demo operator:
- Evidence and technical questions:
- User/impact questions:
- Timekeeper:
- Observer / feedback capture:
- Backup operator:
Failure drills
- Network unavailable:
- Login/credential failure:
- External API unavailable:
- Data not reset:
- Video/audio failure:
- Display incompatible:
- Question exceeds current evidence:
A professional recovery is calm: name the issue, switch to the prepared evidence path and do not invent a result.
Evidence after rehearsal
- Timing and audience comprehension.
- Integrity/acceptance defects.
- Mentor requests vs observations vs constraints.
- Accepted/deferred/rejected actions with rationale.
- Final Expo run sheet and setup checklist.
- Updated handover/known-limitations links.