← Back to blogs

How one person changed the way I looked at management

leadershipmanagementqacareer

If you had asked me twelve years ago, when I was working as a full stack developer, if management was something I wanted to do I probably would have said no.

At that time, I was focused on building things. I enjoyed solving technical problems, writing code, figuring out why something was broken and finding better ways to make things work.

Management felt like a completely different world.

  • More meetings.
  • Difficult conversations.
  • Feedback sessions.
  • More coordination and alignment.
  • Discussions about budgets, planning and priorities.

A lot of it sounded more administrative than technical and I also had the impression that managers were usually extraverted people who enjoyed being in front of groups, talking all day and getting energy from constant interaction with others. That was not really how I saw myself.

Because of this, I had never really spent much time thinking about management as a possible career direction. I expected myself to grow into an architect or development lead at some point.

However, after having been offered the opportunity by the company I worked for to take on more responsibility, I eventually became responsible for QA teams.

Initial approach

I approached management in exactly the same way I approached most things in life and at work: (first) learn as much as possible, understand what good looks like and improve over time. This meant that some lessons were learned quickly and smoothly, but others were unfortunately learned the hard way.

One of the biggest changes in my way of thinking came from realising that managing people is not about applying the same approach to everyone.

When I first started managing people, treating others how I would want to be treated myself seemed like the obvious approach:

  • Be fair.
  • Be transparent.
  • Give direct feedback when needed and focus mostly on points that can be improved.
  • Give people a lot of freedom and trust them to solve problems.
  • Support when they ask for help and shield them from outside interruptions and push back.
  • Only ever focus on output, never micromanage.

Those things are still important, but the part I underestimated was that people need completely different things to be successful.

Some people need a bit of confidence and encouragement, while others respond better to a challenge. Some prefer clear structure and regular guidance, while others do their best work when they have the freedom to explore ideas and work things out for themselves. A good manager needs to understand the person in front of them and not just apply the same approach to everyone.

One person changed my style

One person in particular changed how I looked at this. They were, and still are today, one of the best QA I have ever managed. They were shy and introverted and whenever they talked about their own work, they would often point out what they could have done better before anyone else had the chance to say anything. They were extremely hard on themselves. Over time, that started affecting how others viewed their work as well. When someone repeatedly questions their own abilities, people around them can start picking up on that, even when the actual quality of their work says something different.

The interesting part was that when looking at their output, as well as my conversations with them led to me having a completely different image and opinion of them than their own.

In our one-to-ones, I saw someone who asked thoughtful questions, noticed details other people missed and carefully considered decisions before acting. They had strong technical skills and a great understanding of quality and people. The main thing holding them back was confidence in their own abilities.

We worked on that over time through regular conversations, feedback, pairing sessions, and creating opportunities where they could step outside their comfort zone. With their permission, I encouraged them to take ownership of situations where they had previously stayed in the background.

They obviously had to do the difficult part themselves though:

  • They had to speak up when something mattered.
  • They had to trust their own judgement.
  • They had to recognise that their ideas were valuable.
  • They had to leave their comfort zone.

Those changes came from their own efforts. My role was only to create an environment where they felt safe enough to take those steps and to help them see strengths that they were often overlooking.

Slowly, things started changing. They became more comfortable sharing their opinions in meetings, challenged ideas more often, and started suggesting improvements and taking ownership of initiatives without needing someone else to push them forward. People even started to trust them with their personal issues, as someone that could guide and advise them.

Those skills were just not suddenly created. It was already part of them. People were simply starting to finally see them more clearly. Eventually, they grew into a QA Lead role and became someone who was highly respected across the organisation.

From my personal life to my professional life

That experience had a bigger impact on me than I expected. Seeing someone develop, gain confidence and grow into a stronger version of themselves gave me the same satisfaction I used to get from solving a difficult technical problem. In fact, even more than that.

It made me look back and realise that I had always enjoyed parts of this:

  • I enjoyed teaching.
  • I enjoyed mentoring.
  • I enjoyed helping people learn new things and progress in their careers.
  • I enjoy seeing processes or quality improve.

Some of that was already visible outside of work. For example, I used to be a football goalkeeping coach and I enjoyed every second of that. Seeing them develop from beginner level to the first team was very rewarding (apart from the fact that one of them ultimately took my spot as first keeper!). I have similar experiences with teaching people how to play chess or how to program. Management just brought that into my professional life.

That does not mean the technical side disappeared. I still really enjoy writing code when I get the chance. I still like understanding how systems work, improving automation, building frameworks and getting involved in technical discussions.

My new approach

Whenever I join a new company, I still usually end up exploring the technical side as well:

  • Building or improving test frameworks.
  • Looking at automation opportunities.
  • Understanding the architecture.
  • Helping teams improve their engineering practices.

The difference is that I have learned when my time is better spent enabling others to solve those problems themselves. That combination is what I enjoy most. The technical side keeps me curious, while the people side gives that work a bigger impact.

Of course, management still comes with things that are less exciting:

  • Difficult conversations.
  • Giving feedback that people might not want to hear.
  • Organisational processes.
  • Stakeholder discussions (athough I secretely quite enjoy these as well).
  • Prioritisation decisions.
  • Meetings that probably could have been an email.

But I no longer see these things in the same way I did years ago. I now see them as part of creating an environment where people can do their best work. And when a team is able to do that, the impact is much bigger than what one person can achieve alone.

Conclusion

However, the biggest lesson management has taught me is that people grow in different ways. Everyone has different strengths, different motivations and different things that hold them back. The job of a manager is not to create (or find) copies of themselves (and I feel like this still happens way to often). It is to understand what each person needs and help them become better at what they do.

So I never expected management to become such an important part of my career. Somewhere between the frameworks, the automation, the QA strategies, the one-to-ones and the countless conversations with people, I accidentely found something I genuinely really enjoy.


Alex Hovenkamp