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.





Labels:

Comments

Post a Comment

Popular posts from this blog

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....
1 comment
Read more

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...
2 comments
Read more

Using BDD and gherkinising your Acceptance Tests

In my post Testing of Automated tests , I mention about a BDD framework which involves using BDD to drive your acceptance tests. BDD stands for Behaviour Driven Development.  One effective method of writing BDD tests are by using a format known as Gherkin language. These consist of Given, When, Thens. The main advantage of the gherkin language is that it's readable by the business, and in an ideal world forms part of the Conditions of Acceptance around a PBI. Also, using a Visual Studio plugin of SpecFlow , you can integrate your Gherkinised COAs into your solution with feature files, and then drive the automated tests, however, for this post I will focus solely on how to effectively gherkinise your acceptance tests. A Feature file consists of a feature outline, which details what the feature file is testing followed by Scenarios and examples (parameters).  The BDD scenarios are made up of a Given, When, Then... These are effectively an initial state (Given), an action (W...
6 comments
Read more