Skip to content
Leading Australian training company since 1989
facebook
twitter
youtube
linkedin
IRM Training Logo
Call Support 1300 819 078
Email Support training@irm.com.au
  • Home
  • About Us
    • About IRM Training
    • Testimonials
  • Courses
  • Locations
    • Brisbane
    • Canberra
    • Melbourne
    • Sydney
    • ‹ More Locations ›
  • Services
    • Public Training
    • In-House Training
    • Flexible Group Training
  • Certification
  • Resources
    • BABOK® Course Mapping
    • The BA’s Training Roadmap
    • Partners & Links
    • Articles »
      • The Role of Business Analysts in Cybersecurity Analysis
      • The Future of Business Analysis in the Age of AI
      • Business Analyst Salary & Job Trends – End of 2020 Review
      • Practical Training Delivered Remotely (Live)
      • Business Analyst Interviews
      • Introduction to Agile (and Scrum)
      • More…
  • Contact
  • Book Now

An Introduction to Technical Writing

Home > Requirements > An Introduction to Technical Writing

An Introduction to Technical Writing

09/03/2008 | By IRM Training
0

At some time or another we all have to communicate using the written word, but all too often improving writing and communications skills are at the bottom of our “to do” list.

Yet how many times has poor communications led to incorrect decisions or even downright confusion?

We’re not alone either – look at this extract from public documents issued by one of the world’s leading banks:

“Trade finance is designed to assist meet cash-flow shortages arising from a mismatch in the timing of making payments for goods or raw materials for use in manufacture of goods and the receipt of payments from the onselling of these purchased or manufactured goods”

You have to read this 2 or 3 times before the meaning becomes clear.

technical writing

Governments can be equally guilty – as you can see here in this example from some recent legislation:

“For the purpose of making a declaration…
a) treat a particular event that actually happened as not having happened; and
b) treat a particular event that did not actually happen as having happened…”

It looks like no organisation has a monopoly on poor writing skills and with the move to “online everything” we’re further tempted to cut corners as SMS, e-mail and online publishing become the mediums of choice.

Whilst we don’t advocate a return to “formal, grammar school English” we do need a balance, particularly when documents such as reports, manuals etc. spill over several printed (or online) pages. Traditional skills such as document structure, writing style, audience identification, grammar etc. are timeless – and essential if we want to connect with our readers.

In the following introductory chapter from IRM’s Technical Writing Skills workshop we look at what defines good writing and how to get started.

Read full paper here: Introduction to Technical Writing

 


If you liked this paper, you may also like:

Writing Better Requirements

How Clear is your Writing?

Just Enough Documentation


 

Share this!
Share on print
Print
Share on email
Email
Share on linkedin
Linkedin
Share on google
Google
Share on twitter
Twitter

Tags: better writing, flesch scale, technical writing, technical writing template

Previous Articles

  • Workshop Facilitation – How to Engage Quiet Participants
  • How to Create Use Cases
  • The Role of Business Analysts in Cybersecurity Analysis
  • The Future of Business Analysis in the Age of AI
  • Business Analyst Salary & Job Trends – End of 2020 Review
  • Practical Training Delivered Remotely (Live)
  • Business Analysis Industry Trends in 2019
  • Business Analyst Salary & Job Outlook
  • Business Analyst Interviews
  • Introduction to Agile (and Scrum)

Get in Contact

Phone: 1300 819 078

Email: training@irm.com.au

Online Contact Form

New Articles

  • Workshop Facilitation – How to Engage Quiet Participants
  • How to Create Use Cases
  • The Role of Business Analysts in Cybersecurity Analysis
  • The Future of Business Analysis in the Age of AI

Explore Topics

activity diagram BPMN business analysis business analysis techniques business analyst business analyst training data flow diagrams interview techniques problem solving process modelling requirements gathering technical writing UML use cases user stories
© IRM Training Pty Ltd 2025 - ABN 56 007 219 589 | Terms & Conditions | Privacy Policy | FAQs