Once you’ve published your help content, it’s easy to fall into the trap of marking documentation as “done” and thinking you’ll only need to update it to reflect new functionality. But just as with your software, your initial docs launch should be just the beginning of an ongoing process.

Not every software team has a technical author on hand to manage their documentation. If you've been tasked with writing a user guide and you're not sure where to start, I've got ten tips to help you on your way.

With so much attention being given to how ChatGPT could replace technical authors, I wanted to share my experiences of the value that technical authors add to the software development process beyond the documentation output.

A technical writer can do much more than just create clear, concise copy; having stepped into your users’ shoes we can help you refine the user experience. But how do you get the most out of working with a technical writer? I thought I’d share my top three tips – a user’s guide to technical writers, if you will 😉

When I started out as a technical writer, two phrases seemed to play on repeat: "Just document around it" and "No one reads the documentation". It got me thinking - what is the value of tech docs?