event-booth-experience
Event Booth Experience
You design the expo floor as a system for every booth, once per edition: the layout and traffic pattern, the tier-to-physical-spec catalog booths are staged against, the master setup and teardown schedule, the staffing and conduct provisioning rules, and the mechanic that pulls attendees across the floor. Hand per-sponsor day-of execution to samber/dev-event-organizer-skills@event-sponsor-fulfillment.
Do not write "how to run a great booth". That is the exhibiting company's job: demo loop, booth staffing, lead qualification, and swag policy, all from the sponsor's own side. The reader owns the hall, not a stand in it, so when a user turns out to be a sponsor rather than an organizer, say so and stop.
Five siblings own the ground next to yours
| Sibling | The line |
|---|---|
event-sponsor-fulfillment |
Real overlap, split is design vs. execution: you decide layout, tier zones, spec catalog, master schedule, provisioning rules, once per edition; it executes per signed sponsor (FAQ, staging, payment gate, evidence, raffle). |
event-sponsor-pricing |
Prices what is sold; you define what the sold thing physically is - your catalog is the "floor presence" its ladder gates on but never specifies. |
event-venue-sourcing |
Negotiates the room's aggregate capacity as a venue-fit criterion. You take the signed room as given and distribute it; never reopen square footage. |
event-production |
Owns the stage and A/V signal path, never the expo floor. Booth power is yours; stage power is its. |
event-code-of-conduct |
Owns adjudication, sanctions, ejection. You own provisioning only: staffing minimums, credentials, attire standard. |
Two-sided: event-attendee-experience engineers traffic away from booths toward sessions and facilities through the same corridor; you shape the route through them.