Keeping Your Support Functions as Allies, Not Antagonists: Why Legal, HR, and IT Should Empower Your Game Studio

Support Functions Should Help People Succeed

One of the more interesting patterns I have observed throughout my career is that people rarely talk about support functions until something has gone wrong. Designers discuss game mechanics, producers debate schedules, engineers focus on technical challenges, and artists naturally gravitate toward visual quality. Legal, Human Resources, IT, Finance, and Security often operate quietly in the background, only becoming visible when a contract needs reviewing, a policy has to be enforced, an employee issue arises, or a system stops working. Unfortunately, this often means that an employee’s most memorable interaction with one of these departments occurs during a stressful situation. Over time, those isolated experiences can shape an entire studio’s perception of departments that should, in reality, be some of the company’s greatest sources of support.

That perception matters far more than many leaders realize. If employees view HR as the department that only becomes involved when someone is about to be disciplined, they naturally avoid seeking help when problems first appear. If Legal is viewed as the team that exists solely to reject ideas, people begin looking for ways around legal review rather than involving them early. If IT has built a reputation for saying “no” more often than “let’s figure out how,” employees start finding their own solutions, often introducing greater security or compliance risks than the original request ever posed. None of these reactions are malicious. They are entirely predictable human responses to environments where support functions are experienced as obstacles rather than partners.

What makes this particularly unfortunate is that it represents a fundamental misunderstanding of why these departments exist in the first place. Every successful game studio depends on specialists whose primary responsibility is not creating content but enabling everyone else to create content safely, efficiently, and sustainably. Lawyers help protect intellectual property, negotiate agreements, and reduce unnecessary business risk. HR professionals help recruit talented people, resolve workplace conflicts, develop managers, and build healthier organizational cultures. IT teams maintain the technology that allows hundreds of people to collaborate effectively every day. Finance ensures the company remains healthy enough to continue investing in projects and people. Security protects both the studio’s work and the trust players place in the company. These functions are not separate from the business. They are essential to its success.

Somewhere along the way, however, many organizations unintentionally create a culture where these departments become associated primarily with enforcement instead of enablement. That shift is rarely intentional. It often develops gradually as policies become more numerous, regulations become more complex, and organizations grow larger. Every new process is usually introduced for a sensible reason. Every approval step likely addresses a genuine risk. Every security requirement probably emerged because another company experienced a costly breach or legal dispute. Yet when these individual decisions accumulate without considering how employees experience them, support functions can slowly become departments people interact with reluctantly rather than willingly.

The irony is that this outcome serves neither the employees nor the business particularly well. Organizations often believe they are protecting themselves by making support functions more authoritative, more procedural, or more restrictive. In reality, they frequently make problems harder to detect and more expensive to solve. When employees hesitate to ask questions because they fear the response, small issues remain hidden until they become significant ones. A misunderstanding that could have been resolved during a five-minute conversation eventually develops into a legal dispute, a security incident, or a personnel problem requiring weeks of investigation. The organization has not become safer. It has simply become slower at discovering risks.

Throughout my career, I have been fortunate to work alongside exceptional Legal, HR, IT, Finance, and Security professionals. What separated the best of them from the rest was never their technical competence. That competence was already assumed. What distinguished them was how they approached their role within the organization. They never viewed themselves as gatekeepers standing between employees and the work they wanted to accomplish. Instead, they saw themselves as partners whose responsibility was to help people achieve their goals while navigating genuine business constraints. Their first instinct was rarely, “You can’t do that.” It was much more likely to be, “Let’s figure out how we can accomplish this safely.”

That subtle difference in mindset changes almost every interaction that follows. Employees stop approaching support functions as though they are asking permission from an authority figure and instead begin treating them as experienced advisors who understand risks they may not yet see themselves. Conversations become collaborative rather than defensive because everyone is working toward the same outcome. The objective is no longer to determine whether someone has violated a policy. The objective is to achieve the desired result while protecting both the individual and the company. Trust begins replacing apprehension, and over time that trust becomes one of the strongest cultural assets an organization can develop.

This does not mean support functions abandon their responsibility to protect the company. They absolutely should not. Every one of these departments has legal obligations, regulatory requirements, fiduciary duties, and professional standards that cannot simply be ignored because someone has a good idea or urgent deadline. There will always be occasions where the answer genuinely has to be no. Contracts sometimes cannot be signed. Security exceptions cannot always be granted. Certain workplace behaviours require formal investigation regardless of how uncomfortable those conversations may be. Responsible leadership accepts these realities rather than pretending every request can receive a positive outcome.

