Featured TC: Abhay Chokshi

March 2016

Abhay Chokshi is an Intermediate Technical Writer at Orion Health in Auckland. He manages a multitude of wiki sites, and creates documentation and information graphics for products that capture big data for technical administrators. He has recently taken on the role of Auckland Branch Coordinator, and he spoke to Tim Grey last week.

What initially drew you towards technical writing?

After completing my IT engineering degree I started out as a software developer in India, but I had a chance encounter that led me into technical writing. A technical writing job opened up where I worked, at Mahindra Satyam. The funny thing is, I didn’t know what technical writing was at the time. I was looking it up on the internet, asking friends – but ever since I took that job I’ve loved being a technical writer.

How much has the role changed for you in those eight years since and after immigrating to New Zealand?

The job is still quite similar, but it has evolved a lot too. Personally, for me, my journey has been that evolution from “just” being a technical writer to actually being a lot more – a technical communicator, a facilitator – as my knowledge and experience in the industry has grown.

I thought it was quite easy when I started out! Looking back, I thought it was quite straightforward – you use the software, you document the processes, and that’s it!

But we’re not just writing manuals anymore. We’re online, there’s a lot of complexity, and we’re writing for the in-between user as well as the end user. We’re no longer just interested in the how – we’re also interested in the why.

Also, in India we used a very modified version of Agile methodology, but here it is nice that Agile is diligently followed.

How has that start in software development informed the way you work as a technical communicator?

To an extent, that background has helped me form bonds with the software developers I work with, but on the flip side sometimes it has also hindered my perspective of the end user, to see things purely from the end user’s point of view.

But this is where topic analysis and role-driven documentation helps you in getting the right perspective. It is invaluable to simulate the user experience with invited people in defined roles so you can then start building user stories and documentation around that.

As well as being a qualified software developer and technical communicator, you’re also quite an accomplished speaker (a member of Toastmasters International), and a bit of a social media whiz. How do you fit it all in?

I think if you want to continue working as a technical communicator you have to keep adding skills. You can survive just with writing, but it’s always an advantage if you can do more. Which is why, if the opportunity arises, I’ll get involved in testing, help out with business analysis, and even design graphics.

As well as TechCommNZ, you’re also an active member of the Society for Technical Communication (STC) in India, and helped with the Annual Conference. Can you tell us about that?

I had the chance to present at the 2014 STC India conference – the first time I had addressed more than 200 people in about five years – and drove the social media campaign for the 2015 conference. I ran several contests and managed the Twitter and Facebook accounts. I’m a big fan of conferences anyway. I understand that it is difficult to replicate the advice you’re given directly into your own work environment, but you can come back with great information, and with some real thought you can apply the ideas you’ve learnt.

Looking ahead, what do you think are the biggest challenges facing technical communicators, and what are the changes you’d most like to see actioned?

In New Zealand, correct me if I'm wrong, the technical writing role itself needs to be valued better. If writers can bring more ideas that solve user’s problems and justify their ROI, then companies may value technical writing better and it will help us change perceptions as well.

Ultimately, I think it is important that we all come together and collaborate more, and have a better sense of what is happening in the industry. That's why I joined TechCommNZ, and why I'm excited about being involved in the Auckland branch. I'm looking forward to meeting, and working with, my colleagues in New Zealand.