Tuesday, July 21, 2015
My company roadmap(s) document is going to be an enormous asset to my company. After thinking a lot about the more detailed documentation that my company needs, it's important to create something the gives structure to the less detailed company information. This document outlines what people that may not ever even use one of my products is going to see. Where is my company going? Why am I going to be profitable? What do people have to be excited about? Out of all the materials I have for my company, I need to condense it into one small, entertaining file. I wrote down a lot more guidelines for this than I expected because of the possible audiences for the presentation. This is something that I haven't currently put a lot of effort into, but need to do a lot better job. Being too modest when I'm trying to get people to notice me is not exactly a recommended business practice. I want people to not only like what I am doing, but to be excited about the potential that my company has. Creating my company presentations is not going to be easy, but outlining what they need to sound like was an important first step.
Saturday, July 4, 2015
I have created another area for the internal_documents portion of my company. My real work today was adding to what I am now calling my "product_documents_checklist" which is a guide for what I want to have for documentation for all of my products. I have updated this guide to emphasize my need for more comprehensive documentation. This means that at some point every product is going to get a folder called "product_summary" which includes the most detailed product information that I will have on record. Previously, I was mostly creating installation manuals, download guides, drawing flowcharts, and going over any higher level points that I thought might need to be illustrated. The "product_summary" area for each product will go over all of the features of a product from a very detailed perspective. This means that where I might have drawn a picture of data moving around in a program, I'm going to explain what is happening in each of those parts, why it happens, and what someone might actually expect to see. This means that all of my previous documentation work will still be useful, and there is a good possibility that I will find that I actually need to add a fair amount more to my existing areas.