The important distinction is that employees should leave those conversations understanding why a decision was made and believing that the department genuinely attempted to help them find the best possible outcome within the available constraints. There is an enormous difference between someone feeling unsupported and someone feeling disappointed by a decision they nevertheless understand and respect. One damages trust. The other often strengthens it because employees recognize that the process was fair, transparent, and motivated by legitimate concerns rather than bureaucracy for its own sake. Leaders who understand this difference build organizations where support functions are respected even when difficult decisions must occasionally be made.

Actionable Steps

• Evaluate how employees currently describe your Legal, HR, IT, Finance, and Security teams. Their perception often reveals more about your culture than internal mission statements.
• Encourage support departments to frame conversations around solving problems safely instead of simply enforcing policy.
• Measure the success of support functions not only by the risks they prevent, but also by the trust they build across the organization.
• Remind leaders that every interaction between employees and support departments either strengthens or weakens long-term organizational trust.

Just Because You Can Doesn’t Mean You Should

One of the biggest mistakes leaders make as organizations grow is confusing legal authority with good leadership. As companies become larger, they naturally acquire additional tools, broader contractual protections, more sophisticated monitoring capabilities, and increasingly detailed workplace policies. Many of these exist for perfectly valid reasons. Studios need to protect confidential intellectual property, secure player data, comply with employment legislation, defend themselves against cyber threats, and ensure valuable assets remain protected. None of those responsibilities are optional, particularly in an industry where a single security breach or leaked project can cost millions of dollars. The mistake occurs when leadership begins assuming that because a particular action is legally permissible, it automatically represents the wisest course of action.

The distinction may seem subtle, but it has enormous implications for organizational culture. Every policy communicates something beyond its immediate purpose. Employees rarely judge rules purely by their legal justification. Instead, they interpret what those rules say about how leadership views them. A policy built on mutual trust communicates that employees are valued professionals capable of exercising good judgement. A policy built entirely around suspicion communicates something very different. Even when the practical impact of two policies is nearly identical, the reasoning behind them shapes how people feel about the organization they work for.

Modern technology has only amplified this challenge. Today’s organizations possess monitoring capabilities that previous generations of leaders could scarcely imagine. Devices can report locations, networks can track activity, collaboration platforms retain extensive communication histories, and security systems can provide remarkable visibility into how people work. In many cases, these capabilities are not inherently intrusive. They exist because they are genuinely useful for protecting company assets, investigating incidents, or maintaining operational security. Problems begin to emerge when organizations start using every capability available simply because the technology allows them to do so.

Employees are remarkably perceptive when it comes to understanding the difference between necessary oversight and excessive surveillance. They generally appreciate that company-owned equipment carries certain expectations around security and appropriate use. Most people understand why sensitive information must be protected or why access to confidential projects should be carefully managed. What damages trust is not responsible security. It is the feeling that leadership is constantly searching for reasons to catch someone doing something wrong. Once employees begin believing they are viewed primarily as potential liabilities rather than trusted professionals, the relationship between the organization and its people changes in subtle but significant ways.

This erosion of trust rarely produces the outcome leaders hope for. Excessive monitoring does not necessarily create more honest communication. Instead, it often encourages more cautious communication. Employees become less willing to ask difficult questions, admit mistakes, or discuss uncertain situations because they worry every interaction may later be interpreted in the least favourable way possible. Ironically, this increases organizational risk because problems remain hidden for longer. People become more focused on protecting themselves than on solving issues collaboratively, and the business ultimately loses the opportunity to address concerns while they are still relatively small.

The same principle extends well beyond technology. Legal agreements can certainly be written to maximize every possible advantage for the company, but contracts that aggressively favour one side often damage long-term relationships before the work even begins. HR policies can technically comply with employment law while still leaving employees feeling unsupported during difficult moments. Managers can enforce every rule exactly as written while ignoring opportunities to exercise empathy or professional judgement. None of these decisions are necessarily illegal. They simply represent leadership choices that prioritize short-term control over long-term trust.

