Technical Writing.
The year was 2000.
Or, as those in IT termed it at the time, y2k.
As December 31, 1999 approached, Ian's boss was concerned that things would stop working (such as servers, security doors, and Ian himself) once the calendar flipped over to 2000. Ian was tasked to document different facets of his job. The saying goes : "give a busy person a task. They'll find a way to fit it in." The necessity to create documentation afforded Ian an opportunity to sit and think about the tasks that consumed the better part of his weeks.
He realised there was little point in describing what he did, unless he also described why these things were being done, and when they needed to occur. So, these documents needed to be more than just a dry laundry list of sequential dot-points.
Done properly, technical documentation transcends being a rarely-referenced folder on a dusty shelf - it becomes a procedure manual, a training guide, a knowledgebase. A library of resources in one place, potentially saving your business considerable time and money.
Would you like to read what others have said about Ian's writing?
How about reading some specialised examples of his technical writing?
www.ianharrison.id.au is developed, owned and run by Ian Harrison. Contents of this site are Copyright © 2021.
Some publishers and customers have placed restrictions on my current ability to reproduce some material.
What is posted on this site is a small sample of my work and IP. Contact me if you would like a quote or for more details.
![[Tales]](/Images/sm-tales.jpg){kind=small}
![[Technology]](/Images/sm-tech.jpg){kind=small}
![[The Pub]](/Images/sm-pub.jpg){kind=small}
![[Welcome to Ian's Site]](/Images/sm-home.jpg){kind=small}
![[To The Nines]](/Images/sm-nines.jpg){kind=small}
![[Blog]](/Images/sm-blog.jpg){kind=small}
![[Arty]](/Images/sm-arty.jpg){kind=small}