Play in Utah
D&D for Corporate Team Building (Yes, Really)
A D&D team-building event is a facilitated group problem-solving exercise wearing a dragon costume: a professional Game Master runs your team through a custom two-to-three hour adventure where the puzzles require collaboration, the quiet analyst gets a spotlight, and the org chart stops mattering by the second encounter. It runs in-person or fully remote, needs zero experience from anyone, and it beats trust falls by every metric including "employees actually want to come."
Why it works better than the usual offsite
Team-building exercises fail two ways: they're transparent (everyone knows the ropes course is a metaphor) or they're competitive (the sales team wins again). A tabletop one-shot dodges both. The collaboration is real, not simulated; the party genuinely cannot beat the scenario without pooling information, dividing roles, and listening to the person who noticed the thing. And there's no winner, just a shared story.
What managers actually report afterward: the meeting-silent people talk. Roleplay grants cover ("that was my character being bold"), pregens hand introverts a script to start from, and a good GM reads the room and passes the spotlight like it's their job, because it is. Six sessions of standups won't show you what one goblin ambush does.
What a corporate session looks like
The GM arrives (or opens the video call) with everything: a custom one-shot tuned to your group, pregens with team-friendly roles, dice, and the thirty-second tone-and-boundaries setup that keeps a workplace event workplace-appropriate. Nobody prepares anything. Two to three hours later there's been a heist or a rescue or a diplomatic incident, everyone has a new shared vocabulary ("this is a locked-door problem, someone get Kevin"), and the event photographs shockingly well.
Formats that work: single tables up to eight; multiple parallel tables with linked adventures for bigger groups (the finales collide, which teams love); recurring monthly "campaign" formats for teams that want an ongoing ritual; and fully remote sessions for distributed teams, which consistently outperform the standard virtual happy hour.
Venues, remote, and the Utah advantage
Remote works anywhere. In person, you can host at your office (GMs travel) or come to a venue built for it: our Provo medieval tavern or Sandy sci-fi outpost turn the event into an obvious calendar highlight, and the theming does half the icebreaking before dice touch the table. Utah teams get the venues; everyone else gets the screen, and the session travels fine.
Pricing runs as flat event rates by headcount and length, in normal corporate-activity territory (think catered-lunch-and-facilitator money, not consultant money). Inquire with the date and headcount; custom scenarios, branded in-jokes, and recurring series are all standard requests.
Frequently asked questions
Does D&D team building work for employees who've never played?
It's designed for them: pre-made characters, a GM who teaches by doing, and a scenario where the game mechanics stay shallow while the collaboration runs deep. Mixed groups of veterans and total newcomers are the normal case, not a complication.
How long does a corporate D&D event take?
Two to three hours is the standard block, fitting an afternoon offsite with room for food. Half-day versions with two linked sessions exist for teams that want the full arc; shorter than ninety minutes isn't worth the setup.
Can it run remotely for a distributed team?
Yes, fully: video call plus a shared virtual table, with the GM handling every technical piece. Remote sessions are among the best-reviewed formats because they give distributed teams an actual shared experience instead of another webinar.
Is D&D appropriate for a workplace event?
With a professional facilitator, entirely: content is tuned workplace-safe upfront, boundary tools run by default, and the tone lands closer to an escape room than to anything edgy. HR tends to relax within the first ten minutes.
How many people can participate at once?
Up to eight per table for a good experience; beyond that, parallel tables with linked scenarios scale to a whole department, and the cross-table finale becomes the event's signature moment. Headcount just changes the table math, not the feasibility.