Skip to main content

Stuck in the Comfort Zone?

I was recently reading a good friend of mines blog Helen Meek where she discusses 3 zones that are related to how you work, i'll briefly explain them here, but you can read the blog to find out more:

Comfort Zone: This is where you're effectively coasting along, not challenging yourself in your day to day job.

Learning Zone: This is where you challenge yourself and are learning new things constantly.

Panic Zone: Where there's just panic, you may be challenging yourself, but probably not having the time to learn new things.

I think, that too many people in Engineering are stuck in the Comfort Zone. They are bored easily, but don't want to do anything to change that as it involves challenging themselves and what they know. I want to help get people out of the comfort zone, but doing so isn't necessarily easy.

To me, like most people I would bet, I'm most happy when I'm in the Learning Zone, I get bored and restless in the Comfort Zone, and the Panic zone isn't healthy for anyone! It's just not sustainable.

How can we encourage people out of the Comfort Zone?

I think first you need to find out what people find engaging and what interests people, if you find that then you can engage with them to help get them out of the comfort zone.

Secondly, by working closely with them you can learn how to push their buttons and challenge them on a daily basis, i'm not necessarily talking about setting objectives, but more about finding out about what makes them tick and why they do what they do, if they can rediscover what they love about testing then pushing them into the learning zone will be that little bit easier.

Finally by offering them an environment where they can do what they love, and recognising success and rewarding it as such, will help people come out of the comfort zone and hopefully thrive.

I have been lucky in that I currently have an environment where I do what I love, and people are aware of what interests me and what makes me tick. The next step is really offering this opportunity to others and hopefully move them out of the comfort zone and into the learning zone.


Post a Comment

Popular posts from this blog

Advantages of using Test Management tools

Before I start talking about test management tools, let me clarify what I mean by the term test Management tools...  I am not taking about your office excel program where you store your test cases in. I'm talking about bespoke test Management tools, your quality centers or Microsoft test manager...
In the strict case of the term test Management tool, Microsoft Excel can be used as such, but heck, so could a notepad if used in the right way... For the sake of this blog post I am talking about bespoke test Management tools.
Firstly, what test tools are out there? There are many more out there today than when I first started in QA over 5 years ago. When I started the market was primarily dominated by a tool called Quality Center, this would run in a browser (only Ie unfortunately) and was hosted on a server.. Nowadays it's market share has somewhat dwindled, and there are some new kids on the block. 
One of the more popular tools is that of Microsoft Test Manager, it's big…

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…