The Squad That Almost Never Launched: Why Remote Teamwork Is Your Secret Superpower

The Discord ping hit Lila’s phone at 3:17PM on a drizzly October Tuesday in New York, the exact moment she’d closed her AP Biology exam tab and opened the climate action forum she’d been scrolling for three weeks straight. The message was from a user named Rafa@Rio, a username she’d seen posting photos of bleached coral reefs off the coast of Brazil for months, and it read: *Anyone want to build an indie game about ocean conservation? I know basic Python, but I’m useless at art and story. Looking for teammates who actually care about this, not just people who want to pad their college apps.*

Lila’s finger hovered over the reply button for 12 whole seconds. She’d spent the last two years posting climate strike flyers around her high school, begging her parents to stop buying single-use plastic, and begging her teachers to let her do a climate project instead of the assigned essay on *The Great Gatsby*. She’d never made a game before. She’d never even coded anything more complicated than a basic HTML website for her middle school tech class. But she’d spent 300 hours playing indie platformers the year before, and she kept thinking: why isn’t there a game about saving coral reefs that doesn’t feel like a boring school assignment?

She typed back: *I can do sound design and keep us on track. I’m in New York, 16, never made a game before but I’m fast at learning tools.*

Rafa replied in 30 seconds: *Hell yes. I’m 16, in Rio. I’ve been messing with Godot for a year, made a few tiny platformers no one played. Let’s find more people.*

They spent the next two hours scrolling the forum, pinging users who’d posted ocean art or climate stories in the past week. They found Mia, a 15-year-old from Shenzhen who posted watercolor paintings of sea turtles in her signature, and Kael, a 17-year-old from London who’d written a 20,000-word fantasy novel about a kid who could talk to fish that he’d posted snippets of in the forum’s writing channel. By 5PM New York time, the Oasis Squad was born: four teens, four time zones (UTC-5 New York, UTC-0 London, UTC+8 Shenzhen, UTC-3 Rio), zero game development experience, and a shared rage about how fast the world’s coral reefs were dying.

Their first meeting was scheduled for 8PM New York time that same day. No one thought to check the time difference. For Kael in London, that was 1AM the next morning. For Mia in Shenzhen, that was 11AM the next day, right in the middle of her morning art class. For Rafa in Rio,

The first meeting dissolved into chaos 12 minutes in. Kael joined the Google Meet 10 minutes late, headphones askew, eyes half-clamped shut, and mumbled a “sorry” before slumping back in his chair so far his chin nearly touched his chest. “My mom thought I was sleep-talking to a ghost when she heard me muttering about coral reefs at 1AM,” he admitted when Lila asked if he was okay. He’d fallen asleep mid-sentence three times already, and his camera kept cutting out because he’d propped his laptop on a pile of textbooks on his bed, and every time he nodded off, it tipped forward.

Mia never turned her camera on at all. A quick typed note in the chat explained her art teacher was prowling the Shenzhen classroom, collecting sketchbooks, and if she was caught on a video call, she’d lose her phone for a month. Her messages popped up in the chat every 30 seconds, though—*“I think a platformer is better! We can make the coral levels super pretty!”* *“Wait, should the turtle be a boy or a girl?”* *“Rafa, did you see the tutorial I linked for 8-bit water effects?”*—but half the time, the rest of the team was talking over each other so fast no one read them.

Rafa’s internet cut out twice, each time mid-rant about why Python was better than C# for a first-time indie project. The first time, he reconnected 3 minutes later yelling “MY FAMILY IS WATCHING THE FLAMENGO MATCH CUT THEM SOME SLACK.” The second time, he came back apologizing, but 2 minutes later his audio glitched so bad all they could hear was the roar of a soccer crowd for 45 seconds. Lila, who’d been bouncing in her chair so fast her cat kept jumping off her lap, finally paused 45 minutes in. “Wait,” she said, “we haven’t even decided what our roles are. Or what the first deadline is. Or how we’re going to talk to each other when we’re not in this call.”

No one had an answer.

They spent the next 20 minutes arguing about genre, settling on a 2D platformer with visual novel elements at Rafa’s insistence (“platformers are easier to code for first timers, trust me”), and then spent 10 more minutes arguing about the turtle’s color scheme. Mia wanted a bright pink shell to match the coral reefs she’d painted in her art class; Rafa said pink would clash with the blue 8-bit water he’d already started coding. They compromised on teal, but no one wrote the decision down. When Lila tried to assign tasks—Rafa coding, Mia art, Kael story, her doing sound and “keeping us on track”—no one pushed back, but no one asked what “on track” meant, or what the first milestone was, or when they wanted the first demo done. Rafa said “a few weeks?” and everyone nodded like that was a concrete plan. The call ended 90 minutes after it started, and 17 unread messages popped up in the new group chat before Lila could even close the tab: 7 memes about sea turtles, 4 links to random Godot tutorials, 3 arguments about whether the turtle should have a superhero cape, and 3 messages from Kael saying he’d fallen asleep 10 minutes before the call ended and had no idea what they’d decided.

The next two weeks were a masterclass in unplanned remote dysfunction. They stuck to the “Sunday 8PM ET meeting” schedule they’d agreed to, even though no one had bothered to convert the time for everyone else. Kael stayed up until 1AM every Sunday, his mom knocking on his door every 20 minutes to ask if he was “doing drugs or having a crisis” because he was still awake at 1AM on a school night. He started missing meetings after two weeks, when his Sunday football practice ran late and he was too exhausted to stay awake. The rest of the team left 12 angry messages in the group chat calling him flaky, until he snapped back that he was writing 2,000 words of story a week on top of school and football, and he didn’t have time to stay up until 1AM talking about coral sprites. Mia stopped coming to half the meetings too, because her Saturday art class ran until 6PM Shenzhen time, which was 6AM ET Friday—right when the call started. She’d sit through the call half-asleep, her camera off, typing one-word responses, until one week her internet cut out and she didn’t rejoin for 45 minutes. Rafa’s internet was so unstable he dropped out of calls 3 times in one meeting, and by the end of the second week, only Lila was showing up to every single call, sitting alone in her bedroom talking to 3 black screens for an hour every Sunday.

They had no shared system for work, so they relied on the group chat for everything. Rafa posted a link to his latest code build at 9PM BRT, but Mia was in art class and Kael was at football practice, so no one saw it for 6 hours. By then, Rafa had already reverted the code because he thought it was broken. Mia posted her first set of turtle sprites in the chat, but the 47 memes and random links posted in the last 2 days had pushed it so far down no one saw it for 3 days. She thought the team hated her art, so she deleted the message and spent 3 days redoing all the sprites for no reason. Kael posted a 10,000-word story draft in a Google Doc, but he didn’t share the link in the chat, so no one knew it existed until he mentioned it in a meeting 2 weeks later, when he’d already rewritten half of it.

Task assignments were so vague no one knew what they were supposed to be doing. Rafa told Mia he needed “coral sprites” but didn’t specify size, color palette, or file format. Mia spent 10 hours drawing 3 hyper-detailed 512x512 coral sprites, only for Rafa to tell her the game engine only supported