A game producer’s guide to setting up a risk register to track your fears.

Stop staying awake at night worrying!! Create a risk register to help track all your game development fears. Game development is very stressful and there are a lot of different things that can go wrong. Those things might mean your game will suck, development takes longer than expected, team members quit, and more. In the worst case if you don’t predict risks and take steps to address them, your game might not ship at all! Want more reasons why should you create a risk register? Having one will help you stop unconstructive worrying, make sure you remember and predict upcoming events, come up with plans that you can use when you’ll be super stressed, improve game quality, reduce development chaos, figure out what you can do to reduce the impact and probability of the risk, and so much more. What makes a good risk and description? One that isn’t too generic and that will help you understand why this is a problem. That way you are focusing your worries rather than being generally stressed without direction. Risks that you can’t control (like someone else shipping a game like yours) might not seem like good risks, but I’ll talk about why you should still track them and what you can do. I’ll go deep into exactly what I track in my risk registers. Many game companies and publishers have their own ways of showing and tracking risks. I’ll use an example from a hypothetical game to help understand what is being tracked. For each risk I track: a good description; numbers for impact, probability, and total risk; categories; trigger conditions (what to look for so you know the risk is happening); mitigation plans (what to do before a fire breaks out); contingency plans (what to do if the fire has broken out); alert status (how panicked should we be); and status history. Then I’ll discuss how frequently to monitor your risk register and use it. As well as when to engage mitigation and contingency plans. I’ll finish with some summary tips. One of those is that you shouldn’t create a risk register if you’re not going to use it. Instead you should just discuss your fears and worries with your team. Resources: [Example Risk Register in Notion](https://www.notion.so/174a82440e1680a9abc8fbc92d4415ad?pvs=21) Have a question for an expert game producer? Ask me your question here: https://jennsand.com/askjenn/ Text version: https://jennsand.com/advice/risk-register/ Video version: https://youtu.be/5k4aawBntsg Jenn’s Generally Good Game Production Advice: A game producer’s guide to setting up a risk register to track your fears. 00:00 Introduction 00:55 Question & Why create a risk register? 02:21 What makes a good and bad risk? 04:41 The details of all the properties that make up the risk register 08:44 How to monitor your risks 11:00 When should you engage mitigation and contingency plans? 11:40 Summary tips about risk registers 12:46 Conclusion Jenn’s Generally Good Game Production Advice is an advice column for our modern ages and for game developers everywhere. Topics covered will help you ship your game on time, on budget, with a happy team no matter whether you are a producer or someone else on the game team. Find out more about how to hire me: [jennsand.com](https://jennsand.com/)