Hybrid Events are Not Two Tracks: Here’s Why
Last month, I was a facilitator for some breakout rooms at Hubb’s excellent virtual event, Untethered. In these 90 minute breakout sessions, participants were grouped…
Last month, I was a facilitator for some breakout rooms at Hubb’s excellent virtual event, Untethered. In these 90 minute breakout sessions, participants were grouped…
Last month, I was a facilitator for some breakout rooms at Hubb’s excellent virtual event, Untethered. In these 90 minute breakout sessions, participants were grouped together to discuss some of the bigger issues facing the industry; topics like attendee safety in the post Covid age, exhibitor ROI, and the promise and challenge of hybrid events.
We used Zoom breakout rooms + Mural to ideate with virtual sticky notes. It was cool. As it turns out, working on a problem together is actually a really good way to network!
In one of these breakout sessions, I got matched with some big brains - Sina Bünte from #eventprofsbreakshit, Taylor McLoughlin, co-founder and head of product at twine, and Jessica Bauer.
Together, we went deep on the looming hybrid event question. How are planners supposed to run two independent events, one for virtual participants, and one for in person? Do planners need to think about crossing the streams? (yes, sometimes). What is the tech going to look like to power these experiences? (still an open question). And in a world when almost everyone is vaccinated, what are attendees going to want to do - jump on a plane or tap on a link? (at this point, we don’t know).
My sense is that we stumbled upon a key insight, and I wanted to quickly share it. Here it is:
Conventional wisdom says that hybrid events are two tracks - an in person track, and a virtual track (with a possible third dynamic of finding ways to connect your in person and virtual attendees).
This is not quite right; here’s why. If you consider an event as three distinct phases - pre-event, during event, and post-event - the picture changes (for more on this topic see Points, Lines, and Circles: the Evolution of Events).
We are no longer talking about two parallel tracks. We are talking about ONE attendee journey that forks briefly for the day(s) of the in person experience, before converging again into a single stream / community.
Here’s a pic:
If you believe that both event owners and event technology companies have aspirations to deliver longer lasting experiences, and that attendees have been conditioned during the pandemic to engage with events that last weeks not days, it becomes clear that the virtual experience is the unifying track. (You could even argue that In Person attendees will dip in and out of the virtual track even while on site, via the mobile event app), making the case for a single journey even stronger.
So there you have it… this subtle point has changed the way we think about the attendee journey over here at twine.
Does it unlock any new thinking for you?
Cookie | Duration | Description |
---|---|---|
__stripe_mid | 1 year | Stripe sets this cookie cookie to process payments. |
__stripe_sid | 30 minutes | Stripe sets this cookie cookie to process payments. |
AWSELB | session | Associated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
AWSELBCORS | 5 minutes | This cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers. |
Cookie | Duration | Description |
---|---|---|
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_session_id | session | Cookie set by G2 to store the visitor’s navigation by recording the landing pages. This allows the website to present products and indicate the efficiency of the website. |
at-rand | never | AddThis sets this cookie to track page visits, sources of traffic and share counts. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
uvc | 1 year 1 month | Set by addthis.com to determine the usage of addthis.com service. |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
did | 1 year | Arbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
personalization_id | 2 years | Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
_project_x_session | session | No description |
AnalyticsSyncHistory | 1 month | No description |
CSRF-TOKEN | session | No description |
currentLanguage | 1 year | No description available. |
did_compat | 1 year | No description available. |
li_gc | 2 years | No description |
m | 2 years | No description available. |
muc_ads | 2 years | No description |
pixelcat_id | 1 year | No description |
There was a problem reporting this post.
Please confirm you want to block this member.
You will no longer be able to:
Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.