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!


Post a Comment

Popular posts from this blog

What is a PBI?

After my last post, I had the question of what is a PBI... so I thought i'd write a short blog post about what they are and why they are used.

A PBI is an acronym for Product Backlog Item. It is a description of a piece of work that your SCRUM team will develop and deliver. When you have a list of Product Backlog Items, you then refer to that collective list as a Product Backlog.

The product backlog is often prioritised and yourteam will work through each PBI, and release on a regular schedule... I am however going deep into the world of Agile development, which isn't entirely what this post is about, so I will stop myself now.

A Product Backlog Item is made up of the following:

Title - This is often a one liner that gives the team an idea of what the PBI is about, although it can just be an ID for the item and the team work off of that.

Description - Breaks down the PBI in a bit more detail, and can be written in any style, however I prefer it to be written as follows: 

By writin…

Dealing with Selenium WebDriver Driver.Quit crashes (Where chromedriver.exe is left open)

We recently came across a problem with Selenium not quitting the webdriver and this would then lock a file that was needed on the build server to run the builds.

We were using Driver.Quit() but this sometimes failed and would leave chromedriver.exe running. I looked around and found this was a common issue that many people were having. We (I say we, as we came to the solution through paired programming), came up with the following, that would encapsulate the driver.quit inside a task and if this task takes longer than 10 seconds, then it will clean up any processes started by the current process, in the case of the issue on the build server, it would kill any process started by Nunit.

        public static void AfterTestRun()
            var nativeDriverQuit = Task.Factory.StartNew(() => Driver.Quit());
            if (!nativeDriverQuit.Wait(TimeSpan.FromSeconds(10)))

        private s…

Famous Movie Quotes applied to Software Engineering - Jaws

You're gonna need a bigger boat? How can that relate to Engineering?

Firstly, let me ashamedly admit, that I've never seen the whole of Jaws all the way through. It's on my list of films to watch, but whether I get round to it, is another matter!

Anyway, to apply this to engineering, it's almost like "you're gonna need more testers/developers"...

We hear this all too often when trying to push releases out the door, let's throw men at it... However, as we all know, a bigger boat/more men... isn't always the answer, it's not a guarantee of quality, or even a guarantee of getting things done quicker.

If you have a task that will take 2 hours, simply having 2 people work on it doesn't mean that it is halved, in fact often, the time taken to do the task remains at 2 hours, but the maintainability and the knowledge around that area is increased, so it's a price, in my opinion that is often worth paying.