Technical Writing.

Technical Writing is writing for the purposes of instruction, direction, explanation, or guidance. You’ll find it wherever you see a product, a website (especially e‑Commerce), or anywhere that people use documents to help them be productive. In this sense it’s quite different from both copywriting and content writing.

How is technical writing different?

This type of writing is precise, clear, and to the point. Its primary purpose is to enable the reader to do something. This is why it emphasises accuracy and brevity, rather than elegant style or narrative. Your challenge is maintaining your brand voice when you create technical documentation.

Because its output is ‘technical documents’, tech writers often refer to themselves as ‘documentarians’. Their job is ‘to document’ a product, a service, or how to do something. 

For a hilarious (and very useful!) explanation of technical writing, watch this video:

Technical Writing by Brutal Pixie.

This service includes:

  • discovery phase, to make sure that we understand your digital environment, requirements, and brand voice.
  • Creation of guidepost documents for you if you don’t already have them, such as brand voice guides.
  • The writing itself.
  • A guided, collaborative review process.
  • Delivery in any format that works for you, including plain text, Markdown, HTMLPDF, or even a Word doc.

At Brutal Pixie, we are proud to work to industry standards. We’re members of Write the Docs, the Australian Society of Authors, and the Media, Entertainment and Arts Alliance.

Technical Writing Training for Software Engineers, by Brutal Pixie.

Here at Brutal Pixie we are Google-​trained Technical Writing instructors! If you have a team of software engineers, and you want them to create good documentation for the products that they’re building, we can train them for you.

There are two levels of training. We can run it online or in person.

For more information, contact us.

What type of documentation can we write for you?

We will work with you to create:

  • instructions, user guides and manuals
  • help files or reference documents
  • knowledgebases
  • policies and procedures
  • certification and accreditation documents
  • reference documents
  • training materials
  • installation guides
  • … and much more.