Hiring & Onboarding – [Notes from 2023 Roundtables 3/3]

Hey folks!

Anoter leadership roundtable organized through Game Dev MTL discussed hiring and onboarding. Here are the notes that were shared with the rest of the roundtable (shared publicly with their permission).

Note that some information here may be missing the context of the in-person conversation, but I still think they can be helpful.

Roundtable 1/3: Designing & Maintaining Company Culture
Roundtable 2/3: Feedback, Reviews & 1 on 1s
Roundtable 3/3: Hiring and Onboarding

Sorting Through Applicants

Different folks at the roundtable had different ways of sorting through applicants.

There were a number of tips that came up during the roundtable, which I’ll share below:

There were a couple of additional points that came up that were worth discussing:

  • ‘even if not hired, applicants evolve over many years and can be a good fit in the future’ — be sure to respond to applicants and keep contact with them in the future. Also, an important note (that we’ll get to later in this email) about not keeping their information around for over a year because of the new Bill 25.
  • ‘leads might try to reject some applicants if they’re worried about their own position’ — a couple of folks brought this up, where they’ve had people dismiss what would otherwise be good applications because of their concern for their position (consciously or not!). It’s important then, as mentioned above, to make it very clear what the criteria is and make sure that enough people are reviewing applications to make sure that this gets caught if it happens.

Lastly, where do you post your jobs?

Added note—in another roundtable in 2024 someone talked about places to post jobs to seek out more diversity (especially useful in Quebec or Canada):

Interviews

Everyone in the group did interviews or interview-like conversations. Usually there was a vibe check or a phone call with filtering questions, followed by a formal interview with the hiring manager and the leads of the department or the people who would be responsible for managing the employee.

Some notes about the process and especially about tests. Note that this was a small group and doesn’t reflect the whole industry, even in Montreal—some folks in the industry are strongly against testing during the hiring process (but those people weren’t vocal in these roundtables).

Hiring Logistics

We then moved to any sorts of tips and tricks people might have regarding the actual logistics of hiring—contracts, hardware, etc.

We talked about the importance of being well organized with a list of:

  • all of the steps that take place before the person is hired (for the hiring manager)
  • what we need from the new employee before they start: void cheque, information for payroll, required hardware, etc.
  • employee guide which includes policies, values, processes, etc.

This content started bleeding into onboarding pretty quickly so we jumped right over to that.

Onboarding

Onboarding was the bulk of the discussion, since onboarding is so so so important. We had lots of notes that I tried to organize into categories, so hopefully they make sense to you too.

Lastly, we got into discussion about legal requirements around hiring and HR processes. There was a lot to talk about here, but there was one point about what employees are legally required to sign. See the resources section piece about Law 25. As one participant said, “mieux prévenir que guérir!” (better to prevent than to healtry to fix the problem after).

And one big sticky note which summarized a lot about issues folks had in the past about not having enough processes:

Other Miscellaneous Notes

Because you can’t always categorize everything! Note some of the legal points relate to Quebec, Canada specifically.

Resources

  • Quebec Law 25 obligations
  • Extremely comprehensive list of policies required by a company in Quebec — I’m not a lawyer but I believe that several of these are covered by default by Quebec’s labour laws, so even if you don’t have a policy around some things the default is what’s written in the Quebec code. But, I’m not a lawyer! This isn’t legal advice.
  • Collage HR — tool which helps with gathering and sorting job applications, team members sharing and commenting on them, sending out responses, and can also handle stuff like onboarding, reviews, etc. etc.
  • BitWarden — password manager and secure file sharing (also LastPass but they’re more expensive and there have been more breaches)
  • http://WorkWithIndies.com — job posting for Indie jobs
  • I was asked to share Clever Endeavour’s “How to Interact With Us” questions — each employee fills this out and every other employee reads theirs to know more about them and how to work with them:
    • Conditions I like to work in
    • The times / hours I like to work
    • The best ways to communicate with me
    • The ways I like to receive feedback
    • Things I need
    • Things I struggle with
    • Things I love
    • Other things to know about me

Hope this was useful to you, I definitely learned a lot from the sessions!


Rich

Feedback, Reviews & 1:1s – [Notes from 2023 Roundtables 2/3]

Hi friends!

The next set of leadership roundtables organized through Game Dev MTL discussed feedback, reviews and 1 on 1 meetings. Here are the notes that were shared with the rest of the roundtable (shared publicly with their permission).

Note that some information here may be missing the context of the in-person conversation, but I still think they can be helpful.

