Don’t let anyone hold you back

Testing Planet Newspapers

I’ll never forget the sadness that was conveyed in Cheryll’s words as she politely, but carefully, rejected what would be my very last submission to a popular testing magazine. Me and Cheryll had history. I’d submitted 10 articles to the magazine, and 10 times she had sent me the rejection email.

It wasn’t her rejected me, it was the editor, but she knew my pain. She was the messenger.

Continue reading “Don’t let anyone hold you back”

Build Quality In – The Book

Regularly readers will know the journey we’ve been on here at NewVoiceMedia and the way in which we’ve shrunk our release cycle down from yearly to weekly.

It’s an honour then to have been invited, along with my colleague Lyndsay Prewer, to contribute a chapter to an upcoming book called “Build Quality In“.

We’ll be sharing a story of our transition from yearly to weekly releases. We’ll feature in the book along with many other people doing great things in other companies.

70% of the profits are going to code club, a not-for-profit organisation that runs a UK-wide network of free volunteer-led after-school coding clubs for children aged 9-11.

The book is being curated and edited by Steve Smith and Matthew Skelton and can be bought on LeanPub.

60 Day Proof

Everytime you write something down think about making that writing 60 day proof.

The 60 day proof concept goes something like this:

“If I were to re-read what I wrote in 60 days time, would I know what it meant and would it still make sense?”

I’ve spent the last few years fine tuning my own writing based around this simple rule with lots of success. But also with lots of gaps and holes and at times I simply forget. I first encountered this 60 day proof idea in Michael Bernstein’s thesis on scrapnotes (an excellent read for people who make lots of notes) in which a subject he was observing made all of his/her notes sixty days proof. I was struck with how simple, yet powerful, this concept could be when applied to my everyday work, from note taking to defect reporting. It embodies my promotion of Purpose, Audience and Context principles for communication.

For everything I wrote down I tried my hardest to use this principle. This covered emails, notes, messages and any other form of communication I could…and it made a massive difference.

Adopting this simple concept meant I struggled less with ambigous notes and reports, had fewer of those “give me a minute to get my head around it” moments and it also made my communication even easier to understand by other people.

I still find notes in my pad that make little or no sense. Typically one time reference notes such as IP Addresses, temporary snippets of product information, blog ideas and key words that trigger thoughts in my head. But on the whole I’ve really started to take the care and time to write my notes with recall as a clear objective or purpose. It’s made a huge difference to my defect reporting as it’s made me think about making these defect reports as readable, understandable and future proof as possible.

Why not give it a go and see if it changes your writing. It may be you write your notes, emails, reports and defect reports with clarity in mind, but I thought the same also. Only on inspecting my writing did I find plenty of areas of improvement. Writing is a process of continous improvement and the 60 day proof concept, when considered constantly, has made a marked difference to my testing world. Let me know if you use a similar process or whether this concept might work for you too.