– Technical Writing –

  • BAs, via the Requirements Gathering process, become expert on the topic in question.
  • Such familiarity makes them a solid resource to author non-BRD artifacts.
  • These include Help Manuals, GUI Standard, marketing tools,and PowerPoint decks.

Provided are several examples of my Technical Writing background.This section will display numerous samples of my work, including:

  • HELP Section Creation (RoboHelp)
  • GUI Guides for Developers
  • Marketing Material
  • C-Level Summations

PORTFOLIO DIRECTIONS

ov

PORTFOLIO CONTENTS

twa

(OBSOLETE ORIGINAL): After designing a new Contract Management system I was tasked to author an accompanying Help Section using RoboHelp. This is a WORD version of it.  

twb

(CLIENT BANKRUPT): After creating a new Enterprise Asset Management system I authored a complete Developers Guide to aid the developers in coding it correctly.  

twd

(CLIENT BANKRUPT): Soon after joining an Internet start-up I was assigned to create a professional marketing brochure, laying out what made the new agency stand out.  

REDACTION POLICY

  • OBSOLETE ORIGINAL: Projects that are  authored yet later permanently consigned to the bin fall in this category. The project never existed and never will exist.
  • CLIENT BANKRUPT: In circumstances where both sides of the dev agreement are no longer in business the documents are treated the same as OBSOLETE ORIGINAL.