Starfield lead says the RPG's ending twist was a "panic button" idea to tie things together since the team was "overbooked" making everything else

gamesradar.com:

Starfield's action-packed ending came together in a last-minute scramble after the developers realized that the RPG was lacking a satisfying finale.

As you might be expecting, there will be some Starfield story spoilers just below, so proceed with caution if you haven't finished the game yet. 

Starfield's ending is a dizzying dimension-hopping final battle that zips you around to locations from earlier in the game, and it follows several pretty epic space battles in and around the planet Masada 3, but originally it wasn't quite as exciting or even definitive. 

Speaking at the Game Developers Conference in San Francisco recently (thanks, PC Gamer) as part of a larger talk reflecting on challenges and lessons from Bethesda's latest lengthy dev cycle, Starfield lead quest designer Will Shen, who's since left Bethesda, said the ending was conceived out of "necessity and urgency" after the entire game reached a playable state and the lead developers noticed it was lacking something. 

"We were finally at a state in the project where we could play through the whole [game]. And it became very clear that we were missing the large final location that was going to tie the story together and have a satisfying action-filled payoff," Shen said. "I was both implementing the main quest and leading the quest design team, so I had absolutely no time. The entire quest design team was already overbooked."

If you're wondering exactly how an operation as complex and sophisticated as Bethesda Game Studios could essentially forget to add a proper ending until the last minute, well, according to Shen and former Fallout 76 lead level designer Daryl Brigner, who's also no longer at Bethesda, the sheer size of the 500-strong development team is partly to blame. 

"It's more difficult than ever to know who does what, who you're supposed to report to," Brigner said, with Shen adding that a large, spread-out team can sometimes lead to a "silo effect" in which "every department is scrambling for