Lately I’ve been having a bit of trouble coming up with things to blog about. It’s not that there aren’t subjects worthy of discussing or exploring; it’s just that most of them have to do with my job and I’m uncertain over whether or not – and to what extent – I can share what it is I’m doing and the issues my company is facing. Neither is any of it “Top Secret” (though some of our work is) but, rather, we are an old and staid aerospace company with deep roots in governmental contracting and with a strong impulse to hold everything we do close to the vest. This is, in part, to protect our intellectual property which, in the world we move in, is quite valuable, and the need to comply with the provisions of the International Traffic in Arms Regulations (ITAR) that provide very serious – and expensive – penalties for “exporting” controlled information and knowledge. Export-controlled knowledge is our bread and butter, so I need to be sure I err on the side of caution.
So, I guess this in the way of a caveat. I would love to reveal more about where I’m employed; after all, I’ve been there over twenty years and my experiences greatly color how I see the business world and what I have to say about my struggles to incorporate Enterprise 2.0 design principles and tools within the organization. Unfortunately, I won’t be able to do so for the foreseeable future, though I am working on figuring out just how to step up the precipice without dropping off the cliff of inappropriate posting. I suspect this will be an ongoing struggle, but I will keep trying to figure out how to share my thoughts about our efforts at developing into a company that derives a large part of its income from industrial and commercial efforts, rather than government contracts.
Systems Savvy 