Skip to main content

How the Golden Circle can help you become a Great Tester

I was recently watching a TED Talk by Simon Sinek: How great leaders inspire action... It's a truly inspiring video, and one that I highly recommend you watching it. Like any great video/speech it got me thinking and trying to apply it to my life/world. As you know a lot of my life/world is around testing and so naturally I started asking myself the following questions:

- What helps makes great testers?
- What makes people really appreciate the value of testers?

Now in the video Simon mentions what he calls "The Golden Circle" which you can find a neat little diagram of below:

Using this he helps explain what makes leaders/businesses great, it's not the What of what they are doing? Nor is it necessarily the How? It is in fact the Why of what you are doing. If people can connect and resonate with the Why of what you are doing they are going to follow you, they are doing to buy into your product and appreciate the value you bring even you more so.

This made me think, what helps makes a Tester Great? Is it the What? Is it what they do? Is it testing software/requirements? Is it finding bugs in software?  This is all fine, it's an end to a means, but the question isn't, What makes a fine Testers? It's what makes a Tester great? To me, this will not make you a great tester, nor will it really demonstrate the true value in which you will bring to a team of engineers in developing quality software.

What about the How? Some testers know and are extremely confident in how they are going to test something, so they go ahead and test it, some testers however might not know the How's completely, and require on help from others in figuring this out, again this is okay, team work is about helping others be better. Does the How make you a great Tester? No, it probably helps makes you a good Tester, but this isn't what will make you a great tester, nor will it make others truly appreciate the value in what you are bringing.

Finally, we are on to the Why? Very few testers that I work with, truly understand the Why of testing... Why are we testing something in a certain way? Why aren't we testing this? I feel that this is what will help make you a great tester. Find out the Whys of Testing... Why we are performance testing something in this way, or Why we are testing something this way, if we can figure out Why we are testing something, then we can define How and What we are testing so much easier. If we can define this instead of relying on people to tell us what to test, and why we are testing it then we are helping them understand the true value of Testing. This I truly believe will demonstrate to the team and others the true value of great testing. 

You could look at it at the bigger picture, if we understand why we are doing our jobs, then we understand the value we bring, and this will rub off on others, and help others truly appreciate what we bring to the table.

So I suppose another question is, how can we get to the point where we truly understand why we are testing something. One route is to fully understand the architectural aspects of a solution, or to understand how it is being developed and understand the code behind the application, this will help us understand why we are testing. We can also ask lots of questions, not just about development, but about requirements, about why we are doing something? Truly understand the end user, and then we can shape how we test something and what we want to test and in doing so, hopefully help everyone understand Why we test, and the value that we can all bring by working closely with others in the team and not off in silo.

Finally, and a bit of a disclaimer obviously, knowing the Why of Testing is not going to make you a Great Tester, it will help, and it will help people appreciate the value you bring, but there are many aspects that I will cover in another post that help make Great Testers, so stay tuned!

Comments

  1. “He who has a why to live for can bear almost any how.” ― Friedrich Nietzsche

    ReplyDelete
  2. " If we can define this(why?) instead of relying on people to tell us what to test, and why we are testing it then we are helping them understand the true value of Testing" very true

    ReplyDelete

Post a Comment

Popular posts from this blog

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...

QA is Awesome!

No real point to this post other than I have had the song stuck in my head and figured I could change it slightly and quite easily make QA is Awesome! Oh and I haven't even seen the movie all the way through! But for some reason that song is incredibly catchy! Not much point to this post in fact, just thought I'd put it out there :)

Measuring QA Key Skills and Competencies

I have been thinking about how I can help encourage self improvement within my team, as I understand it, everyone wants to improve, it's just that often there are a number of things that hold people back. I believe one of these things that hold people back are around identifying skills that they are perhaps weak in or that they could/should improve on. So I thought about how I can help tackle that problem. One solution that I want to try with people is to identify the key skills for a QA, what key skills should every QA have, or at least what key skills make up a good QA? If I can identify these then I can start helping people identify if they are lacking in an area. Sure there is a competency matrix that we have, but it has things like "An excellent understanding of XXX", it's often very difficult to quantify what an excellent understanding actually is. So I sat down and came up with the following key skills: OOP Test Documentation Manual Testing Automated...