The transition back to Obsidian wasn’t just about returning to a familiar studio; it was about reclaiming the kind of creative friction that thrives only in person. Cain describes his current role as deeper than freelancing—less about fixed contracts, more about embedded collaboration. Instead of being a temporary resource for specific projects, he’s now a permanent fixture, able to engage with teams across disciplines without the constraints of remote communication.
Remote work, Cain argues, strips away the organic interactions that define game development. Over video calls, conversations often devolve into scheduled check-ins or task updates. In an office, however, ideas emerge unpredictably—between artists sketching concepts, designers debating mechanics, or writers refining dialogue. Cain cites recent exchanges with level designers, narrative architects, and even audio specialists as proof. These discussions, he insists, would never have surfaced over a screen. The hesitation to ask for help when working remotely, he explains, stems from an unspoken fear: Will this count against my billable hours? In an office, that barrier disappears. A quick Slack message or an impromptu visit to a colleague’s desk becomes effortless.
Even the mundane rituals of office life—like the studio’s weekly bagel run—serve as microcosms of collaboration. Cain, who jokes about his devotion to the ritual, frames it as more than just a snack break. It’s a chance to troubleshoot game problems alongside peers, to observe how others approach challenges, and to contribute without the formality of a meeting. For someone with his experience, these moments aren’t just productive; they’re revitalizing. The studio’s culture, he says, thrives on this kind of serendipitous exchange, and it’s something he couldn’t replicate as a contractor.
This isn’t to say Cain dismisses remote work entirely. The flexibility suited his semi-retirement, allowing him to contribute to multiple projects without geographic limitations. But the lack of structure—constantly chasing the next gig, the uncertainty of where his expertise would be needed next—eventually wore on him. Now, he’s in a role that feels sustainable. He’s not just a consultant; he’s part of the daily rhythm of creation. And for a man who helped define an industry, that matters more than any remote setup ever could.
The shift back to Obsidian also reflects a broader truth about game development: some work demands proximity. The best ideas, Cain suggests, are born from shared space, from the tension of differing perspectives, from the ability to iterate in real time. For him, that’s what ‘unretirement’ looks like—not just returning to work, but returning to the kind of collaboration that makes games extraordinary.
