Content

Contact

Contact OakenDoor to request a phone or in-person consultation, services, or more information by filling out and submitting the following form. All information submitted is strictly confidential.

Name:

Email Address:

Your Message:

Technical Writing Samples

The following samples include PDF files and a Help system, all of which highlight Information Architecture produced through Technical Writing.

Akori

Azimuth

The Use of Tools

OakenDoor maintains expertise in the following writing and publishing tools:

Content Management Systems

Learn all about Content Management Systems

Technical Writing

Techical Writing is better described under the umbrella of Information Design. Technical Writing was a good concept when it began, but it never really took off because, for one, technical writers aren't necessarily highly technical people. However, Engineers expect people with "Technical" in their title to be highly technical - in something other than Information Architecture and its associated tools. Additionally, writing doesn't encompass what technical writers do either. Technical writers produce well-formed Information Architecture for starters. They also produce, maintain, and archive complex systems of information that need to be accessed and output on a regular basis, and in different forms. Technical Writers were advocates for Experience Design long before that term even came along.

The delivery of information, unless you are wearing headgear that puts you into a 3D world, is delivered in a 2D environment that is comprised of words, images, video, and sound. That is what Technical Writers produce, so Information Design is a more focused term. While people often say to me that they don't want to get hung up on the name, but rather the function, I'm still relating this information on a regular basis because the human condition is to understand a whole person in a professional environment based on their title. That's why Human Factors in Information Design has branched off into terms that didn't even exist at a high level when Information Design first started. Back then you were an Information Designer. Now you can be a User Experience Designer, Interaction Designer, User Researcher, Usability Tester, etc., etc., etc. OakenDoor, however, does it all, and still produces some of the best tech comm content you've ever seen. Companies need to refocus on Information Design by taking a look at the whole problem with their interface or widget instead of focusing on making the documentation simply go away. OakenDoor looks at the whole, which is what every Information Designer should be doing. So, to that end, you'll find many excellent Information Design samples on this page - even a Help system that puts a fine point on the statement of Technical Writer as Information Architect.

Additionally, good technical writers produce well-formated DITA/XML in environments where that is necessary, and good technical writers have a working knowledge of assessing, helping to implement, and helping to manage content management systems.