The Conference That Almost Didn't Happen
In 2019, Spotify’s engineering team began planning its second internal engineering conference, slated for April 2020. The plan was ambitious: roughly 1,500 attendees from a dozen cities, seven parallel tracks, three days of talks and social events. Sixteen engineers from across Spotify organized it, with support from partners and day-of volunteers.
Then the conference was canceled.
Days before the announcement, the organizers had finalized an agenda featuring over 140 hours of talks from colleagues. Rather than let that work go to waste, a few members of the team started asking an obvious question: what if we held the conference anyway? The follow-up questions — would anyone want to speak, would anyone tune in — were quickly answered with a yes.
What they didn’t anticipate was how much work it would take to pivot from a large in-person event to a series of virtual talks.
Building a Virtual Stage
The organizers leaned on existing infrastructure. Keith McNeill, a backend engineer and member of Spotify’s Techbytes committee, loaned the team their playbook and event platform. Mike Lewis, a web engineer, agreed to co-host talks in the Central European Time zone. Edmond Chow helped brainstorm a name, and the team settled on Tiny Desk Conference, a nod to NPR’s Tiny Desk Concert series popular among U.S.-based employees.
They reached out to the original conference speakers and got an enthusiastic response. By mid-August, they had completed two seasons of internal and external talks featuring 32 speakers from four time zones and six offices, with nearly a dozen more planned. The talks spanned all seven R&D disciplines: web, backend, data, machine learning and tech research, mobile, quality, and leadership/Agile. Live viewership came in higher than expected, and recorded videos drew comparable numbers afterward.
A Speaker Needs an Audience
Presenting to a screen is not the same as presenting to a room. Without the energy of a live audience, speakers can feel like they’re speaking into a void — a particular challenge for those who rely on real-time feedback, even if it’s a relief for those prone to stage fright.
The team is exploring ways to close that gap: side-channel discussions, instant polls for engagement and feedback, pre-recorded talks with live chat interaction during the stream, and optional breakout sessions before and after talks to encourage organic conversation.
Over-Communication Works
Early on, the organizers sent a single calendar invite and a Slack reminder the day before, thinking that repeated invites for talks happening several times a week would clutter calendars. They were wrong. Attendance improved significantly once they shifted to a policy of relentless reminders: calendar invites with email notifications, promotion in broad internal channels, and posts both prior to and on the day of each talk.
High-Touch Outreach Beats Mass Emails
Initial speaker recruitment relied on personalized emails to each individual, and response rates were high. When the team tried a mass email to recruit backend engineering speakers, the response rate dropped considerably. They reverted to the time-intensive, individualized approach. The lesson: the energy put into outreach reflects the energy get back.
Virtual Is Not Lighter Lifting
A virtual talk requires more effort than an in-person one. AV checks are more extensive — a failed livestream can’t be fixed by raising your voice. The event production team, Amplifier, supported every talk. And because the conference was no longer a three-day sprint but a months-long series of events held several times a week, the promotion, coordination, speaker prep, emceeing, and asset generation all repeated on a continuous cycle, adding significant overhead.
Shorter Talks, Consistent Attendance
For attendees, the format had a clear upside: no need to commit three full days. Talks ran 20 to 45 minutes, and attendees could pick topics that genuinely interested them. Traditional conferences see attendance drop off by the final day; over four months, Tiny Desk Conference’s numbers stayed relatively stable.
What Comes Next
Tiny Desk Conference’s second season wrapped on September 9th. The organizers and leadership are now debating its future — whether it will remain a standalone series or be folded into Spotify’s internal conference week. What’s clear is that the experiment worked, thanks to the willingness of colleagues across R&D to try something new and share what they’ve learned in the process.