The organizations I have admired most consistently ask an additional question before implementing new policies or exercising existing authority. They do not stop after determining whether something is legally acceptable. They also ask whether the decision reflects the kind of organization they want to become. That second question frequently changes the discussion because it shifts attention away from minimum legal standards and toward leadership values. Sometimes the answer remains exactly the same because the business genuinely has no practical alternative. Other times, however, leaders discover there is a more collaborative approach that achieves the same objective while preserving trust, dignity, and healthy working relationships.

Building that kind of culture requires intentional effort because trust is accumulated gradually through hundreds of relatively ordinary interactions rather than a handful of dramatic moments. Employees notice whether Legal explains the reasoning behind a contract change instead of simply rejecting it. They remember whether HR approached a sensitive issue with compassion as well as professionalism. They appreciate when IT takes the time to understand the problem before proposing a solution instead of immediately pointing to policy. These moments may appear insignificant in isolation, but together they shape whether support functions become departments people seek out early or avoid until circumstances leave them no choice.

Actionable Steps

• Review workplace policies by asking whether they build trust as effectively as they manage risk.
• Challenge leadership teams to distinguish between actions that are legally permissible and actions that strengthen organizational culture.
• Encourage support departments to explain the reasoning behind difficult decisions so employees understand the broader context.
• Look for opportunities to replace unnecessary control with guidance, education, and collaboration whenever business risks allow.

HR Should Develop People, Not Simply Manage Risk

One of the biggest misconceptions about Human Resources is reflected in the name itself. Somewhere along the way, many organizations unintentionally began treating people as resources to be managed rather than individuals whose growth determines the success of the business. While HR has always carried important responsibilities around compliance, employment law, compensation, investigations, and organizational policy, reducing the department to those functions alone fundamentally undervalues what it can contribute to a company. The best HR professionals I have worked with certainly understood legislation and policy, but they also understood people. They recognized that their greatest opportunity to reduce organizational risk did not come from documenting problems after they occurred. It came from helping leaders prevent those problems in the first place.

Unfortunately, many employees never experience that side of HR because the department only becomes visible during difficult moments. Their first meaningful interaction may involve disciplinary action, a grievance, redundancy, or an uncomfortable workplace investigation. Those situations are unavoidable parts of running any organization, but when they become the primary way employees encounter HR, it becomes almost impossible for the department to develop the trust needed to perform its broader role effectively. Employees begin associating HR with consequences rather than support, and managers often hesitate to involve them until situations have already escalated beyond what informal coaching could have resolved.

That hesitation creates unnecessary problems for everyone involved. Workplace conflicts rarely appear overnight. Communication issues, declining performance, interpersonal tension, unclear expectations, and ineffective management behaviours almost always develop gradually over time. If managers feel comfortable approaching HR while those issues are still relatively small, there is often an opportunity to coach individuals, clarify expectations, mediate conversations, or provide additional development before formal intervention becomes necessary. Waiting until the relationship has completely broken down dramatically limits the number of constructive options available. By that point, the organization is frequently choosing between outcomes that are all less desirable than the ones that could have been achieved months earlier.

One of the most valuable contributions HR can make is helping managers become better leaders rather than simply better administrators. Technical expertise rarely prepares someone for their first leadership position. A programmer may become an Engineering Manager because they consistently deliver excellent code. An artist may become an Art Director because of outstanding creative ability. A producer may earn greater responsibility because they successfully managed increasingly complex projects. None of those promotions automatically teach someone how to conduct difficult conversations, motivate different personalities, provide constructive feedback, or resolve conflict between team members. These are learned leadership skills, and HR is uniquely positioned to help managers develop them before poor habits become deeply ingrained.

I have often seen organizations underestimate how much influence frontline managers have over employee experience. Company values, executive presentations, and cultural initiatives certainly matter, but employees usually judge an organization through their direct relationship with their immediate manager. A supportive manager can help people remain engaged during challenging periods. An ineffective manager can undermine even the strongest organizational culture in remarkably little time. HR therefore creates tremendous value when it spends time coaching leaders, improving communication, and strengthening management capability rather than focusing exclusively on policy enforcement. Every stronger manager positively influences an entire team, multiplying the impact of HR far beyond what any individual intervention could achieve.

Career development provides another opportunity for HR to become an indispensable partner rather than an administrative necessity. One of the most common reasons talented people leave organizations is not compensation. It is uncertainty about their future. Employees who cannot see opportunities for growth naturally begin looking elsewhere for them. HR can play an important role in helping leaders create meaningful development plans, identify internal opportunities, encourage mentoring relationships, and ensure people understand how they can continue progressing within the company. These conversations demonstrate that the organization is invested in long-term success rather than simply extracting value from employees until they decide to leave.

