unDavos Playbook

Explore

unDavos 2024 Summit Co-Creation and Volunteering

Volunteer Roles & responsibilities

unDavos Venue Host

unDavos Conference Owner

unDavos Core Team

Event and ticketing system: Luma

Welcome to the unDavos Summit: A Community-Driven Experience

Welcome to the unDavos Summit, where our collective expertise and collaboration shape an engaging and impactful event. This summit thrives on a self-organized, community-driven approach, making every role crucial in bringing our shared vision to life. Click the roles to read more about them.

Want to co-create?

Join the

unDavos Summit 24 - group for volunteers, people interested in working on formats⁠

Telegram group (not speakers though - different space for them!) and intro yourself when you join (i.e. Linkedin URL... and how you could help)

Key Roles and communication structure:

For ease of self organisation and communication we propose this organising structure:

⁠

Conference Owner⁠

: Oversees the overall coordination of the summit, ensuring seamless integration of all sessions and activities, and serving as the central point of contact for session organizers and key stakeholders.

⁠

Session Owners⁠

: Curate and manage individual sessions, including speaker coordination and content planning.

⁠

Speakers⁠

: Share insights and knowledge, contributing to the rich tapestry of discussions.

⁠

Moderators⁠

: Drive panel discussions, engage audiences, and keep conversations focused and dynamic.

⁠

Facilitators⁠

: Lead interactive sessions, encouraging active participation and engagement.

⁠

Venue Hosts⁠

: Ensure smooth transitions between sessions, maintaining the schedule, and fostering a welcoming environment.

⁠

Greeters and Registration⁠

: Welcome attendees and assist with check-ins and information dissemination. Maintain the orderliness and cleanliness of the event spaces.

⁠

Security and People Management⁠

: Oversee attendee safety and manage crowd control during peak times(Only at night if needed).

Collaborative Spirit:

Cooperative Effort: Roles may be filled by one or multiple individuals, with opportunities for co-working to manage responsibilities.

Expected Effort: Time commitments are estimated based on tasks and the efficiency of communication and alignment within the team.

Dedicated Communication Channels: Each slot/panel will have its own Telegram group for streamlined communication among the slot owner, panelists, moderator, content team, speaker wrangler, and Mark.

Venue Management: With three rooms in MP adjacent to each other, coordination can be efficiently managed with shared hosts and a central registration point.

Task Allocation:

Based on Venue and Time Slots: Tasks are organized according to specific rooms or venues and are divided by different time slots to ensure comprehensive coverage and support for each session.

Each slot at the summit is an orchestrated effort involving various roles, ensuring a rich and seamless experience for all attendees. From session planning to audience engagement and operational management, every role is integral to the success of the unDavos Summit.

⁠

⁠

👄 unDavos Lingo

As with every unique gathering, there are some expressions and abbreviations that might be confusing at first, so here's a short explanation of the most common ones:

unDavos Summit: The collective name for a set of events taking place during WEF week in Jan 2024

Venue: A physical place where we hold the events - As of 10 Dec we have:.Mountain Plaza Hotel & Sonas bar

Room: The specific room where we hold an event in a venue. As of 10 Dec we have: Sertig 1, Sertif 2, Fuela, and Sonas

Slot: A slot is a block of time, typically 1.5 hours but it may be longer.

BYOC. Bring your own cup, so people can share delicious drinks with you!

Workshops. All the workshops, sessions, and activities that make the magic of Togather.

⁠

Welcome to the unDavos Summit: A Community-Driven Experience

Key Roles and communication structure:

Collaborative Spirit:

Task Allocation:

👄 unDavos Lingo

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.