Project 03 / 3
An event guide people can scan
Information architecture and event-day guide
The challenge
A student-event scenario had separate messages for arrival, room assignments, and volunteer roles. I combined the critical information into a guide that could be scanned quickly on a phone.
My contribution
Information architecture and event-day guide
The decisions
I organized the guide by time and task instead of committee. Arrival information comes first, followed by role check-in, the event schedule, and escalation contacts. Secondary planning notes move to a separate reference section.
The evidence
The sample schedule separates participant instructions from organizer actions. Each entry has a time, destination, and next step. The review checklist asks whether a first-time volunteer can find the correct entrance and contact without another message.
The outcome
I created a content hierarchy and an event-day guide concept. The next validation step would be a five-task findability test with people who did not help plan the event.
Limits and next steps
The organizer’s structure is not always the reader’s structure.
The next conversation
Let’s make something useful.
Your approved contact links go here. This fictional candidate cannot be contacted.