None of this diminishes HR’s responsibility to protect the organization when serious issues arise. Investigations, policy enforcement, legal compliance, and difficult employment decisions remain essential responsibilities that cannot be ignored. The difference is that these activities should represent one part of HR’s contribution rather than its defining identity. An organization where employees only interact with HR during moments of crisis has missed an enormous opportunity. A truly effective HR department becomes a trusted advisor that employees and managers willingly involve early because they know its objective is not simply to document problems but to help solve them responsibly.

When HR develops this reputation, the benefits extend well beyond employee satisfaction. Managers become more confident because they know experienced advisors are available when unfamiliar leadership challenges emerge. Employees feel more comfortable raising concerns before frustration turns into resignation. Teams recover from conflict more quickly because conversations happen earlier and with greater support. The organization ultimately becomes more resilient because it spends less time reacting to preventable problems and more time helping people perform at their best. That is a far more valuable contribution than simply ensuring paperwork is completed correctly, even though administrative excellence remains an important part of the role.

Actionable Steps

• Encourage managers to involve HR early when leadership challenges first emerge instead of waiting until formal intervention becomes unavoidable.
• Invest in leadership development programs that strengthen communication, coaching, conflict resolution, and performance management skills.
• Position HR as a long-term career partner by supporting employee development, mentoring, and internal growth opportunities.
• Evaluate HR not only by compliance metrics but also by its contribution to stronger leadership, healthier teams, and employee retention.

Legal Should Enable Business, Not Stop It

Few departments develop an unfair reputation faster than Legal. Ask people across almost any industry what they think lawyers do inside their organization, and you will often hear remarkably similar answers. They slow projects down. They complicate agreements. They identify problems instead of solutions. They exist to tell everyone what they cannot do. While there are certainly organizations where Legal has developed this reputation honestly, I have found that the perception is often less about the advice itself and more about how that advice is delivered. The most effective legal professionals I have worked alongside were never trying to stop the business from moving forward. They were trying to help it move forward without creating unnecessary risk.

That distinction fundamentally changes the relationship between Legal and the rest of the organization. Every business faces constraints. Intellectual property must be protected, contracts need careful negotiation, regulatory obligations have to be respected, and commercial risks cannot simply be ignored because a project feels exciting. Those realities exist whether people enjoy them or not. The question is how Legal chooses to participate in solving those challenges. There is an enormous difference between responding to a proposal by saying, “You can’t do that,” and responding by saying, “Here are the risks we need to address before we can move forward safely.” Both responses acknowledge the same legal concerns, but only one invites collaboration.

This collaborative mindset becomes particularly valuable within game development because our industry thrives on experimentation. Studios constantly explore new business models, emerging technologies, novel gameplay systems, licensing opportunities, community initiatives, and partnerships that may not fit neatly into familiar templates. Legal departments that understand the commercial objectives behind these discussions can often identify creative solutions that allow innovation to continue while still protecting the company. Rather than becoming the final approval step that everyone dreads, they become trusted advisors who help shape ideas into something both commercially viable and legally sustainable.

One habit that separates exceptional legal professionals from merely competent ones is curiosity. Before offering advice, they invest time understanding what the team is actually trying to accomplish. The initial proposal presented to Legal is often only one possible solution to a broader business objective. Once they understand the underlying goal, they may discover alternative structures that achieve the same commercial outcome with significantly less legal exposure. That conversation rarely happens if the discussion ends after identifying why the original proposal creates problems. It requires Legal to see itself as part of the solution rather than simply the organization responsible for identifying risk.

The same principle applies to contract negotiations. Every agreement contains areas where parties naturally have competing interests, and Legal has an important responsibility to protect the company’s position. At the same time, contracts also establish the foundation for long-term business relationships. Winning every individual clause at the expense of trust rarely produces the strongest partnerships. Experienced legal teams understand when a particular issue deserves firm negotiation and when flexibility may create greater long-term value. They appreciate that successful business relationships are rarely built on one side extracting every possible advantage simply because the wording allows it.

