I have agree about the definition and the need for somewhat more implicit guidance. The problem however as several of those among us who've been talking about it for a while know seems to be the my piece of the pie syndrom.
By this I simply mean that because real Information Operations is and should be inclusive of all the varied areas of study mentioned in joint pubs and more. With this being the case it has been my experience that those of any particular discipline percieve and approach it in that light. The EW guys can naturally find all the different ways to gain information superiority with their systems, the same goes for all other groups and as such what you generally get reflects who you've got.
The statement I've heard most often has been that it seems to get too complicated when you actually start breaking down all the various components and capabilities and there is often an assumption that those charged with doing it won't be able to do it well enough. I would tend to agree with MAJHEFNER in that. It's just made harder by those who try to place it in their own boxes.IO is nothing more complicated than the art of influence.
I would suspect that 99% of what a good IO planner works with and the skill sets used are not much different than what most anyone does within the confines of their own lives on a daily basis. That said OK lets get a definition that is more explicatory, the toughest part is going to be making it such that all who read it don't read too much, or too little into it, but rather accept it for what it is.
BTW remember I always like to over simplify things
Bookmarks