Technical Writing Process: The simple, five-step guide that anyone can use to create technical documents such as user guides, manuals, and procedures

Some technical writers are thrown into this job by people who assume we just take a Word document and copy and paste whatever people tell us we should do. This helps provide the tools to push for reasonable acceptance within your business of what you do, especially if you're a one person design, writing and publishing team like so many of us are these days. If you don't have a required form to use already, download the templates so you have a professionally designed framework ready to go. The last thing we all need is one more doc to design and present to others, even though that is what will end up happening anyway (you won't feel like you did as much work as you wound up doing anyway at least). After going through a few similar books at the library, this is the first one I encountered which I could forward to people to help them understand project management of technical writing, especially in an Agile environment where all tasks and projects are tracked.

The content of this book is great. Informative, educational, and useful. But in the Kindle version, there are multiple sections of missing pages, which made for a very frustrating experience.

Nice framework. More suitable than earlier documentation management texts for the more agile modern workplace. Better than Hackos for smaller workplaces wth less legacy documentation where you have more new content to write and less old content to maintain or manage translations on. Still a place for Hackos, but probably mature industries only. Would like to see how to apply a lighter framework like this within a development DevOps Docs like Code environment. Maybe if the templates were wiki based not Office files to be resources that developers would use from Linux not Windows.

I personally thought this book was boring and did too much beating around the bush. I had to skip a ton of pages just to get where I wanted to start without all of the fluff. Half of the book is introduction which wasn't worth my time or money.

This was exactly what it claimed to be and exactly what my team needed: A thorough, but surprisingly accessible, review of key components in technical writing to help beginners and non-technical writers. I have a small team of non-technical writers (a trainer and an analyst) who have been charged with helping to develop documentation standards and a centralized library for our client support team. The concepts in this book were spot on for helping us develop a great first-pass implementation on this project. Highly recommended for anyone else facing the challenge of improving support documentation - without experience and training as a technical writer!

As the title suggests, this book focuses on the technical writing process, which it does very well. I have found this to be a really useful resource. It is well written and contains a lot of good advice for technical writers of any skill level and can be easily used when writing many different forms of documentation. Highly recommended.

I purchased this for a class I am teaching, but I ran into some financial and administrative harangues. Nevertheless, I read this book and started course planning with it, and it is the most appropriate tool out there that bridges writing process with technical writing. I will eventually use it...I will make it happen.

If you have no experience or formal training with technical writing this book will help you think and work like a technical writer. Perhaps the best part of this book is how easy it is to read and it doesn't take much time at all to go cover to cover.

Bought this for use at work. I’m a Quality Engineer and had a document criticised unnecessarily and this proved my point. Good reference aid at work would recommend

So easy and simple to understand! I found this much more helpful than other technical writing books I've looked at and I recommend it as a great place to give yourself a solid foundation. The structure of this approach really worked for me. Thanks :)

Solid description of the process. The book does not offer any surprise techniques, but covers all the bases with solid, easy to follow common sense remarks.

This is a good read and provides a simple framework to develop a range of technical tools using a simple 5-step process. The process is supported by templates and written by an Australian consultant who refined the process in the field. The book is a good foundation for entry level technical writers or non-writers.

Refer to this all the while. Really useful book