When we’re working on a new game, it’s very common to spot a lot of problems and point them out when we’re talking with our team. Having an analytical mindset is normal, especially if you’re in a role like a game designer or gameplay developer. You are, by default, forced to analyze everything very specifically, and this can lead to your analysis being extremely detailed.
The impulse can be to immediately flag these issues, especially nowadays on a Slack channel for instance. They are designed to make you talk. You see that a feature doesn’t work and you mention it because you want to make it known. The issue with this is that, especially when you are in a more senior position, it can lead to confusion.
Imagine you are on a boat with others, and you are all rowing towards a specific direction. Suddenly you notice a leak in the boat, and you stop rowing and shout, “Hey guys! The boat is leaking!” Everybody will stop, right? And someone will fix the leak before continuing.
What if, instead, you continue to work and offer a solution? For example, “Joe, you can fix the leak while we all continue to work,” or “Guys, continue to row! I need to fix this using this plug!”
This shows a different problem-solving skill, one that I had to learn the hard way. Don’t just point at a problem without proposing some solution. Be a problem solver, and your team will appreciate that.