If people are bouncing [between Star Citizen and Squadron 42], how does any one thing get done? How do you keep that from becoming just two amorphous blobs that never get finished?
TL;DRThey rely on specialized teams with core members plus flex members, who move only at the end of milestones, to minimize context switching, with key leads staying put and resources committed to better playability.
Yeah, the key is in the specialization, right? So we have teams like, I can give an example, the mission system team, for example, are highly specialized in the online mission system, right? But this assignment, right? You take the resources that are good at one element that one project needs and you can dedicate them. You're not losing anything from the other side, right? The flex obviously is there in your extra kind of chunk of resources, right? Every team has core members and extra members that can flex. And so the idea with this has been to make a plan where we can actually focus on the things that matter, and we pick what we think matters, right? So our player experience team on the SC side helps us with the bug fixes that we're going to be looking at in priority. We know what those are, so we make sure those are covered. So it's about not just prioritization and assignment and just blatantly going SC, Squadron. It's really about looking at, what do we want to achieve? And on SC, we want to achieve better playability. And so we're going to commit resources to that. The flex will come only when we ship, right? That's the moment where flex actually happens, so end of milestones. And so the impact of this will kind of be minimal, because we minimize the context switch on the key resources. Leadership is a key part of this. The right leads in the right places make a big difference. Those ones need to not move.