How to Be Seen

One of the difficulties of being a software tester is that when you’re doing your job really well, it’s unnoticeable! Unlike software developers, who are creating a product that will then be seen by management, software testers create tests that will help validate that the product is working correctly. When we do a great job, it’s not clear what the difference is between the product that would have gone out to production if we hadn’t found all the bugs, and the product that actually did go out to production.

The problem with not being seen by management is that it becomes difficult to advance in one’s career. Fortunately there are four different ways that we can make sure that our managers and others see the impact we are making.

Tell Them:
Make sure that you are letting your manager know all of the ways you are helping to make a great product. For example, in your daily stand-up meeting, you could say “I found an important bug yesterday in the chat feature that would have kept users from accessing their chat window if it went to production.”

Also be sure to mention whenever your test automation catches a bug: “Our automated regression suite caught a critical bug on the User Info page shortly after the change was deployed to the QA environment.”

Show Them:
Managers love dashboards and metrics. Remember that managers often have their own managers to whom they need to report. If you can make your manager’s job easy by providing them clear data about the quality of your application, they will be very grateful.

For example, you could create a dashboard that shows the pass/fail rates of your nightly regression tests. This dashboard could show the different environments you are testing in, and ideally it should show that the passing rates in your Production environment are near 100% because the automation found the bugs well before the new code made it to Production.

Or you could start keeping metrics of escaped defects: these are bugs that made it to Production without being noticed. Ideally the number of escaped defects will be zero, but even if it isn’t, your metrics for each release can demonstrate that your team is getting better at releasing bug-free code.

Teach Them:
Having lots of great software testing skills is awesome, but what is even more awesome is teaching those skills to others in your company so they will be as effective as you are. Your company probably has a number of different ways that you can teach others testing-related skills. For example:
* Talking about an automated test framework you are using in a departmental meeting
* Leading a workshop for other testers about how to adopt the test framework
* Mentoring a new or struggling tester

Lead Them:
Your manager can’t see you as a leader if you don’t speak up! One great way to lead is to suggest process improvements for your team during your Sprint Retro meeting. When your team adopts those ideas and sees the quality of your product improve as a result, you’ll be seen as a positive change agent.

Setting up a Community of Practice (CoP) meeting is also a great way to stand out as a leader. In the meeting, all the testers at your company can gather together and share ideas and solve problems. If your company already has a CoP meeting, volunteer to lead a discussion or talk about an innovation that your team recently adopted.

Common Objections to Being Seen:
Software testers are often introverts. Many of them enjoy working quietly, testing features and writing automation without much interruption from others. Some prefer not to be the center of attention. It’s OK to feel this way, but it will not get you promoted!

If you are shy or fear public speaking, start out by making small improvements. You could begin by creating a blog post or test dashboard. Then you could try adding one comment in each Sprint Retro meeting. Next, you could volunteer to demo a new feature at a meeting. You can continue to add small steps in this way until you feel comfortable enough to run a workshop.

Final Thoughts:
Software development processes have come a long way in the past two decades; there are very few managers today who don’t understand the importance of software testing. But they may not notice your contributions to your product unless you make sure to be seen. I hope that the above suggestions will help you show your manager what a great asset you are to your team.



7 thoughts on “How to Be Seen

  1. Arjun bm

    Nicely written. We software tester create a lot of value to the product but don’t often get recognized as you outlined we are in silos or we work quietly ๐Ÿ™‚ because of that. we have to speak up and show them the value of the work we do. Thanks for this awesome post. I follow all your posts and you are a true inspiration to me ๐Ÿ™‚

    Reply
  2. Pingback: Five Blogs โ€“ 23 November 2020 – 5blogs

  3. Chandan Gupta

    Agreed with all the points mentioned. Fortunately I have been doing all. Recently I decided that demo will be given by QAs and not Developers which was welcomed and it gave an opportunity to be a speaker, I am loving it. Regarding dashboard, I made an excel with details like Userstories, assigned Dev, QA, expected and actual arrival and completion date and shared it with the entire team. Since we have virtual stand up now, the sheet is the first one to be presented, discussed and updated. This is in practice since the sprint started. Happy that I am following all the points that you have mentioned. All I believe is make the right noise at right place. Thanks

    Reply
    1. kristinjackvony Post author

      This all sounds great, Chandan! Doing demos is definitely a great way to be seen, and testers often know more about the product than developers do, so it’s an effective way to demonstrate your knowledge. And using a spreadsheet to keep track of the team’s work is a great way to show leadership skills. Keep up the good work! ๐Ÿ™‚

      Reply
  4. Nandini S

    Great post.. I have faced a lot of not recognised by the inputs given by testing team. The managers as you mentioned should be matured enough to involve testing person.

    Reply
    1. kristinjackvony Post author

      Hi Nandini- I’m glad you enjoyed my post! You are right that managers should know to involve testers in activities such as planning. Hopefully using some of the ideas in my post will help testers teach managers the importance of testing!

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *