The GamesIndustry.biz HR Summit, held on October 1, served as a platform for a recurring theme that resonated throughout the day’s sessions: the influence of generative AI on the modern workplace. While some attendees highlighted the technology’s ability to accelerate certain aspects of game development—such as code generation or the automation of repetitive chores—the consensus was that AI is far from the miracle solution championed by its most enthusiastic supporters.
In fact, many argued that the very same tools designed to streamline processes are spawning a host of new challenges for studios, ranging from data‑privacy fears to heightened employee stress and an unexpected surge in HR workload. One senior executive stressed that their studio takes a painstaking approach to ensure no AI‑produced material ever makes it into a shipped title.
(The summit operated under Chatham House Rules, so specific company names were not disclosed.) Yet the same leader acknowledged that AI does have a place elsewhere in the business. "It’s a delicate balance," they said, noting that AI could be valuable for routine, low‑creativity tasks that developers typically dread.
The potential for efficiency is real, but it must be weighed against the broader implications for staff morale and operational risk. Employee anxiety emerged as a recurring motif.
One participant recounted late‑night emails from team members asking, "Are we using AI? Does that mean I’m going to lose my job?" That unease is not confined to rank‑and‑file staff; managers themselves are uneasy about the direction AI is taking and how to plan for an uncertain future. "We simply don’t know what the landscape will look like," admitted another senior leader, underscoring the difficulty of crafting long‑term strategies in a rapidly evolving field. Policy development is another area where the pace of change is causing headaches.
A poll at last year’s summit revealed that only a minority of companies had formal AI policies. This year, most respondents claimed to have a policy in place, yet many admitted those documents are already outdated.
"I wrote a policy two weeks ago, and yesterday I learned about a new prompt‑injection technique that forces me to rewrite sections," one leader explained. The speed at which new threats and use‑cases emerge makes it hard for HR teams to keep guidelines current. Data leakage remains a top concern. Even when studios purchase enterprise‑grade AI models that promise not to retain proprietary information for training, they have limited control over how individual employees use consumer‑grade tools like ChatGPT on personal accounts.
"Someone could be feeding confidential NDA‑covered material into a public model, and there’s little we can do to stop it," warned a participant. The prevailing advice is to clarify acceptable versus prohibited behavior rather than attempt impossible technical restrictions.
Confusion about AI’s proper role was also evident. "The biggest issue right now is that AI is presented as the answer, but people don’t know what the question is," said a speaker who described multiple studios eager to "use more AI" without a clear purpose. The hype surrounding AI as a universal panacea is clashing with the reality that, for many, it has yet to produce genuinely fun or innovative experiences.
One senior attendee bluntly observed, "I haven’t seen AI create anything enjoyable. It can replicate, sure, but it hasn’t delivered fun yet." Despite differing viewpoints, the summit’s overarching message was unmistakable: AI cannot be ignored. Whether a studio decides to embrace or reject generative tools, that stance must be codified in employee guidelines and consistently enforced.
Understanding the current capabilities of AI, aligning them with organizational values, and assessing both risks and opportunities is essential. As one speaker put it, AI is now encroaching on creative disciplines that five years ago were considered untouched by such technology.
The journey of AI adoption is still in its infancy. One session outlined a four‑stage model, from casual experimentation to becoming an AI‑first organization. Most companies remain in the first stage—perhaps purchasing an enterprise license for a model like Claude to let developers tinker with code generation. Larger studios are moving into stage two, piloting AI in specific pipelines and weighing time savings against cost, compliance, and reputational risk.
Without strict governance, experimentation can backfire. An anecdote described an artist who used Gemini to generate shader code while a programmer was away. The resulting code violated the studio’s coding standards and AI policy, went unnoticed for weeks, and ultimately forced a build rollback.
In another case, a freelancer employed AI to produce artwork that impressed the community, but the studio realized the cost‑saving narrative was misleading once the AI involvement was uncovered. Pilot projects often expose deeper flaws in studio processes.
"Most of them collapse because workflows rely on tacit knowledge rather than documented procedures," a speaker noted, highlighting the danger of building AI solutions on shaky foundations. From a human‑resources perspective, there are both bright spots and dark clouds. AI can help staff draft clearer emails or provide instant answers to routine queries about maternity or sick leave, acting as a useful prompt for those struggling to articulate their thoughts.
However, the technology is also generating more work for HR teams. Several attendees reported a surge in AI‑crafted grievance letters—often lengthy, factually inaccurate, and peppered with odd legal citations.
One legal professional said they receive about ten such letters weekly, each requiring careful review despite their questionable content. HR professionals are obligated to read and respond to these submissions, even when they are riddled with errors.
This adds to their workload rather than alleviating it. One participant recounted a nine‑page grievance that was largely incomprehensible, illustrating how AI can complicate even minor disputes. While banning AI‑generated complaints outright might seem tempting, it could be viewed as discriminatory against employees who rely on assistance for writing.
A possible mitigation strategy discussed was to set limits on grievance length or request specific, verifiable details that an AI would not possess, thereby forcing the employee to provide genuine information. Nonetheless, the overall impression was that generative AI is, at present, creating more tasks for HR rather than reducing them. "We’ve seen HR teams shrink in size, but the volume of work has stayed the same or even increased," one attendee observed. "Often, using AI ends up giving me more to do." Finally, the human element cannot be replaced.
While AI can answer policy questions, it lacks empathy, emotional intelligence, and the ability to read body language. An employee seeking advice about a sensitive maternity situation may receive a factual response but miss the compassionate support a human HR representative could provide.
As one speaker concluded, "That connection with people is the glue that brings it all together."