The gaming industry has become painfully familiar with the same story. A massive corporation buys a development studio, promises investment and a bright future, restructures it and then, sometimes only a few years later, shuts the entire studio down.
The company moves on. The executives move on. The IP usually remains safely tucked away inside a corporate portfolio.
The developers are the ones left looking for another job.
GamingHQ believes there should be much stronger financial consequences when giant technology and gaming companies acquire studios and later decide to close them.
Buying a Studio Means Taking Responsibility
Acquiring a developer should mean more than purchasing its games, intellectual property and potential revenue.
You are also acquiring a functioning company filled with people who built their careers around that studio.
Developers may remain after an acquisition because they believe the new owner offers greater stability. Others might relocate, abandon other opportunities or spend years working on projects that ultimately disappear when corporate priorities change.
Then a restructuring happens.
Projects are cancelled. Teams are reduced. Eventually, the studio itself can disappear.
For a corporation worth billions, closing one development studio can become another line in a financial report.
For the people working there, it can change their entire lives.
A Normal Fine Wouldn’t Be Enough
Simply giving a corporation a relatively small regulatory fine wouldn’t accomplish much.
The financial consequence would need to be substantial enough that closing an acquired studio becomes something executives seriously consider before signing off on it.
More importantly, a significant portion of that money should benefit the affected employees directly.
That could mean mandatory enhanced severance packages, extended salaries, healthcare coverage where applicable, retraining budgets and financial support for relocation.
If a corporation made the decision to acquire the studio, it should carry greater responsibility when it later decides that studio no longer fits its plans.
There Could Be an Acquisition Protection Period
One possibility would be introducing additional protections for studios following major acquisitions.
Imagine a corporation purchasing a developer and then being subject to stronger employee protections for the following five or ten years.
Closing the studio during that period could trigger mandatory compensation based on factors including the number of employees affected, how long they worked there and how recently the acquisition happened.
The larger the corporation and the greater the disruption caused by the closure, the greater that responsibility could become.
That would not make studio closures impossible.
It would simply make them expensive enough that employees cannot be treated as disposable parts of an acquisition.
Give Developers the Chance to Survive
There should also be alternatives before a studio is completely dismantled.
If the parent company no longer wants a developer, why should closure automatically be the answer?
The company could be required to investigate selling the studio first.
Original founders, employees, another publisher or outside investors could potentially take ownership and allow the developer to continue independently.
Employee buyouts could also become an option in certain circumstances.
The parent company might still retain specific intellectual property depending on the acquisition agreement, but the actual development team could survive.
Closing the doors should be the final option rather than the easiest one.
Not Every Closure Is Corporate Greed
There also needs to be some balance.
Not every studio succeeds.
Games can perform badly, projects can collapse during development and studios can become financially unsustainable. Keeping hundreds of people employed indefinitely on unsuccessful projects isn’t realistic.
That is why any regulation would need clearly defined conditions.
The size of the parent company, circumstances surrounding the acquisition, number of layoffs, time since the acquisition and financial condition of the studio could all matter.
There is a major difference between an independent developer running out of money and a multinational corporation deciding that a studio it purchased several years earlier no longer fits its strategy.
The law should be capable of recognising that difference.
Acquisitions Should Come With Consequences
Microsoft, Sony and other enormous companies have enough resources to purchase studios and intellectual property worth hundreds of millions or even billions.
With that purchasing power should come responsibility.
If you buy a development studio, you are not simply buying a logo and a catalogue of games.
You are taking control of people’s careers.
Corporations should still be allowed to restructure their businesses when necessary, but acquiring a studio and later shutting it down should carry significantly greater obligations toward the employees who lose their jobs as a result.
If closing an acquired studio came with substantial mandatory compensation, companies might also think considerably harder before buying developers simply because they have the money to do so.
Perhaps that wouldn’t stop every studio closure.
But at least the people who actually created the games wouldn’t be the ones carrying almost all of the consequences.