Roundtable 1/3: Designing & Maintaining Company Culture
Roundtable 2/3: Feedback, Reviews & 1 on 1s
Roundtable 3/3: Hiring and Onboarding

Feedback

We started off talking about why we give feedback in the first place, and some interesting points came up:

Also, this very important point:

The way people like to give and receive feedback, its frequency, etc. is all very cultural. This is important to keep in mind especially working with employees or partners in different countries, speaking different languages, etc.

Then we got to how we give feedback, and other things related to how feedback can be received. It’s important to note that there’s a difference between small pieces of feedback, which are small adjustments to modify behaviour, and important “we need to talk” issues.

A couple of the sticky notes above needed some elaboration:

⭐ – “need to be explicit about expectations” – this came up in the context of giving someone feedback without it being clear what the expectations were in the first place. If you tell an artist that you want a first pass done of a character, and they present something, and your feedback is that it’s not polished enough or doesn’t look representative of the art in the final game, then this kills your feedback and credibility to give feedback! They’ll learn from this that you’ll criticize their work regardless of what they do, since you’re not being clear about what you want in the first place. Also, getting negative feedback on something that was missing clarity can cause confidence issues (especially in juniors).

⭐⭐ – “feedback for validation → can cause issues” – if folks need positive feedback to validate everything they do, this can be a problem because:

  1. they’re less likely to do something imaginative and out-of-the-box because they depend on that validation and it’s less likely to happen if there’s negative feedback, which will happen if they take creative risks with their work
  2. it will scare us (managers) into not ever wanting to give them negative feedback because we know it’s tied to their personality / self-esteem
  3. this is generally a bigger problem which could mean the person isn’t receiving any positive validation from their social / familial ecosystem, and is dependent on you (the manager) in an unprofessional way (i.e. more as a parent/child relationship and not a boss/employee one)

🔎 – The feedback model from Manager Tools (linked in the resources below) goes something like this. “When you _, here’s what happens. How can you do this differently?” This applies to things like folks showing up late to meetings, work product being sub-par, folks not paying attention in meetings, etc.

1:1 Meetings

We started defining one-on-one meetings, but it’s clear (throughout all of management in all fields of work) that 1:1s are different for different people. Some notes came up:

Some folks at the roundtable had set questions which they asked every time, others had a more free-form meeting. Some question ideas include:

  • any problems?
  • any positive highlights?
  • how is the sprint going?
  • any roadblocks?
  • how is X (task, project) going working with Y (person)?

One of the participants shared their review structure which ties into 1:1s, and which many others found inspiring due to the fact that it tied 1:1s back to evaluations and back to company culture:

Performance Reviews

There were a number of different points raised about performance reviews, including their frequency (most did annual, one person did every 6 months), how people do self-evaluation, etc.:

We talked about 360 reviews, where some number of people who work with the employee review them, and that data is often used to help create annual reviews.

Other Misc Notes

A lot of stuff came up in the chat! Here are some sticky notes:

Resources & Future Questions

And a bonus question which we didn’t have time to dig into enough: “how do you give feedback to someone who is simply working too slowly?” We discussed it a bit, and there were questions around workload, how well they’re being managed, etc… but we didn’t reach a solution!

Hope this was useful to you, I definitely learned a lot from the sessions!


Rich

Designing & Maintaining Company Culture – [Notes from 2023 Roundtables 1/3]

Hey y’all! I organized and led a series of leadership roundtables through Game Dev MTL, and wanted to share the notes here that were shared with the rest of the roundtable (with their permission).

This is part of a series of posts from the various roundtables, and the information on these sticky notes of course are missing the context of the in-person conversation. But I think they can still be very helpful!

Roundtable 1/3: Designing & Maintaining Company Culture
Roundtable 2/3: Feedback, Reviews & 1 on 1s
Roundtable 3/3: Hiring and Onboarding

Defining Culture

The roundtable was introduced and someone brought up the idea that we should probably define culture before we start talking about our biggest successes and biggest mistakes in desigining and maintaining a company culture.

Folks put forward some different ideas that came up when we talk about what culture is and means:

Some folks brought up other, less straightforward ideas around defining culture:

Successes & Mistakes

Then, everyone talked about their greatest success in this regard, and their biggest mistake followed by what they learned from that.

Some of the things people pointed to as biggest successes were either process-related, culture design related, or positive effects of what they felt was a good company culture:

Some of the biggest mistakes people made and the lessons they learned are below. For almost all of the lessons, most of the room nodded their heads in agreement:

Open Discussion

