Ex-Microsoft Developer Criticizes Longstanding Halo Culture Flaws

Laura Fryer has returned with another blunt assessment of Microsoft's handling of Halo, and this time her criticism goes far beyond one troubled release. Fryer spent decades at Microsoft, joining the company's game development organization in the mid-1990s and working on projects including Crimson Skies, Fighter Ace, Zoo Tycoon, and Gears of War.

She later led Warner Bros. Seattle Studios and became General Manager of Epic Games Seattle, where she oversaw work involving Unreal Engine 4. That background gives her perspective on the unusual weight of studio management. Her latest argument is that Halo Studios, known for most of its history as 343 Industries, had cultural problems almost from the moment it was created.

Fryer says she watched the studio take shape from the office next door while her own team was pushing hard to finish Gears of War 2.

Her team arrived early, left late, and worked weekends, while the newly formed Halo operation often seemed quiet by comparison. From her perspective, that was a worrying way to begin building a team that would eventually inherit one of Microsoft's biggest franchises.

There is some important context here. The new Halo Studios did not immediately have a major Halo release to finish. Bungie had become independent, but it continued producing Halo games, with Halo 3: ODST arriving in 2009 and Halo: Reach in 2010.

During the early years, outside partners also handled several projects connected to the franchise while the internal team expanded. Still, Fryer argues that the central issue was never simply workload. The new organization did not recreate the culture that had made Bungie effective.

Microsoft eventually moved Halo Studios into Bungie's former building in Kirkland, apparently hoping that some physical separation would help reproduce the environment Bungie had enjoyed. Fryer sees that as missing the point. A building could not create the urgency, ownership, collaboration, and shared responsibility that existed among Bungie's developers.

You could inherit a franchise, technology, or office, but you could not simply transfer the culture that made another studio successful.

Talent matters, but a collection of talented people does not automatically become a successful development team. How those people work together, make decisions, take ownership, and push toward a shared deadline can matter as much as the experience written on their resumes.

Fryer believes Halo Studios then made its problems harder by growing into a huge internal operation while also attempting to rebuild Halo's proprietary technology. Halo Infinite became the clearest example of that approach. The team was developing a new engine while targeting new hardware, and other parts of production waited for those tools to be ready.

Former leadership later described the situation as effectively trying to fly a plane while building it. You can see the consequences in Halo Infinite's development history. The game was announced in 2018, but its 2020 gameplay presentation quickly became a major problem after its visuals, and especially the appearance of Craig the Brute, became a widespread joke.

Microsoft delayed the release by an entire year. Even when Halo Infinite finally launched in December 2021, it was missing major features, including campaign co-op and Forge. Online campaign co-op eventually arrived about 11 months later, but official split-screen campaign co-op never returned. That was particularly frustrating because 343 Industries had previously said split-screen would come back after the criticism surrounding Halo 5.

For many longtime Halo Infinite players, the missing feature became another example of the franchise moving away from what had once been standard.

Eventually, Microsoft began changing the leadership and structure around Halo Studios and the franchise. Bonnie Ross left, 343 Industries was renamed Halo Studios, and the proprietary Slipspace Engine was dropped in favor of Unreal Engine. Fryer's criticism, however, is that management still rearranged the organization without fully confronting the culture that caused so many of its problems.

That argument also extends to the way Microsoft has approached Halo's development more broadly. Fryer points to Halo: Combat Evolved as an example of what she believes a much smaller team could accomplish. Microsoft has increasingly relied on a hybrid model, distributing large amounts of work among external partners while maintaining a substantial internal organization around the franchise.

In Fryer's view, that can create an awkward middle ground: you have the bureaucracy and scale of a giant internal publisher operation without the flexibility and speed that can make external development effective. The difference becomes even more striking when you compare the original game with newer projects.

The credits for Combat Evolved list roughly 185 names, but Marcus Lehto and Marty O'Donnell have described the core development group as closer to 45 people. That relatively small team built the engine, campaign, and multiplayer, and delivered the game for brand-new hardware.

By comparison, Fryer points to more than 2,000 names in the Halo: Campaign Evolved's credits.

The project is built with Unreal Engine and focuses specifically on campaign content. Yet it still lacks features many fans consider fundamental, such as traditional split-screen multiplayer. Her argument is not that a larger team is automatically worse. It is that a larger organization must produce enough additional value to justify the added complexity and cost.

Fryer also believes Microsoft spent years changing parts of Halo that did not necessarily need fixing. One example she highlights is the Halo: Campaign Evolved's changes to Cortana's appearance, noting that fans quickly responded by modifying her back to her classic look.

Original Bungie developer faces were also replaced. Those decisions fit into a larger pattern that Fryer sees across the franchise: resources being used to alter familiar elements while other features and priorities remain unresolved. She connects the same thinking to the Halo television series, where Master Chief removes his helmet very early, and the story is placed in a separate Silver Timeline.

Rather than treating established elements as valuable foundations, Fryer argues that Microsoft repeatedly chose to reinterpret them. Her criticism is not simply that change should never happen. Instead, she questions whether every change is worth the development time and money it requires. That concern grows as game development economics tighten.

Every employee hour and every production dollar has to serve a purpose, particularly on a franchise operating at Halo's scale.

If substantial resources are spent redesigning familiar elements that players were already happy with while basic or expected features remain absent, it becomes reasonable to question where the priorities are. According to Fryer, Microsoft may have reached that point with Halo Studios and its internal structure.

She says the next mainline Halo project has moved to a newly assigned Activision team separate from the developers responsible for Call of Duty. Meanwhile, Halo Studios has reportedly been reduced to a smaller support organization focused on maintaining existing games.

If that description is accurate, it would represent a major change after nearly two decades of Microsoft trying to build and maintain an internal studio around the franchise. The implication is that the company has finally accepted that the model it created was not producing the results it needed.

Fryer makes an important distinction, though. Structural problems are management decisions, while layoffs affect individual developers who may have had little or nothing to do with creating those problems. She has said she feels for the people affected, and she made a point of saying that the developers dealing with the fallout didn't necessarily have a hand in the decisions that got the company here.

That puts Halo Studios in a strange spot.

Microsoft has already swapped out its name, its tech, and its leadership, and according to Fryer, it has now changed who is building the next big game too. A different group could bring a fresh approach, but changing developers does not automatically solve every problem surrounding a franchise as large and established as Halo.

For now, the biggest shift may be recognizing that another reset isn't enough. If the underlying problem was always the way the studio operated, replacing an engine or moving people between departments can only go so far. The next era of Halo will ultimately have to show whether Microsoft has actually changed how it builds the franchise, rather than simply changing who holds the reins.