Portfolio
Portfolio
Just about everything I have written is protected under non-disclosure agreements so it is very difficult to show work samples!
Here are a few tech writing samples of publications that I did for companies that no longer exist.
Web Scraping Technique and Legalities
Visio Diagram of Medical Provider Direcory Updated Standards
Traditional Help File Table of Contents Structure
Software Operation Instructions
Bug Report Status Descriptions for Management
Business Analysis-System Documentation for Future Enhancements
This was a very daunting task and is written in very amusing and informal techno-geek speak. No one knew how the work in these systems was done or how they dovetailed together except those who had bandaided this system together. This document was originally aver 70 pages long. Part of my expertise includes streamlining material into easily accessible and understanndable documents without losing key information. The systems documented here illustrate how a small system for an initially small company grows beyond expectations and how and why system consolidations and computerizations are necessary. The other very traditional and very trained senior business analysts did not like this document and I think they slandered me about it -even after not having reviewed any of the drafts I turned in every week for thier review, as requested -they, one in particular, had agreed to help me and never did. However, it must be noted that these very senior $200/hour analysts could not figure it out enough to document it, and so I was called in after they could not do it. We often see this, talented less experienced people just getting the job done! This document describes everything that multifaceted system did. The next step was to design an enhanced system around these findings and describe it ("spec it out") with a classic business analyst system spec with all the bells and whistles of acceptable and expected business analyst techno babble. The Sr. VP who reviewed and approved the accuracy of this system description I did was very relieved and very happy and gave me very thankful acknowledgements with much gratitude. He was very pleased regarding my success of actually having captured all this. I did this work on just a short assignment I took out of curiosiity as I continued my job search. The lesson learned here would be for management to be aware of internal on-the-fly system development so that larger integral systems can be put in place before the small ones fail, ensure that knowledge transfers and minimal system documentation occur, and ensure some sort of proper naming conventions relevant to the business processes. The geeks named their system modules in very amusing and very confusing ways. However I must say this was an amazing multifaceted system that did many amazing things.
An editorial commentary: In hindsight it is very intriguing to me to note that these companies -that I have not named- no longer exist. These and such others not on this list, went out of business, in my opinion and observation, because of very poor behavior on many levels. I observed very poor behavior rampant throughout these company cultures at all levels of their corporations. I am always very careful to observe all the behaviors of all the employees I interact with and I find that I can predict the future success or demise of that company based on its' peoples' behavior and mindsets. Poor behavior does totally come from the top, down. Any type of poor behavior is very destructive and does contribute to serious corporate financial problems and even failure - I call it Karma. It is rare to see Karma play out so rapidly to bring down some that were "too big to fail".
