Why Servant Leadership Creates Stronger Teams, Healthier Studios, and Better Games Through Genuine Support Instead of Authority
How Can I Help You?
Leadership Is Not About Having All the Answers
One of the biggest misconceptions people have about leadership is that becoming a leader means becoming the person with all the answers. It is an easy assumption to make because many organizations unintentionally reinforce it through the way people are promoted and recognized. Someone demonstrates technical expertise, consistently solves difficult problems, delivers strong results, and eventually receives greater responsibility because of those accomplishments. The qualities that helped them become a leader can then create the impression that leadership means continuing to be the smartest person in the room or the individual everyone turns to whenever something goes wrong. In reality, one of the most difficult transitions into leadership is recognizing that the skills that earned you the position are not necessarily the skills that will make you effective once you are there.
The longer I have worked in the video game industry, the more I have come to believe that leadership has far less to do with personally solving every problem and far more to do with creating an environment where other people can solve problems successfully. That shift in perspective rarely happens overnight because it requires leaders to give up some of the behaviours that previously demonstrated their value. It usually develops after leading enough teams, making enough mistakes, and eventually recognizing that no matter how experienced you become, you will never possess all the knowledge, creativity, or expertise required to build a successful game by yourself. Game development is simply too collaborative and too specialized for any individual to understand every part of it at the necessary depth. A leader who continues trying to be the answer to everything eventually becomes limited by the boundaries of their own knowledge.
Every project brings together designers, programmers, artists, animators, writers, producers, audio specialists, QA professionals, marketers, community managers, and many other disciplines. Each of those people brings specialized knowledge that may have taken years or decades to develop, and good leadership begins by respecting that expertise rather than trying to compete with it. A technical director will understand challenges that a creative director may never fully appreciate, while a UI artist may recognize usability problems long before a producer sees them reflected in testing or metrics. A gameplay programmer may identify a technical limitation that fundamentally changes how a feature should be designed, and an experienced QA professional may recognize a pattern of instability before anyone else understands its significance. Leadership does not diminish because other people know more about their disciplines. It becomes stronger when the leader knows how to bring that expertise together and create the conditions in which it can be used effectively.
Once you accept that reality, the role of leadership begins to look very different. Your primary responsibility stops being the delivery of answers and becomes understanding what the team needs in order to succeed. Sometimes that means providing clear direction when priorities are uncertain, and sometimes it means making a difficult decision when consensus is impossible or time is running out. It may involve protecting the team from unnecessary distractions, advocating for resources with executives or publishers, resolving organizational conflicts, or providing context that helps people understand why a decision has been made. Increasingly, however, leadership becomes less about demonstrating what you can personally do and more about enabling everyone around you to do what they are capable of doing.
That is why I have come to value one very simple question in leadership: “How can I help you?” There is nothing particularly sophisticated about those five words, and they certainly do not constitute a revolutionary management framework. They require no elaborate presentation, certification, leadership seminar, or complicated organizational theory. Their value comes from the change they create in the starting point of a conversation. Instead of beginning with what someone has failed to accomplish or what leadership expects them to deliver next, the question begins by trying to understand what might be preventing them from succeeding.
The important part is that the question has to be sincere. Employees are remarkably good at recognizing the difference between genuine curiosity and a management technique someone has recently decided to practice. If “How can I help you?” becomes another item on a leadership checklist, people will quickly recognize that nothing meaningful happens after they answer it. They will become cautious about what they share, particularly if previous attempts to raise concerns have resulted in criticism, dismissal, or no action at all. A question designed to build trust can actually weaken trust when the behaviour that follows demonstrates that leadership was never particularly interested in the answer.
When the question comes from genuine curiosity and is supported by consistent action, it communicates something much more important than the words themselves. It tells people they are not expected to struggle alone and that encountering a problem is not automatically evidence of poor performance. It demonstrates that their leader is paying attention to the environment surrounding their work rather than evaluating results without considering the conditions that produced them. It also makes asking for assistance feel more normal because leadership has already established that support is part of the relationship. Over time, this can change the way employees perceive leadership from an authority that primarily evaluates them into a partner that is genuinely invested in helping them succeed.
None of this eliminates accountability, nor should it. Teams still need clear expectations, measurable goals, honest feedback, deadlines, quality standards, and people who take responsibility for the commitments they make. Supporting someone does not mean lowering expectations every time they encounter difficulty, and asking how you can help does not transfer ownership of their responsibilities to the leader. The strongest leaders I have worked with were capable of demanding high standards while simultaneously making it clear that nobody was expected to navigate every obstacle alone. Supporting people and holding them accountable are not competing philosophies of leadership when both are practiced properly; support can actually make accountability stronger because people have fewer reasons to hide the problems preventing them from meeting expectations.
Looking back across my own career, I rarely remember leaders because they consistently had the perfect answer to every problem. I remember the people who made it clear that my success genuinely mattered to them and who were willing to invest time in helping me become more capable. They challenged me when I needed to be challenged, but they also listened when I needed help understanding something I had not encountered before. They did not interpret every request for assistance as evidence that I was incapable of doing my job. That combination of expectation and support has influenced the way I think about leadership far more than any attempt to appear like the smartest person in the room.
Why These Five Words Matter So Much
Most interactions between leaders and their teams naturally contain some form of evaluation. Leaders ask for status updates, review milestones, examine schedules, assess quality, discuss budgets, and identify risks because organizations need visibility into whether work is progressing as expected. None of those conversations are inherently negative, and effective game development would be impossible without them. The problem appears when nearly every interaction an employee has with leadership begins from the perspective of measurement. When that happens consistently, people can gradually begin associating leadership with oversight rather than support, which changes what they are willing to share.
Employees who believe every conversation is an evaluation become more cautious about admitting uncertainty. They may attempt to solve increasingly complicated problems themselves because asking for assistance feels like acknowledging that they are not performing at the expected level. Sometimes that independence is healthy and produces exactly the kind of growth leaders should encourage. At other times, a relatively small issue develops into a significant production problem because the person involved waited too long to raise it. By the time leadership becomes aware, an obstacle that might have required a short conversation several weeks earlier now affects schedules, dependencies, budgets, or other teams.
Approaching the same conversation from a position of support changes the dynamic considerably. When a leader asks how they can help, they signal that the purpose of the discussion is not simply to determine whether progress has occurred but to understand what may be preventing it. That distinction makes it easier for people to discuss obstacles because they are no longer immediately placed in the position of defending their performance. The conversation can move toward understanding dependencies, clarifying priorities, finding resources, or identifying decisions that need to be made. Instead of leadership discovering problems only after they have become visible through missed milestones, the organization creates more opportunities to address them while they are still manageable.
This is particularly valuable in game development because so many problems exist between disciplines rather than entirely within one of them. A designer may be blocked because engineering resources are unavailable, while engineering may be waiting for specifications that cannot be finalized until concept art establishes the intended experience. Artists may be producing repeated revisions because creative priorities changed without being communicated clearly, and QA may be unable to validate a feature because requirements remain ambiguous. Asking any one of those people to work harder does not necessarily solve the problem because individual effort is not what created the dependency. Leadership can provide far more value by understanding how the pieces interact and helping remove the friction between them.
Consistently asking how you can help also provides leaders with information they may never receive through formal reporting structures. Production dashboards are useful, milestone reviews matter, and metrics can reveal important patterns, but none of them completely explain what it feels like to do the work inside the organization. A schedule can tell you that something is late without explaining that a developer has spent half their week attending meetings that contribute very little to the feature. A report may show repeated revisions without revealing that three stakeholders are providing contradictory creative direction. Conversations with the people doing the work often expose organizational problems long before those problems can be represented cleanly in a spreadsheet.
The question also requires humility, which I think remains one of the more underrated qualities in leadership. Humility does not mean lacking confidence in your judgement or being unwilling to make decisions when the organization needs them. It means accepting that a leadership title does not provide perfect visibility into every challenge faced by the people around you. No matter how experienced you become, there will always be aspects of another person’s work that you cannot fully understand without asking questions and listening carefully. Leaders become more effective when they stop interpreting that limitation as a weakness and instead build systems and relationships that give them access to the expertise distributed throughout the organization.
This mindset tends to create healthier conversations because employees feel that their expertise is respected rather than merely managed. Most people enjoy discussing their work with leaders who demonstrate genuine curiosity about how that work actually functions. They are more willing to explain why something is difficult when they believe the leader wants to understand rather than immediately contradict them with an answer. This does not mean leaders should accept every explanation without scrutiny or allow expertise to become an excuse for avoiding accountability. It means beginning with enough curiosity to understand the situation before deciding what leadership needs to do about it.
There is also a direct relationship between this behaviour and psychological safety. The term is sometimes discussed so abstractly that it can sound like another corporate initiative, but in practical terms it means people believe they can speak honestly about problems without facing unnecessary negative consequences for doing so. Teams with stronger psychological safety tend to raise concerns earlier, admit mistakes more readily, ask questions when they are uncertain, and challenge assumptions before those assumptions become expensive. A leader who sincerely and consistently asks how they can help contributes to that environment because the question normalizes the idea that encountering obstacles is part of complex work rather than something employees should conceal.
Of course, none of this happens because of five words alone. If a leader asks how they can help and then ignores every concern that is raised, people will quickly learn that the question has no practical meaning. If the leader interrupts the answer to provide a solution before understanding the problem, employees will become less interested in explaining what is actually happening. If support disappears whenever a project becomes difficult, the team will recognize that leadership’s willingness to help was conditional upon circumstances being comfortable. The question becomes powerful only when it represents a broader leadership philosophy in which helping people succeed is treated as part of the leader’s responsibility rather than an occasional act of generosity.
Actionable Steps
-
Ask “How can I help you?” during normal periods of production rather than reserving the question for moments when a project is already in trouble.
-
When someone answers, spend enough time understanding the situation before immediately offering your own solution.
-
Follow through on commitments created by these conversations so people learn that raising problems leads to meaningful support.
-
Look for recurring patterns in the answers you receive. When several people struggle with the same issue, the problem may be organizational rather than individual.
-
Make sure support and accountability remain connected. Helping someone overcome an obstacle should enable them to take responsibility, not remove responsibility from them.
Leadership as a Service Profession
As people move into more senior leadership positions, one of the biggest adjustments they face is recognizing that success is no longer measured primarily by their own output. Earlier in a career, the relationship between effort and recognition is often relatively straightforward. A programmer writes excellent code, an artist creates outstanding assets, a designer builds engaging systems, or a producer keeps a complicated feature moving successfully through development. Individual contribution is visible, and performance can often be connected directly to the quality and quantity of the work someone personally produces. Leadership changes that relationship because the value of the individual increasingly comes from what everyone around them becomes capable of accomplishing.
This transition can be difficult for first-time managers because the behaviours that previously earned recognition remain deeply ingrained. Someone who became a lead because they were an exceptional programmer may continue trying to prove their value by solving the team’s most difficult technical problems. A talented artist promoted into management may still want to personally review and correct every important asset, while a producer may continue making decisions that could now be delegated to people they are supposed to develop. These behaviours often come from good intentions because the leader wants to maintain quality and demonstrate that they remain useful. Unfortunately, they can also create bottlenecks and prevent the team from developing the independence leadership should be encouraging.
Over time, teams working under this kind of leader can become dependent on them for decisions they were perfectly capable of making themselves. Employees learn that difficult questions eventually travel upward, so there is less incentive to develop the confidence required to resolve them independently. Work slows because too many decisions flow through one person, and the leader becomes increasingly overwhelmed by responsibilities they should no longer personally own. The situation can even reinforce itself because the leader sees how many people need their involvement and interprets that dependency as evidence of their importance. In reality, an organization that cannot function effectively without constant intervention from one person has developed a leadership weakness rather than a leadership strength.
Viewing leadership as a service profession helps shift that perspective, although service should not be confused with making everyone happy. Leaders still have to make unpopular decisions, enforce standards, provide difficult feedback, manage performance, and occasionally tell people that something they want cannot happen. Serving a team means creating the conditions in which the organization can perform at its highest possible level, and those conditions sometimes require decisions people will not immediately enjoy. The difference is that authority is being exercised in service of the work and the people responsible for it rather than as a way for the leader to demonstrate control.
Service can therefore take many forms depending on what the team actually needs. It may involve removing an obstacle that nobody else has the authority to remove, providing clarity when competing priorities are creating confusion, or protecting developers from unnecessary interruptions so they can concentrate on meaningful work. At other times, service means coaching someone through a difficult challenge instead of taking the task away from them, or having an uncomfortable performance conversation because avoiding it would ultimately harm both the individual and the rest of the team. These actions can look very different from one another, but they share the same objective. They are attempts to use leadership authority and experience to improve the team’s ability to succeed.
One of the more interesting things I have noticed throughout my career is that some of the most respected leaders spend relatively little time talking about leadership itself. They spend their time understanding what their teams need, making thoughtful decisions, resolving conflicts before they become larger problems, and removing barriers that interfere with progress. Much of that work will never be visible outside the team because good leadership often prevents problems rather than receiving recognition for solving them after they become crises. Executives may never know how many conflicts were resolved before escalation, and players certainly never see the hundreds of small organizational decisions that allowed developers to concentrate on building the game. That invisibility is part of the responsibility rather than evidence that the work lacks value.
“How can I help you?” reflects this understanding because it reminds leaders that their role is not simply to direct work but to enable it. The question shifts attention away from proving the leader’s individual contribution and toward understanding what the organization requires from the position they occupy. Sometimes the answer will require the leader to act directly, and sometimes the best response will be to give someone else the room and authority to solve the problem themselves. Learning the difference is one of the most important skills a leader can develop. The ultimate measure is not how indispensable the leader appears, but whether their involvement leaves the team more capable of succeeding.
Actionable Steps
-
Regularly examine whether your daily involvement is increasing the team’s capability or creating greater dependence on you.
-
Look for decisions and responsibilities that can be delegated without sacrificing necessary oversight.
-
Treat coaching and mentoring as part of the leadership role rather than optional work to be done only when production becomes quiet.
-
Pay attention to the invisible work of leadership, including removing friction, clarifying priorities, resolving conflicts, and protecting focus.
-
Measure your success partly by the confidence and effectiveness developing around you, not simply by how many problems personally reach your desk.
Helping Does Not Mean Solving Every Problem
One of the easiest traps leaders can fall into after embracing a service-oriented approach to leadership is believing that they now need to personally solve every problem brought to them. On the surface, this can feel completely consistent with asking, “How can I help you?” If your responsibility is to support the people around you, providing the answer, removing the obstacle, or taking ownership of a difficult problem can appear to be the fastest and most generous response. Leaders who have significant experience are particularly susceptible to this because they may genuinely know how to solve the problem faster than the person asking for help. The difficulty is that solving today’s problem and helping someone become better at solving tomorrow’s problems are not always the same thing.
When leaders consistently become the answer to every question, they can unintentionally train their teams to stop looking for answers on their own. Developers begin escalating issues they are capable of resolving because experience has taught them that leadership will eventually make the decision anyway. Designers become hesitant to commit to creative choices without approval, producers rely on senior management to resolve conflicts that should be handled within their teams, and leads become reluctant to exercise authority because they know someone above them may eventually step in. The leader may feel extremely productive because problems continue disappearing from the project. Meanwhile, the organization is becoming less capable because fewer people are developing the judgement and confidence required to solve those problems independently.
This is one of the harder adjustments for new leaders because helping someone and doing their work for them can initially look remarkably similar. Both approaches may result in the immediate problem being resolved, and under production pressure the faster option can be extremely tempting. The difference becomes visible over time when the same types of problems repeatedly return to the leader because nobody else has developed the capability to handle them. Good leadership therefore requires understanding not simply what problem needs to be solved but what kind of support the person actually needs. Sometimes they genuinely need the leader to intervene, while at other times they need guidance, context, confidence, resources, or simply someone willing to help them think.
Imagine a junior designer struggling to balance a combat system. An experienced design leader could sit down, examine the numbers, identify the weaknesses, redesign the system, and probably reach a reasonable solution much faster than the junior designer can. The feature moves forward, the schedule looks healthier, and everyone can return to the rest of their work. Unfortunately, the designer has learned relatively little about how the problem was solved and may return with a similar problem several weeks later. The leader has improved the feature without necessarily improving the person responsible for designing it.
A different approach would involve sitting with the designer, discussing the goals of the system, reviewing the available information, and asking them to explain how they reached their current decisions. The leader can challenge assumptions, point out variables the designer may not have considered, and use their experience to help structure the problem without immediately providing the final answer. This approach will probably take longer than simply fixing the design, particularly when the leader already has a strong opinion about what should change. What it creates, however, is an opportunity for the designer to understand the reasoning process rather than merely inherit the result. The next time they encounter a similar balancing problem, they have a better chance of solving it without needing the same level of assistance.
This distinction becomes increasingly important as studios grow because leadership approaches that function with ten people often collapse at fifty, one hundred, or two hundred. Small teams can survive for a surprisingly long time with a few highly experienced people acting as the answer to almost everything. As the organization expands, those people inevitably become bottlenecks because they cannot personally resolve every design question, production challenge, technical decision, personnel issue, and stakeholder conflict. Even if they somehow found the time, continuing to centralize decisions would prevent the next generation of leaders from developing the experience required to make those decisions themselves. Scalability in leadership therefore depends partly on teaching people how to exercise judgement rather than simply giving them access to someone else’s judgement.
This does not mean leaders should become passive observers who respond to every request for help by asking another question. There are situations where direct intervention is clearly the correct response. A production crisis may require an immediate decision, a legal or security problem may need executive involvement, or an interpersonal conflict may have escalated beyond what the people involved can reasonably resolve themselves. Deadlines also matter, and there will be moments when there simply is not enough time to turn every challenge into a coaching exercise. The goal is not to avoid providing answers but to recognize when an answer is genuinely required and when providing one would unnecessarily remove an opportunity for someone else to develop.
One question I often find useful is whether my involvement will make the team stronger or simply make today’s task easier. There are certainly situations where making today’s task easier is exactly what leadership should do, particularly when risk or time makes experimentation irresponsible. However, if immediate efficiency wins every time, the organization gradually becomes dependent on a small number of experienced decision makers. Strong studios need to solve today’s problems while simultaneously increasing their ability to solve similar problems tomorrow. Asking “How can I help you?” should therefore lead to the support someone actually needs, not automatically to the leader taking the problem away from them.
Actionable Steps
-
Before providing an answer, consider whether the person genuinely needs a decision from you or needs help developing their own decision.
-
Use questions to understand someone’s reasoning before explaining how you would approach the problem.
-
Recognize when production pressure genuinely requires direct intervention rather than turning every situation into a coaching exercise.
-
Pay attention to problems that repeatedly return to leadership, since repetition may indicate that capability is not being developed elsewhere.
-
Evaluate whether your involvement leaves the individual or team better equipped to handle a similar situation in the future.
Removing Obstacles Instead of Becoming One
If there is one responsibility that consistently separates effective leaders from ineffective ones, it is the ability to identify and remove unnecessary obstacles. Every development team encounters difficulties that leadership cannot simply make disappear. Technical limitations, budget constraints, changing market conditions, unexpected bugs, production risks, and difficult creative decisions are all natural parts of making games. Experienced teams understand that some amount of friction comes with complex creative work. The more frustrating obstacles are often those created unintentionally by the organization itself because those problems consume time without creating meaningful value.
These obstacles can take many forms. They are meetings that consume hours every week without producing useful decisions, approval processes requiring several layers of sign-off for relatively minor changes, and conflicting priorities communicated by different stakeholders who have not aligned with one another. They can appear as decisions that remain unresolved because nobody understands who has authority to make them, or production processes that made sense years ago but continue to exist simply because nobody has questioned whether they are still necessary. None of these systems were necessarily created by incompetent people or with bad intentions. Organizational friction often develops gradually as individually reasonable decisions accumulate into processes that no longer make sense when viewed as a whole.
One of the mistakes leaders make in these situations is asking people to compensate for organizational inefficiency with additional effort. When schedules begin slipping, the instinctive response may be to push harder, ask for greater focus, increase oversight, or encourage teams to find ways to improve their velocity. Those responses can be appropriate when performance is genuinely the problem, but they become counterproductive when the organization itself is preventing people from working effectively. Asking someone to move faster while requiring them to navigate unnecessary bureaucracy does not demonstrate high standards. It simply transfers the cost of poor organizational design onto the people doing the work.
This is where asking “How can I help you?” can reveal problems leadership might otherwise misdiagnose. Someone struggling to complete work on time may not need time-management advice if their day is being fragmented by constant interruptions and unnecessary meetings. A producer whose schedule repeatedly slips may not have a planning problem if stakeholders continue introducing requirements without acknowledging their impact on the existing plan. Artists who appear overloaded may not need additional headcount if much of their workload comes from repeated revisions caused by unclear creative direction. Understanding the difference requires leaders to look beyond the visible symptom and investigate the system producing it.
I have seen organizations where individual approval steps were introduced for perfectly reasonable reasons, yet the combined process eventually became a significant barrier to getting anything done. One department wanted oversight because of financial risk, another wanted to ensure technical standards, another needed brand consistency, and leadership wanted visibility into important decisions. Each requirement could be defended individually, but together they created a process where relatively ordinary work waited days or weeks for approvals. The developers did not need another conversation about motivation or efficiency. They needed someone with enough organizational authority to examine the entire process and ask whether all of those controls were still providing value proportional to the friction they created.
This becomes particularly important because organizations normalize friction remarkably quickly. People learn which meetings they are expected to attend, which approvals take several days, which stakeholder needs to be consulted before a decision can move forward, and which cumbersome processes are simply considered part of working at the company. Eventually, they stop questioning those systems because working around them feels easier than attempting to change them. New employees sometimes notice these problems more quickly precisely because they have not yet learned to accept them as normal. Good leaders should try to preserve some of that curiosity even after they have spent years inside the organization.
Removing obstacles does not mean eliminating every process or treating structure as the enemy of creativity. Studios need appropriate controls around budgets, security, legal obligations, platform requirements, quality, personnel decisions, and countless other areas. Processes often exist because someone previously experienced a problem that the organization reasonably wants to prevent from happening again. The leadership challenge is determining whether the solution remains proportionate to the risk and whether it still functions effectively as the company changes. A process that protected a twenty-person studio may become unnecessarily restrictive at one hundred people, while a loose system that worked at twenty may become dangerously inadequate at the same scale.
Leaders should therefore remain curious about the systems surrounding their teams rather than assuming those systems are fixed. Every recurring complaint about unnecessary approvals, unclear responsibilities, redundant meetings, or conflicting priorities deserves at least enough investigation to understand whether the frustration reflects an individual preference or a genuine organizational problem. Not every complaint will justify change, and leaders should be comfortable explaining why some processes need to remain. However, when unnecessary friction can be removed without introducing greater risk elsewhere, doing so is one of the most practical ways leadership can improve both productivity and the everyday experience of the people doing the work.
Actionable Steps
-
Ask teams which recurring processes consume the most time without providing proportional value.
-
Review meetings periodically rather than allowing them to continue indefinitely simply because they already exist.
-
Examine approval chains to determine whether every participant still needs to be involved in every decision.
-
Look for systemic causes when multiple people experience the same performance or scheduling problem.
-
Treat unnecessary organizational friction as a leadership problem rather than expecting employees to continually compensate for it.
Supporting Teams Through Difficult Times
It is relatively easy to ask “How can I help you?” when a project is progressing smoothly, milestones are being achieved, and the company feels stable. The real test of that leadership philosophy comes when circumstances become difficult and the answers are no longer straightforward. Every studio eventually experiences periods of uncertainty. Funding discussions take longer than expected, milestones slip, publishers change priorities, market conditions deteriorate, projects are cancelled, strategies change, and organizations sometimes face restructuring or other decisions that affect people’s careers and livelihoods. Those moments reveal considerably more about a company’s leadership culture than the periods when everything is going according to plan.
One of the most important things leaders can provide during difficult periods is presence. When uncertainty increases, people naturally begin looking more closely at leadership because they are trying to understand what is happening around them. They pay attention not only to formal announcements but also to changes in behaviour, communication patterns, meeting attendance, and how available senior people appear to be. Leaders who become distant during these periods may believe they are avoiding premature communication or concentrating on solving the underlying problem. Employees often experience the same silence very differently because information gaps create space for assumptions, rumours, and fears that may be considerably worse than the reality.
Being present does not require pretending to have answers that do not yet exist. There are situations where leadership genuinely does not know whether funding will close, whether a publisher will approve the next milestone, whether a project will continue, or what an organizational change will ultimately look like. Attempting to project certainty in those situations can damage trust when reality later contradicts what employees were told. A more credible approach is to communicate clearly about what is known, what remains uncertain, and what process is being used to reach the decisions that have not yet been made. People may not enjoy the uncertainty, but they are usually better equipped to deal with uncertainty they understand than silence they are left to interpret themselves.
The question “How can I help you?” can become especially meaningful during these periods because the answer may change dramatically from person to person. Someone may need practical support because priorities have shifted and they no longer understand where to focus their time. A producer may need executive help resolving a dependency between teams, while another employee may be struggling with uncertainty about what organizational changes could mean for their role. Someone else may simply need the opportunity to express frustration before they are ready to discuss solutions. Leadership becomes more effective when it recognizes that support is not a standardized intervention that can be distributed identically to everyone.
This is also where leaders need to become comfortable with the idea that helping does not always mean fixing. Some situations cannot be fixed immediately, and pretending otherwise can lead to promises leadership cannot keep. A leader may not be able to guarantee that a project will survive, prevent a publisher from changing strategy, or create funding that does not currently exist. What they can do is listen, communicate honestly, provide whatever practical assistance is available, and avoid making people feel abandoned simply because the problem cannot be solved quickly. Sometimes the most responsible support is acknowledging the seriousness of a situation while remaining engaged in working through it.
I have learned over the years that leaders can underestimate how much value people place on simple availability during difficult periods. Employees do not always expect their leader to remove every challenge, particularly when they understand that the circumstances are larger than any individual person’s authority. They do, however, notice whether leadership continues showing up when conversations become uncomfortable. A leader who was highly visible during successful periods but disappears when the project struggles communicates something very different from one who remains accessible even when they cannot provide reassuring answers. Support becomes credible when people discover that it does not disappear the moment circumstances become difficult.
Honesty becomes particularly important because the desire to protect morale can tempt leaders to soften reality until communication becomes misleading. There is a difference between avoiding unnecessary panic and withholding information people reasonably need to understand their situation. Leaders should not speculate irresponsibly or share confidential information simply to appear transparent, but neither should they treat employees as though they are incapable of handling difficult news. Most experienced developers understand that games are risky, businesses face uncertainty, and not every project succeeds. What damages trust is often not the existence of a difficult situation but the feeling that leadership knew something important and deliberately allowed people to operate under a false understanding of reality.
Supporting teams through difficult times therefore requires the same combination of empathy and accountability that effective leadership requires during normal periods. People may need additional understanding, clearer communication, or flexibility as circumstances change, but the organization still has work that needs to be done and decisions that must be made. Good leaders do not respond to uncertainty by abandoning standards, nor do they pretend that people should operate as though nothing has changed. They acknowledge the reality of the situation while helping the team understand what remains within their control. That balance allows support to remain practical rather than becoming empty reassurance.
The leaders people remember most strongly are often those they experienced during the hardest moments of their careers. They remember who communicated honestly, who remained available, who treated people with dignity, and who continued trying to help even when there was no perfect solution available. They also remember the leaders who disappeared, avoided difficult conversations, or suddenly treated employees as problems once circumstances deteriorated. Asking “How can I help you?” during difficult periods is therefore about much more than finding an immediate solution. It demonstrates whether the service-oriented philosophy leadership expressed during easier times was a genuine belief or merely something that worked while the answers were comfortable.
Actionable Steps
-
Increase meaningful communication during periods of uncertainty rather than allowing leadership visibility to decrease.
-
Be clear about what is known, what remains unknown, and when people can reasonably expect additional information.
-
Avoid creating false certainty simply because reassuring people feels easier than acknowledging an unresolved situation.
-
Make yourself available for difficult conversations even when you cannot provide an immediate solution.
-
Recognize that practical support, honest communication, and simply listening can all be legitimate responses to the question “How can I help you?”
Helping Individuals Grow Instead of Simply Deliver
One of the easiest ways to distinguish between managing work and genuinely leading people is to look at what someone prioritizes over time. Managers are often measured by whether work gets completed, which naturally directs attention toward schedules, milestones, budgets, deadlines, and deliverables. There is nothing inherently wrong with that focus because every game studio needs people who make sure commitments are understood and projects continue moving forward. Production discipline matters, and leadership that ignores delivery in favour of development will eventually create a different set of problems for the team. The distinction is that leadership has to think beyond the immediate milestone and consider whether the people responsible for delivering today’s work are also becoming more capable of handling tomorrow’s challenges.
Every project eventually ends, even though production pressure can make the current one feel like the only thing that matters. Teams change, technologies evolve, studios reorganize, and people who work alongside us for years may eventually move to other departments, companies, industries, or opportunities. If a leader’s entire philosophy revolves around completing the next feature or reaching the next milestone, they may deliver a successful game while failing to develop the people responsible for building it. That may not create an immediate production problem, which makes it easy to overlook. The consequences tend to appear later when the organization needs new leads, senior specialists, mentors, or decision makers and discovers that nobody was given enough opportunity to prepare for those responsibilities.
One of the most rewarding aspects of leadership for me has always been watching people become more capable than they were when they first joined a team. A junior designer who once needed significant guidance can gradually develop the confidence to lead feature discussions and challenge assumptions constructively. A programmer who initially relied heavily on senior colleagues can become the person newer developers approach when they need help understanding a complicated system. An artist who once focused almost entirely on their own assets can begin thinking more broadly about pipelines, collaboration, and how their discipline interacts with the rest of production. Those changes rarely happen because someone simply spent enough time at the company. They happen because people were given opportunities, feedback, support, and enough room to exercise responsibilities slightly beyond what they already knew how to do.
This is another area where asking “How can I help you?” becomes more valuable when the question extends beyond immediate production. Early in someone’s career, the answer may involve overcoming obstacles preventing them from completing their current work. As they gain experience, the answer may become more complicated because they begin thinking about where they want their career to go next. Someone may want exposure to another discipline, an opportunity to lead a small feature, or experience presenting their work to senior stakeholders. Another person may want to become better at mentoring, public speaking, project planning, or people management because they see those skills becoming increasingly important to the kind of role they eventually want.
These conversations matter because career development and project needs will not always align perfectly. The studio may need someone to continue performing work they already do extremely well, while that individual may need new challenges if they are going to continue growing. This creates a legitimate tension for leaders because moving strong performers into unfamiliar responsibilities can introduce short-term risk. It may be faster to give the difficult task to the experienced person who has already completed it ten times rather than allowing someone else to learn. If that logic determines every assignment, however, the organization becomes efficient at repeating what it already knows while becoming increasingly poor at developing additional capability.
Game studios are particularly vulnerable to this because production creates a nearly endless reason to postpone development. There is always another sprint, milestone, submission, launch, patch, feature, or deadline that appears more urgent than a conversation about someone’s longer-term growth. Everyone can sincerely agree that career development is important while repeatedly moving it behind whatever production challenge happens to be immediate. Eventually, the organization begins struggling to fill leadership positions internally because potential leaders were never given opportunities to practice leadership. Senior specialists become permanent bottlenecks because knowledge remained concentrated around them, and strong employees begin looking elsewhere because they no longer believe their current studio can offer meaningful opportunities to grow.
Helping people develop is therefore not separate from building a stronger studio. It is one of the ways leaders increase the organization’s ability to survive changes in projects, teams, and business conditions. A person who has been coached to make increasingly complex decisions creates additional leadership capacity. A specialist encouraged to share knowledge reduces dependency on a single expert, while someone given opportunities to work across disciplines may eventually solve collaboration problems that previously required senior intervention. These benefits take time to emerge, which is why they are easy to sacrifice under short-term pressure. Strong leadership has to protect enough space for development precisely because immediate production will almost always provide a convincing reason not to.
One question I have tried to keep in mind throughout my career is not simply what someone needs to succeed today, but what they may need to succeed two or three years from now. Those can lead to very different conversations because the first question is usually about solving a problem while the second is about building capability. A person may need help completing a feature today but need opportunities to lead one tomorrow. They may need technical guidance now while eventually needing experience communicating strategy or mentoring others. Leaders who consistently consider both horizons create teams that become stronger across successive projects because the people inside them continue developing rather than simply becoming more efficient at performing the same responsibilities.
Actionable Steps
-
Discuss career development throughout the year rather than limiting those conversations to formal performance reviews.
-
Ask people what they want to become better at instead of assuming their desired career path based on their current strengths.
-
Look for opportunities that stretch someone beyond their existing responsibilities without placing them in situations where they have no reasonable support.
-
Include mentoring, knowledge transfer, and leadership development in production planning rather than treating them as activities that happen only when schedules are quiet.
-
Measure leadership success partly by how much additional capability exists within the team after a project has finished.
Building a Studio Culture Where Everyone Helps Each Other
One of the interesting things about leadership is that behaviour tends to spread through organizations more effectively than policy. Studios can write excellent documents describing collaboration, communication, trust, knowledge sharing, and teamwork, but those statements have limited influence when employees observe different behaviour every day. Culture is shaped far more strongly by what people repeatedly experience, particularly from those with authority. Employees watch what leaders reward, what they tolerate, how they behave under pressure, and how they treat people when something goes wrong. Those experiences teach people how the organization actually works regardless of what appears in an employee handbook or company values presentation.
If leaders consistently ask how they can help without expecting recognition or something in return, people begin to understand that supporting others is part of how the organization operates. When senior specialists openly share knowledge instead of protecting it as a source of personal importance, other people become more comfortable doing the same. When producers respond to problems by trying to understand and remove obstacles rather than immediately assigning blame, developers become more willing to raise risks before those risks become crises. None of these behaviours need to be presented as major cultural initiatives to have an effect. Their power comes from being repeated often enough that people understand what kind of behaviour is normal and valued.
The opposite spreads just as easily. Leaders who protect information teach other people that information creates power and should therefore be protected. Leaders who avoid accountability make it harder to demand accountability elsewhere because employees can see that expectations change according to seniority. If recognition consistently goes to individuals who promote their own achievements while collaborative work receives little attention, people eventually learn that visibility matters more than contribution. Culture develops from these repeated signals, which is why leaders cannot reasonably separate the culture they want from the behaviour they personally demonstrate.
This is one reason I am cautious whenever organizations attempt to solve cultural problems primarily through slogans, workshops, or new sets of values. Those tools can be useful for creating common language and clarifying expectations, but they cannot compensate for contradictory leadership behaviour. A company can tell employees that collaboration matters while rewarding managers who build territorial departments and compete for resources. It can promote psychological safety while punishing people who raise uncomfortable problems, or celebrate transparency while senior leaders routinely withhold information without explanation. Employees will believe the behaviour because that is what determines their actual experience inside the organization.
Asking “How can I help you?” contributes to culture because it normalizes support as an ordinary part of work rather than something employees receive only from their manager. Eventually, the most meaningful version of the question is the one leadership no longer needs to initiate. Designers begin helping artists understand why a particular workflow is creating problems, engineers spend time explaining technical constraints to producers, and senior developers mentor newer colleagues because sharing knowledge is understood as part of being a strong member of the team. Cross-disciplinary problems become easier to resolve because people are less likely to view helping another department as work that falls outside their responsibilities. The behaviour has moved beyond an interaction between leader and employee and become part of how colleagues relate to one another.
That kind of environment produces benefits far beyond making the studio feel friendlier. Communication improves because people are more comfortable asking questions before making assumptions. Knowledge spreads more effectively because specialists do not feel that their value depends on remaining the only person who understands something important. Departments collaborate more naturally because helping another team is understood as contributing to the same project rather than sacrificing your own performance for someone else’s benefit. Production risks can surface earlier because people expect colleagues to help solve problems rather than use those problems to assign blame.
Leaders still need to be careful that a culture of helping does not become a culture where boundaries disappear and the most generous people become overwhelmed. Collaboration should not mean that everyone is permanently available to everyone else or that employees are expected to sacrifice their own responsibilities whenever another person needs assistance. Teams need clear ownership, priorities, and reasonable expectations around where support should come from. The objective is not to create an organization where people constantly interrupt one another in the name of collaboration. It is to create one where asking for appropriate help feels normal and providing appropriate help is recognized as contributing to collective success.
Culture develops gradually through hundreds of interactions rather than a handful of dramatic leadership moments. Every time a leader demonstrates genuine curiosity, follows through on an offer of support, coaches instead of immediately taking control, removes an unnecessary obstacle, or helps someone through a difficult situation, they provide another example of how people are expected to treat one another. Those examples accumulate until the behaviour becomes less dependent on individual leaders and more embedded in the organization itself. At that point, “How can I help you?” has accomplished something considerably larger than improving a single leadership conversation. It has contributed to a studio where helping people succeed is understood as part of everyone’s responsibility.
Actionable Steps
-
Model the collaborative behaviour you want from the studio rather than relying primarily on policies or values statements to create it.
-
Recognize people who share knowledge, mentor colleagues, and help other teams succeed rather than rewarding only highly visible individual accomplishments.
-
Create practical opportunities for mentoring, knowledge sharing, and cross-disciplinary collaboration.
-
Make sure a culture of helping includes reasonable boundaries so collaborative employees do not become overloaded.
-
Regularly examine whether incentives, processes, and leadership behaviour reinforce cooperation or unintentionally encourage competition between individuals and teams.
Final Thoughts
Leadership is often described through the language of authority because authority is one of its most visible characteristics. We talk about decision-making, accountability, strategic direction, organizational structure, performance management, budgets, and executive oversight because leaders are responsible for all of those things. As people become more senior, the consequences of their decisions also become larger because more people depend upon the environment those decisions create. A producer influences the daily experience of a development team, a department lead shapes how an entire discipline collaborates and develops, and a studio head can influence the direction, culture, stability, and opportunities of everyone within the company. Leadership therefore deserves to be taken seriously precisely because the authority attached to it affects far more than the person holding the title.
What is discussed less frequently is that the same authority creates a responsibility to serve the organization and the people responsible for making it successful. The further someone progresses into leadership, the less their value can be measured exclusively through their personal output. A studio head cannot create every asset, write every line of code, design every feature, manage every schedule, resolve every conflict, and maintain every external relationship. Their impact increasingly comes from the quality of the environment they create and the decisions that allow other people to perform effectively within it. Leadership becomes an exercise in multiplying capability rather than demonstrating individual capability.
That multiplication rarely happens because someone delivers an inspirational speech or introduces another elaborate management framework. It happens through the accumulation of ordinary decisions about how people are treated and how work is enabled. Leaders create capability when they take time to understand a problem before assuming they know the answer, remove unnecessary obstacles instead of asking people to continually work around them, and coach employees through challenges they are capable of learning to solve. They create it when they invest in someone’s development even though doing so may be less efficient than giving the work to the person who already knows how to complete it. They reinforce it whenever people discover that leadership genuinely wants them to succeed rather than merely wants them to produce.
This is why I continue to find “How can I help you?” such a useful question despite its simplicity. Asking it sincerely requires humility because the leader must accept that they may not understand the problem as well as the person experiencing it. Responding to the answer requires judgement because helping may mean removing an obstacle, providing context, making a decision, finding resources, coaching someone through the problem, or deliberately allowing them enough space to solve it themselves. Following through requires accountability from the leader because an offer of support that repeatedly produces no action eventually becomes meaningless. The value of the question therefore comes from the leadership philosophy behind it rather than from the words themselves.
It is equally important to recognize that helping someone does not remove their responsibility for their own performance. I have never believed that empathetic leadership requires lowering standards or protecting people from every consequence of their decisions. In many situations, the most useful help a leader can provide is honest feedback, greater clarity, or a difficult conversation about something that needs to change. Service-oriented leadership is not passive leadership, and it should not create an environment where accountability becomes optional. The objective is to create conditions where people have a reasonable opportunity to succeed and understand that leadership will support them in doing so.
The same principle applies when circumstances become difficult. A leader may not be able to save every project, resolve every financial problem, prevent every restructuring, or provide certainty when the organization itself does not yet know what will happen. What they can control is whether they remain present, communicate honestly, treat people with dignity, and continue providing whatever support is realistically available. Employees rarely expect leaders to possess supernatural control over circumstances, but they do remember whether those leaders remained engaged when the answers became uncomfortable. The credibility of supportive leadership is built as much during periods of uncertainty as it is during periods of success.
Looking back across my own career, the leaders who made the strongest impression on me were not necessarily the people with the most impressive titles or the individuals who seemed to have an answer for everything. They were the people who invested in my growth, challenged me when I needed to become better, listened when I needed another perspective, and removed obstacles that allowed me to concentrate on doing my best work. Their support did not make me less accountable for my responsibilities. If anything, it made me more willing to take responsibility because I knew asking for help when I genuinely needed it would not automatically be interpreted as failure.
That experience has shaped how I think about the responsibility leaders have toward the people around them. Our job is not to make ourselves indispensable by becoming the answer to every question, because an organization permanently dependent on one person’s judgement has not developed enough capability. It is not to protect people from every difficult situation, because challenge and failure are important parts of professional growth. Leadership should instead create enough clarity, support, trust, and opportunity for people to develop the confidence required to handle increasingly complicated problems themselves. Over time, the strongest evidence of successful leadership may be that fewer problems require the leader’s direct involvement because the people around them have become more capable of solving those problems together.
There are countless leadership frameworks, management books, organizational theories, and methodologies available to anyone interested in becoming a better leader, and many of them contain genuinely valuable ideas. I have learned from plenty of them throughout my own career, and I expect I will continue doing so because leadership is something none of us ever completely finishes learning. However, frameworks only become useful when they improve the experience and effectiveness of the real people we are responsible for leading. A complicated philosophy that never changes how we listen, communicate, support, challenge, or develop people has limited practical value no matter how sophisticated it sounds.
For that reason, I still return to the simplicity of asking the people around me how I can help them. Sometimes the answer reveals an obstacle I can remove immediately, while other times it exposes a larger organizational problem that will take considerably more work to address. Sometimes the right response is advice, sometimes it is a decision, and sometimes it is simply listening long enough to understand what the person actually needs. The important part is approaching leadership with enough humility to ask the question sincerely and enough commitment to take the answer seriously. Over the course of a career, that habit can influence not only the problems a leader helps solve but the confidence, capability, and culture that develop around them.
Thank you for reading this article to the end. I hope it has been informative and helpful. If you’d like to learn more about the topics we covered, I invite you to check out my podcast and my YouTube channel, where I delve into these subjects in more depth.
Additionally, I would love to stay in touch and keep you updated on all the latest developments and insights in the world of leadership. That’s why I encourage you to sign up for my newsletter. Not only will you receive regular updates, but as a thank you for joining, I will also send you my free eBook, “5 Heroic Leadership Skills.” This eBook is packed with practical tips and strategies that will help you take your leadership skills to the next level.
So don’t wait! Sign up for my newsletter today and start your journey towards becoming a more effective and inspiring leader. I can’t wait to hear from you.
🎮✨ Join the Press Start Leadership Discord! 🌟💬
Ready to level up your leadership game? 🚀 Join our exclusive Discord channel where we dive into leadership, mindfulness, and all things awesome in the video game industry! 🎯✨ Connect with fellow enthusiasts, share insights, and join our Accountability Club to stay on track and crush your goals together! 💪🔥
Click here to join the adventure: Press Start Leadership Discord
🎮✨Work With Me!🌟🎮
If you’re on the quest to elevate your team’s leadership, production, or game design capabilities, I’m here to assist! Leveraging extensive experience and a strategic approach, I offer personalized audits, bespoke workshops, and leadership retreat facilitation to drive your team toward excellence. My commitment is to provide efficient, reliable, and proven support, ensuring you have the tools and insights needed to thrive. Ready to unlock your team’s full potential and achieve unparalleled success? Don’t hesitate—Press Start on your journey to transformation today! Feel free to reach out directly to discuss how we can tailor a solution to meet your unique needs and goals. Let’s connect and take your team’s performance to the next level!
🔗 www.pressstartleadership.com
📧 contact@pressstartleadership.com
🎮✨ Discover the Mysteries of Play On Words Studios! 🌟🚀
I’m excited to share the incredible projects Play On Words Studios, my indie studio, has been working on! 🎨🕹️ Dive into our creative world and see the games we’re crafting just for you.
- Check out our Studio: Play On Words Studios
- Pre-Order Shadow City Mysteries: The Roleplaying Game: Pre-Order Here!
- Watch Shadow City Mysteries: House of Skye: Watch Here!
- Wishlist Shadow City Mysteries: Case Files – Rise of the Rat King: Wishlist Now!
- Wishlist Shadow City Mysteries: A Clockwork Noir on Steam: Wishlist Now!
- Join Our Discord: Play On Words Studios Discord
Join us on this amazing journey and be a part of something truly special! 🌠🎉