I have also found that Legal departments build far stronger relationships when they invest time educating the rest of the organization. Many disagreements arise not because employees are resisting legal advice, but because they do not fully understand the reasoning behind it. Explaining intellectual property considerations, contractual obligations, privacy requirements, or regulatory risks in language people can actually understand dramatically improves collaboration. Once teams appreciate why certain constraints exist, they often become much better at identifying compliant solutions themselves. Education therefore becomes another form of risk reduction, one that strengthens the entire organization rather than relying exclusively on centralized review.

Perhaps most importantly, Legal should never become a department employees avoid until the final possible moment. By then, options are usually far more limited because commitments have already been made, timelines have been established, or commercial expectations have been created. Early collaboration almost always produces better outcomes because adjustments remain relatively inexpensive while ideas are still flexible. When teams trust Legal as a partner, they seek guidance before problems emerge rather than after they have become significantly more difficult to resolve. That proactive relationship benefits everyone involved, including the lawyers themselves.

Ultimately, Legal creates its greatest value when it enables confident decision-making rather than hesitant decision-making. Leaders should leave legal discussions with a clear understanding of the risks they are accepting, the protections available to them, and the practical steps required to move forward responsibly. That confidence allows organizations to innovate without being reckless and to protect themselves without becoming paralysed by unnecessary caution. In an industry built on creativity, that balance is one of the most valuable contributions any legal team can provide.

Actionable Steps

• Involve Legal during idea development rather than waiting until projects are largely complete.
• Encourage lawyers to understand commercial objectives before recommending solutions.
• Invest in legal education that helps non-legal teams understand key business risks and obligations.
• Measure Legal’s success not only by the risks it prevents but also by its ability to help the organization move forward with confidence.

IT and Security Should Be Productivity Multipliers

Ask almost any development team what they value most from their IT department and the answers are remarkably consistent. They want reliable systems, responsive support, secure infrastructure, and as little unnecessary friction as possible. Developers want to build games, artists want to create art, designers want to prototype mechanics, and producers want projects to remain on schedule. Very few employees arrive at work hoping to spend their day dealing with technical obstacles. That is why IT has such an extraordinary opportunity to shape the daily experience of everyone in the studio. When technology works well, people barely notice it. When it does not, productivity across the entire organization can grind to a halt.

The challenge is that IT often finds itself balancing two responsibilities that can appear contradictory on the surface. On one hand, it must enable employees to work quickly and efficiently. On the other, it must protect valuable intellectual property, secure sensitive information, maintain stable infrastructure, and reduce cybersecurity risks. Poorly balanced organizations sometimes lean so heavily toward security that everyday work becomes unnecessarily difficult. Others prioritise convenience so aggressively that they expose themselves to preventable breaches. Neither extreme serves the company particularly well. Effective IT departments recognise that productivity and security are not competing objectives. They are complementary goals that must be designed together.

Security illustrates this balance particularly well. Most employees understand why studios invest heavily in protecting confidential projects. Leaks can damage publisher relationships, undermine marketing strategies, expose intellectual property, and create significant financial consequences. The question is not whether security matters. The question is whether security is experienced as something imposed upon employees or something achieved alongside them. When security professionals treat staff as partners in protecting the studio, employees become far more willing to report suspicious activity, admit mistakes, and ask questions before small incidents become major breaches. Fear rarely creates that level of openness.

Education is one of the most effective tools IT and Security possess, yet it is often undervalued. Employees cannot be expected to follow good security practices if they only encounter the subject through mandatory compliance training once a year. People are far more likely to adopt healthy behaviours when they understand why those behaviours matter and how they directly contribute to protecting the projects they care about. Short conversations, practical guidance, approachable documentation, and responsive support frequently produce better security outcomes than increasingly restrictive technical controls introduced without explanation.

The best IT teams I have worked with understood that every support request represented more than a technical problem. It was an interruption to someone’s ability to perform their job. That perspective changes how support is delivered because resolving issues quickly is no longer simply about service levels or help desk metrics. It is about helping colleagues return to productive work with as little disruption as possible. Employees remember departments that approach problems with curiosity, patience, and a genuine desire to help. Over time, those positive experiences encourage people to involve IT earlier, making it easier to prevent larger technical issues before they affect wider teams.

Technology continues to evolve rapidly, and game studios now rely on increasingly complex ecosystems of cloud services, remote collaboration tools, development environments, version control systems, artificial intelligence, and distributed infrastructure. This complexity makes partnership even more important. No single department can maintain security or operational resilience in isolation. Developers, artists, producers, HR, Legal, Finance, and executive leadership all contribute to protecting the organization through their daily decisions. IT therefore creates its greatest value not by standing apart from the rest of the business but by becoming deeply integrated into how that business operates.

