Rocket scientists, though brilliant, have a very limited "comfort zone" when it comes to conversational skills, and I'm learning that NASA engineers are skittish beasts at best.
So I work for a company that is the leading provider of Product Graphic Management (PGM) software. Out solution, essentially, is designed to help companies translate, store, manage, and re-use their existing 3D engineering CAD data for downstream purposes like product catalogs, service manuals, product documentation, ietm (interactive electronic training manuals), and general collaboration between departments where 3D assets are best utilized.
My job consists of listening to engineers tell me their life story about how their job is the coolest in the world--which, for some--it actually is. We deal with the big three auto manufacturers, the top 5 (out of 6) aerospace firms, and the government (as well as graphic production companies and film studios), so I should've known better then to give a contact my direct line because last Friday he calls me 7 times to put out a fire (that I had no clue as to how it started, why it was happening, or how to fix it) but since he is from Large Governmental aerospace/aircraft design company that isn't LM) it is in our best interest to fix the problem, since 10 divisions of said company do business with us. Fires were put out, all was right with the world.
He called back today and I've spent the last hour on the phone with him trying to sort out random mess # 453.
I'm dealing with freakin' Rain Man here...."Yeah, there's a problem..yeah, a definite problem..."
So I work for a company that is the leading provider of Product Graphic Management (PGM) software. Out solution, essentially, is designed to help companies translate, store, manage, and re-use their existing 3D engineering CAD data for downstream purposes like product catalogs, service manuals, product documentation, ietm (interactive electronic training manuals), and general collaboration between departments where 3D assets are best utilized.
My job consists of listening to engineers tell me their life story about how their job is the coolest in the world--which, for some--it actually is. We deal with the big three auto manufacturers, the top 5 (out of 6) aerospace firms, and the government (as well as graphic production companies and film studios), so I should've known better then to give a contact my direct line because last Friday he calls me 7 times to put out a fire (that I had no clue as to how it started, why it was happening, or how to fix it) but since he is from Large Governmental aerospace/aircraft design company that isn't LM) it is in our best interest to fix the problem, since 10 divisions of said company do business with us. Fires were put out, all was right with the world.
He called back today and I've spent the last hour on the phone with him trying to sort out random mess # 453.
I'm dealing with freakin' Rain Man here...."Yeah, there's a problem..yeah, a definite problem..."
- Mood:
nerdy


Comments
I had a similar situation come up when I wrote documentation for a company that made satellite communications software. I had the unfortunately rare opportunity to visit customer sites and do direct audience analysis for our documentation products. This being a rare situation, I did not have the experience to know not to blithely hand out my business cards.
For months I had to deal with satellite operators calling me with their suggestions for doc improvements, including one who asked me to make the font "more bluer".
(I have defended my geeky brethren!)