Signs of anxiety in the workplace - or how a product manager’s job is managing both your own and your colleagues’ stress

Ärevuse märgid töökeskkonnas

I recently read Kathleen Smith’s book Everything Isn’t Terrible and started thinking that, by her definition, there really is a lot of anxiety in working life. Maybe even more than I’d realised before. A workplace is a complex system of colleagues and emotions. People constantly act and react in certain patterns while trying to cope with stress. Some amplify their own and others’ stress with their behaviour, others know how to defuse it.

Smith describes four patterns of how anxiety shows up in our everyday lives, including at work. Overworking as a symptom of anxiety, for example, surprised me and also didn’t, given how often work culture glorifies it. Truth be told, I glorified it too - until I burned out.

Anxiety as procrastination or distancing

Smith says that one sign of anxiety at work can be distancing - physical or emotional. For example, when a difficult technical problem needs solving, it can get passed from hand to hand like a hot potato, with nobody wanting to own it. Instead of solving it straight away, people either stay away from it or take on the role of helper rather than owner. Meanwhile the development team is confused and doesn’t know which direction to go. Another possible hint of distancing is when a colleague no longer wants to come to the office at all.

Anxiety as conflict

This one is logical. We’ve probably all experienced that the more tense the situation, and the longer it lasts, the shorter the fuse. Anxiety can also show up as constant arguing and dissatisfaction with colleagues. Under work pressure it’s easy to see others’ mistakes and start looking for someone to blame, especially when a project is late or the quality doesn’t meet expectations. Software development is an especially slippery slope, because iteration means deadlines sometimes do slip. Colleagues outside the product and technology departments find that hard to understand, especially when there are other tensions in the company. Instead of focusing on finding a solution, all the time can go into figuring out who made the wrong decision or whose work fell short. And that only deepens the anxiety.

Anxiety as overworking or underworking

And now my favourite - overworking. It’s practically a product manager’s sport. When anxiety grows, you feel you have to control everything yourself to make sure things are going right. This can lead to part of the team taking on too much responsibility (overworking) while others hand over their tasks and pull back (underworking). For example, a product manager may feel the need to review code, step into marketing plans and even handle customer communication, because otherwise things just won’t work. As a result, key people get overloaded and the team’s overall effectiveness drops.

Overworking is especially common among product managers who feel that all the responsibility rests on their shoulders and that they have to watch every last detail themselves. It can lead to burnout, and at the same time it encourages other team members to take less responsibility, hoping the product manager will sort everything out.

Anxiety as triangulation

Triangles form when two people are in conflict and bring a third party into the situation to relieve the anxiety. In product management this can mean a team member doesn’t talk about their problem directly with the product manager, but involves someone from outside the team. For example, a developer might go to a manager or colleague to criticise a decision, leaving the product manager who made it out of the conversation. Even worse if that colleague or manager then comes to “help” by taking sides. Although talking about a problem with someone else can feel like a solution at first, it usually leads to even more confusion and growing anxiety within the team.

Triangulation spreads the responsibility for solving the problem and can lead to communication problems, where different parties end up with different versions of what happened.

The solution - take time to be an astronaut

Besides the usual advice, like creating an environment where team members can discuss concerns directly, keeping communication open, dealing with problems head on and defining clear roles to help the team find balance, Smith suggests one simple technique - take the astronaut’s view, which means stepping back and looking at the situation more broadly.

For example, as a product manager you’re constantly surrounded by problems - some feature doesn’t work as it should, the design still needs work and the marketing team is waiting for faster answers. They all seem critical and in need of quick intervention. In the middle of all that, it’s easy to end up desperately trying to keep everything under control at once. In the end you’re overloaded and notice the project is dragging, because small issues and “helping” others have eaten all your time.

That’s where Smith suggests the astronaut’s view. Instead of reacting immediately to every small worry, consciously step back and look at the bigger picture. Think about the end goal of the project and whether you really are the right person to do these tasks. It may turn out that many things don’t need your direct involvement at all, and the team can solve them on their own. Regularly assessing the bigger picture like this and keeping the astronaut’s view helps keep anxiety under control and keeps the focus on the right course - the product’s long-term success and holding its direction.

Want to know more?

Follow me on LinkedIn or get in touch!