When employees trust IT and Security, they stop viewing policies as arbitrary restrictions and begin understanding them as practical safeguards that protect everyone’s work. They become more comfortable reporting phishing attempts, admitting accidental mistakes, discussing new technology before adopting it, and collaborating on better ways to solve emerging challenges. That level of openness cannot be mandated through policy alone. It develops because people believe the departments responsible for protecting the organization are also genuinely committed to helping them succeed. In the long run, that trust becomes one of the strongest security controls any company can possess.

Actionable Steps

• Design security processes that support productivity instead of creating unnecessary barriers to everyday work.
• Invest in continuous education that helps employees understand both the purpose and practical application of security practices.
• Treat every IT support request as an opportunity to strengthen trust and improve the employee experience.
• Encourage collaboration between IT, Security, and development teams so new technology can be adopted responsibly without slowing innovation.

Culture Starts at the Top

By the time a support function has earned a reputation as “the department that always says no,” the problem has usually existed for quite some time. These reputations rarely appear because of a single bad interaction or one unpopular policy. Instead, they are built gradually through hundreds of conversations, decisions, and leadership behaviours that collectively teach employees what they should expect whenever they engage with Legal, HR, IT, Finance, or Security. That is why I have never believed these perceptions belong solely to the departments themselves. They are reflections of organizational culture, and organizational culture is ultimately shaped by leadership. CEOs, studio heads, and executive teams decide what behaviours are rewarded, what attitudes are tolerated, and what role support functions are expected to play within the business.

This is one of the reasons I become uncomfortable when I hear executives complain that their HR department is unpopular or that Legal is viewed as an obstacle to progress. Those observations may be accurate, but they also reveal something about executive leadership. Departments rarely decide their own purpose in isolation. They respond to the expectations placed upon them. If leadership consistently rewards Legal for preventing risk while never recognizing the value of enabling innovation, Legal will naturally become more conservative over time. If HR is measured almost exclusively on policy compliance and disciplinary processes, those activities will inevitably become the centre of its identity. If IT is only praised when security incidents are avoided, employees should not be surprised when every new request is viewed primarily through the lens of risk rather than productivity.

Metrics are powerful because they communicate what an organization truly values. A company may publicly describe HR as a strategic partner, but if every executive meeting focuses solely on turnover reports, compliance statistics, and legal exposure, that description quickly loses credibility. The same applies to every support function. People naturally devote more attention to the outcomes that influence performance reviews, budgets, promotions, and executive recognition. If leaders want departments that actively support innovation, collaboration, and employee success, they must ensure those contributions are measured, discussed, and celebrated alongside traditional operational metrics. Otherwise, the organization unintentionally reinforces the very behaviours it later complains about.

Leadership also establishes the tone for how support functions interact with the rest of the business. I have seen executive teams introduce Legal as though they were the final authority that everyone must satisfy before making progress. I have also seen leaders introduce lawyers as experienced advisors whose role is to help the company navigate complex commercial decisions successfully. Those two introductions may appear similar on the surface, but they create entirely different expectations. The first positions Legal above the business. The second positions Legal within the business. Employees immediately understand whether they are expected to collaborate with support functions or simply comply with them.

The same principle extends into everyday management. Executives often influence culture through seemingly minor comments that they barely remember making. A manager joking that “HR is coming for you” may believe they are simply trying to lighten the mood, but repeated comments of that nature reinforce the idea that HR exists primarily as an enforcement body. Referring to Legal as “the fun police” or rolling your eyes every time IT introduces a new security requirement has a similar effect. Leaders frequently underestimate how closely employees observe these interactions. The behaviour executives normalize quickly becomes the behaviour managers repeat throughout the rest of the organization.

One of the healthiest practices I have witnessed is including support functions in strategic discussions long before decisions have been finalized. Rather than inviting Legal after a commercial agreement has already been negotiated, involve them while opportunities are still being evaluated. Instead of asking HR to manage organizational change after restructuring decisions have been made, include them while those decisions are still being shaped. Bring IT and Security into conversations about new technology before commitments have been announced to the wider business. These early discussions almost always produce better outcomes because support functions contribute expertise while there is still genuine flexibility to adjust plans without creating unnecessary disruption.