We then moved to open discussion and bounced around a variety of topics. I jotted down some notes during the roundtable and added some more context to them while creating these notes.

  • Trust is huge for culture. I’ll borrow from Carolina Mastretta from Original Fire Games: “Trust is an emergent part of culture in a team, an ebb and flow that shifts as teams and individual members tackle new challenges, work with new people and face changes, wins and failures. With principles & practices, it can be built, sustained and nourished!” (check out her micro-talk from GDC 2023 if you have access to the Vault)
  • It’s important to recognize that folks who are not from the same country, background, level of professional experience or language may have very different base cultural assumptions around communication or professional conduct. These implicit, undefined norms will always exist but it’s important to take care to be aware of them and make them explicit.
    • Consider the language you use, inclusive language includes awareness of people who are speaking in their second language, from different cultures, etc.
    • Consider how much of your culture is assumed (which falls prey to these issues of cultural norm) versus how much of the culture is explicitly defined.
  • Meeting culture is a thing! Different companies have different ways of handling agendas, pre-sent materials, open discussion, going off-topic in meetings, timeboxing meetings, etc. This can be exacerbated when working across cultures and native languages.
  • Different countries, industries, and locations (i.e. the Montreal office and the Shanghai office) often have different company culture expectations.
  • If a company actually lives according to its values, then it should be able to check its major and minor decisions against those agreed upon values. For example, whether or not to accept working on a particular project might be informed by the team’s values.
  • It’s important to keep team values on the forefront. Most folks agreed that most values and mission documents are created and then stored somewhere, without employees looking at them or even knowing that they are explicitly. People have different strategies for awareness around these values, for example one person said they would randomly throw out a cultural value in morning standup and this got conversation started, sometimes around that value. This got people thinking and talking about company values in a more free-flowing way.
  • Culture is important for retention and attracting talent, as a way of differentiating your team from other teams / organizations. This is especially important given that many of us compete with companies like Epic who can pay massive salaries compared to most smaller or mid-sized studios.
  • Rules around communication are part of company culture.
  • Sometimes someone on the team can start to stray far from the culture / rules of the studio, and this often results in the person leaving or needing to be let go.
  • While a team’s culture will change with every new addition to the team, it’s also important not to let a new person bulldoze the culture and bend it to their will. There’s a give and take element where the new addition needs to be willing to learn and adapt, but also needs the space to be themselves and bring their experience in to help shape the team culture.
  • There needs to be a balance of how broad values are versus how directly actionable they are. Broad values can be vague and easy to either forget about or misinterpret, but values that are too specific might be restrictive or easy to dismiss as being not applicable to the current situation.
  • Sub-teams within a larger organization will interpret values / culture differently, hence why the balance of broad vs specific needs to be kept in mind.
  • People sometimes will stay in a company without fitting the culture because the other things make it worthwhile, for example pay, a 4-day work week, etc. This is known as the “golden cage” problem. This can be extremely detrimental to company culture because people are checked out but still influencing the culture without buying into or believing in it.
  • The new generation (Gen Z ish) has different values, and this can be a sore spot for managing culture. We talked a bit about the positive and negative aspects of this culture “clash”, and what we (most of the folks in the workshop were 30+) can learn from the younger generation.
  • Where does “hard work” fit into culture? It feels sometimes like this can’t be spoken about in a workplace culture because it goes directly against “people first” approaches. This is difficult to manage!
    • Creating estimates together and tracking sprints closely helps with the “hard work” being rewarded, one person said in response
  • Transparency has impact on culture—financial transparency, the HR process, comapny goals, etc. The default assumption is often that more transparent is better, but some folks mentioned how employees asked for transparency but then weren’t prepared to deal with the feelings that came up when they received that information. This isn’t to say not to be transparent with any of the things above, simply that there is an effect of being either more or less transparent that needs to be considered.

Further Thinking Required

A lot of questions came up during the roundtable, and we could have talked for another 5 hours. So I’ll leave you with some questions to reflect on:

  • If values are not sufficient to define the whole company culture, then what else is required?
  • How does your company culture show up in your day-to-day work? Meetings, reviews, town hall meetings, communication between team members, etc.
  • How do you integrate young people / the new generation into your culture, or how is your culture changing to incorporate the younger generation and their value set?
  • How much do you transform employees to fit your culture? What is too much (restricting their ability to positively affect your culture) and what is too little (letting them keep the exact same culture from their last workplace and transforming your culture)?
  • When do you start talking about company culture to new employees?

Hope this was useful to you, I definitely learned a lot from the sessions!


Rich