Workshops & classrooms: type must survive the back row and the 13-inch breakout laptop simultaneously
`workshop-visio-pptx` covers day-long labs, design sprints, and table exercises. Projectors are dimmer and lower-contrast than boardroom panels—hairlines and pale fills disappear. Attendees also reopen the same PPTX in small windows, so layouts drift. Maintain separate export profiles for “main screen” vs “printable breakout appendices” and laser-check arrow direction from mid-aisle, not only front-row feedback.
Workshop runbook: derive minimum type from room diagonal, export screen vs print variants, rehearse timers and breakout page turns
- Measure or photograph usable screen height, derive minimum title/body sizes, then return to .vsd to enlarge labels and reduce parallel connectors; for trace-and-copy exercises, boost stroke weight and contrast so learners can sketch what they saw.
- Validate both projector full-screen and a 13-inch window—watch for horizontal scroll or squashed art; if checklists sit in the footer band, print tests to ensure page numbers do not clip required steps.
- Give each table a consistently named kit and print the deck version plus hash on slide one; after breaks, announce new hashes if files swap so half the room is not on the morning USB copy.
VSD to PPTX (workshop) FAQ: classroom type, print appendices, kit versioning, break-time file swaps
Projector color skew makes green vs gray steps indistinguishable—recalibrate hardware or fix art?
Boost contrast and avoid adjacent pale-only distinctions; calibration is ideal but unreliable, so add numeric step labels or legend text that does not depend on hue alone—including for color-weak attendees.
Facilitators want whiteboard tweaks—can converted PPTX shapes be edited live?
Raster pages need overlays or return to .vsd; provide editable backup slides or PDF line art for markup instead of betting the whole improv on one export.
Fullscreen timers squeeze diagram safe zones—share the main master or use a dedicated timer layout?
Use an isolated timer master so content coordinates never shift; exiting countdown should jump back to the content master without the facilitator accidentally editing the main sequence.
Breakouts return with conclusions—embed editable tables or sticky photos?
Tables help post-event cleanup but need logins—structured slide headings plus numbered sticky photos indexed in notes often survive flaky Wi-Fi better than live co-editing.
After lunch, half the class claims missing pages—conversion bug or stale copies—how to prove in one minute?
Print total slide count and file hash on cover or properties; TAs compare manifests machine-by-machine—matching hashes with missing content usually means an old cached same-name file, not a silent drop.