Executive leadership also has a responsibility to protect support departments from becoming overwhelmed by unnecessary bureaucracy. It is remarkably easy for organizations to solve every isolated problem by introducing another approval step, another mandatory form, another reporting requirement, or another policy. Individually, each addition may seem entirely reasonable. Collectively, they can create processes so cumbersome that employees begin searching for ways to avoid them altogether. Strong leaders periodically ask whether existing procedures are still serving their intended purpose or whether they have gradually become obstacles that consume time without creating equivalent value. Simplifying unnecessary bureaucracy benefits everyone, including the departments responsible for administering it.

Ultimately, employees judge leadership not only by the decisions executives make but also by the relationships they encourage throughout the organization. When support functions are respected, approachable, and genuinely invested in helping people succeed, collaboration becomes significantly easier. Problems are identified earlier, decisions improve, and trust grows steadily over time. None of those outcomes occur by accident. They emerge because leadership intentionally designed a culture where expertise is shared freely rather than protected behind organizational boundaries.

Actionable Steps

• Measure support functions by the value they create for employees as well as the risks they manage for the business.
• Include Legal, HR, IT, Finance, and Security early in strategic discussions rather than only during implementation.
• Eliminate language that portrays support functions as adversaries or obstacles within the organization.
• Regularly review policies and approval processes to ensure they remain useful instead of becoming unnecessary bureaucracy.

Protect the Company by Supporting the People

One of the most persistent myths in corporate leadership is the belief that protecting employees and protecting the company are somehow competing priorities. While there are certainly situations where difficult decisions must be made, I have found that, in the overwhelming majority of circumstances, these goals are remarkably well aligned. Organizations perform better when talented people trust their leaders, communicate openly, ask questions without fear, and believe they will be treated fairly. Those same conditions also reduce legal exposure, improve retention, strengthen security, encourage innovation, and create healthier commercial relationships. The interests of employees and the interests of the business intersect far more often than many organizations acknowledge.

This is particularly true in creative industries such as game development, where success depends heavily on collaboration. Great games are rarely the result of isolated brilliance. They emerge because designers, engineers, artists, producers, writers, QA, audio specialists, marketing teams, and countless other professionals share ideas freely while solving complex problems together. That level of collaboration depends upon trust. People contribute more confidently when they believe mistakes will become learning opportunities rather than immediate disciplinary issues. They raise concerns earlier when they expect support instead of blame. They challenge assumptions more openly when psychological safety allows healthy disagreement without fear of personal consequences.

Support functions play an essential role in creating this environment because they influence how employees experience the organization during many of its most important moments. HR shapes onboarding, career development, conflict resolution, performance conversations, and organizational change. Legal influences partnerships, licensing, intellectual property, and commercial negotiations. IT determines whether people have reliable tools and responsive support. Security establishes how the company protects valuable assets without undermining productivity. Finance enables investment while ensuring long-term sustainability. Every one of these departments affects whether employees feel empowered or constrained in their daily work.

When these functions approach their responsibilities through the lens of partnership, remarkable things begin to happen. Employees become more willing to admit mistakes because they trust the response will focus first on solving the problem rather than assigning blame. Managers seek advice before situations escalate because they know they will receive practical guidance instead of criticism. Teams begin involving Legal during the early stages of commercial discussions because they believe lawyers will help identify workable solutions rather than automatically rejecting ambitious ideas. Security incidents are reported more quickly because employees understand that transparency protects everyone more effectively than silence. Each of these improvements reduces organizational risk while simultaneously strengthening employee confidence.

The opposite culture produces very different outcomes. Employees become increasingly careful about what they share because they worry information may later be used against them. Managers delay difficult conversations until problems have become far more complicated than they needed to be. Departments begin solving issues independently rather than seeking expert advice because involving support functions is perceived as slowing progress or inviting unnecessary scrutiny. None of these behaviours appear in official company policies, yet they emerge naturally whenever trust begins to erode. The organization may believe it has strengthened control, but in reality it has simply reduced visibility into what is actually happening.

This is why I believe servant leadership applies just as strongly to support functions as it does to any other leadership discipline. Supporting people does not mean avoiding difficult conversations or refusing to enforce important policies. It means approaching those responsibilities with the mindset that your expertise exists to help others succeed. Sometimes helping someone succeed means explaining a legal risk they had not considered. Sometimes it means investigating a complaint thoroughly to ensure fairness for everyone involved. Sometimes it means denying a request because the long-term consequences genuinely outweigh the short-term benefits. Partnership is not defined by always saying yes. It is defined by genuinely trying to achieve the best possible outcome for everyone affected by the decision.

Organizations that embrace this philosophy often discover something interesting. Compliance improves because people understand the reasoning behind policies rather than simply memorizing the rules. Security strengthens because employees willingly report concerns instead of hiding them. Employee engagement increases because people believe their wellbeing genuinely matters. Retention improves because talented individuals prefer working in environments where they feel respected and supported. Commercial relationships become healthier because partners experience collaborative problem solving rather than rigid bureaucracy. None of these outcomes require abandoning professional standards. They require applying those standards with empathy, transparency, and good judgement.

Protecting the company has never been about creating the highest possible number of rules. It has always been about building an organization capable of making consistently good decisions. Support functions contribute enormously to that objective when they educate, advise, coach, and collaborate alongside the rest of the business. Their greatest value is not simply preventing mistakes. It is helping the entire organization become more capable, more informed, and more confident over time.

Actionable Steps

• Design policies that encourage employees to seek help early rather than avoid difficult conversations.
• Reward collaboration between support functions and operational teams instead of reinforcing departmental silos.
• Treat education, coaching, and transparency as essential risk management tools alongside compliance and enforcement.
• Evaluate organizational trust regularly because it often predicts future business performance more accurately than many traditional operational metrics.

Final Thoughts

Whenever I hear someone describe Legal, HR, IT, Finance, or Security as “necessary evils,” I usually find myself wondering how that organization arrived at that conclusion. These departments perform work that every successful company depends upon. They protect intellectual property, maintain secure infrastructure, recruit talented people, develop leaders, manage commercial relationships, ensure financial stability, and help organizations navigate increasingly complex legal and regulatory environments. There is nothing inherently adversarial about those responsibilities. The adversarial reputation develops because of how those responsibilities are experienced by employees, not because of the work itself.

Looking back across my own career, the strongest support departments were never the ones that simply enforced policy more aggressively than everyone else. They were the ones that consistently demonstrated they understood the business they were supporting. They invested time learning how development teams worked, why deadlines mattered, how creative decisions were made, and what pressures managers faced every day. Because they understood those realities, their advice became more practical, their recommendations became more collaborative, and their relationships with the rest of the organization became significantly stronger. People sought them out not because they were required to, but because they genuinely improved the quality of decision-making across the studio.

That level of trust does not remove the difficult parts of these roles. HR will still conduct investigations. Legal will still reject agreements that expose the company to unacceptable risk. IT will still enforce security requirements that occasionally inconvenience employees. Finance will still decline spending requests that cannot be justified responsibly. Those responsibilities remain essential, and avoiding them would be neither professional nor responsible. The difference is that employees understand those decisions are being made by departments that have consistently demonstrated they are trying to help, not simply trying to control.

For executive leaders, I believe this represents one of the most important cultural choices they make. Every organization teaches employees what support functions are for. Some teach that these departments exist primarily to enforce rules and catch mistakes. Others teach that they exist to help talented people navigate complex challenges safely and responsibly. Those lessons are communicated through everyday interactions, leadership behaviour, performance metrics, and organizational priorities far more than through mission statements or internal presentations. If leaders genuinely want support departments that are trusted, they must intentionally build an environment where trust becomes part of how success is measured.

The most successful game studios understand that protecting the business and supporting the people are not opposing goals. They recognise that exceptional games are built by talented individuals who are given the tools, guidance, confidence, and support necessary to do their best work. Legal, HR, IT, Finance, Security, and every other support function contribute directly to creating that environment when they see themselves as partners in the studio’s success. Their work may often happen behind the scenes, but its impact is visible in healthier cultures, stronger collaboration, better decisions, and organizations that continue to thrive long after individual projects have shipped.

If there is one lesson I hope leaders take away from this discussion, it is that support functions should never aspire to become departments employees tolerate. They should aspire to become departments employees trust. When people feel comfortable asking questions, admitting mistakes, seeking guidance, and involving experts early, organizations become more resilient because problems are addressed before they grow into crises. In my experience, that is one of the most effective ways a company can protect itself. The strongest support functions are not remembered because of the number of policies they enforced. They are remembered because they quietly helped talented people succeed, and in doing so, helped the entire business succeed alongside them.