Archive for ictech

Journalists vs Analysts

Posted in Web2.0 Productivity with tags , , , , , , , , on August 31, 2011 by Lance Strzok

I get the impression that a lot of analysts try to be journalists, and it got me thinking that maybe the road ahead is to actually make journalists within the IC.

How do analysts differ from journalists? The most obvious differences are level of knowledge on a subject, and objectivity. It is my beliefthat most analysts are pretty deep in tbrms of knowledge with respect to the subject matter they write on, and as human nature would have it, they are pretty attJched to their judgments on the things that they write about and don’t necessarily seek out others to collaborate with or open theclselves up to disagreement.

Journalists on the other hand, appear to me to be openly shallow in most subject areas that th~y write on when compared to analysts,but they seem more ethically bound to deliver balanced reporting on a subject after interviewing various analysts and SME’s for onions on the matter from various angles. In this way, the various sides of the story, and the drivers and stakeholders all get some kind of view represented in the report. (Want to highlight a little with respect tel differing motives and abilities here, depth of knowledge differences, motives differences, and objectivity or cognitive dissonance impacts as well as how each potential role might yield a different result).

So taking much of what I mention above as true, I ask, “what if the Ie had journalists that were directed to write reports, with deadlines, and had to find and interview analysts across the Ie, DoD, legal, state, local, academic, and others areas in order to more fully cover a topic? That would leave more emphasis properly placed on analysts to do their job of maintaining facts and forming and defending positions, rather then writing reports and adding to the noise. In addition to this, it would tend to have a positive influence on relationships between analysts an their willingness to collaborate when they start to see the influence that their argument held up, or not, who agreed with them, who did not and why. All these are good things in my mind and might alleviate some of the agency vs agency stuff that seems to eat away at the collective effort.
Now I believe that we have the tools to author joint products, like Living Intelligence, Intellipublia, and more, but how we would task this group of Ie level Journalists is another matter to consider. I am less certain about a common tasking system that would allow the head of the journalists to direct efforts against stories in a way that would meet intelligence requirements of all those that are submitting Intelligence requirements to different requirements processes. That being said, if we were going to make this group of journalists, then we could ptobably set up some folks that know how to direct this kind of activity and are familiar with the groups out there, and the general types of requirements that are needed such that they could direct journalists to meet them.

So in short, there would be analysts, sme’s and journalists. A directing mechanism for the journalists that takes input from key stakeholders, and a truly joint product that woul:d have the names of the analysts and agencies that contributed to them, thereby reducing the number of redundant reports that are created, and fostering the kind of collaboration and solid products that I believe we should be creating as a community.
I would think that creating this group and giving them the charter and responsibilities to do this job would be more likely than analysts all across the community getting reallylgood at collaborating and sharing in that way that we have hoped. Again, the difference in motivation and bias may be slowing or preventing the achievement of the environment we are trying to create.

Cheers!
Please let me know what you think.
Lance.

Some responses from another area are below.

(Reader 1) I read a lot of topical blogs written by journalists, and I have say for many of them, I hold their analysis in higher esteem
than much of what I read in finished intelligence. Now, journalists are just as capable of having biases, but most of
them state it up front, or you can tell it by whom they are writing for. I think professional journalists are better at writing a tight storyline, keeping to the narrative, and in many cases offer interesting insights that many others would miss.

(Reader 2) I have to respectfully disagree. Some contemporary journalists seem to publish opinion pieces under the heading of articles. I have seen instances that present as the journalist going into the process of reporting with their own agenda instead of being objective. In this age of computers and instant gratification it also seems in trying to reduce the reporting to the short time span it’s presented in, the message is often distorted or lost entirely. The dearth of print media and conglomeration of newspapers further reduces the impact of responsible journalism. I am not saying this is necessarily the fault of the journalist, it’s the just the system they are forced to operate within. Don’t get me wrong, there are responsible journalists out there but there are many sloppy ones as well.
So too is the analyst field. But this is a problem of our own making. For too many years the attitude of “knowledge is
power” and each agency’s artificial stovepiping discouraged the sharing of information. This attitude became ingrained
and as we all know it is hard to change as human nature, as well as corporate mindset attests. As a result the problem
becomes not so much as how to share but in finding out who is working on what. Reinventing the wheel became
commonplace,. Then too the lack of social media skills among the older generation of analysts further compounded the
porblem.
But programs like this blog for example s~gnal a change in direction. Education is the key. The newer analysts are more
comfortable using social media in their daily life so it translates easily into their analytical practices. Now it is a matter of
“advertising” who is doing what in the various agencies so that connections can be made between analysts. In addition, no
competent analyst should be producing arliyfinished intelligence without it being vetted. This is just common sense in my opinion. Are we going to have an opinio~? Yes. Are we going to possibly resent criticism? Again, yes. This is human
nature. I truly believe the vast majority0tanalysts today get the fact that producing for production’s sake is not
appropriate. We hopefully realize each intlividual is ultimately responsible for each and every call and their decision could ultimately affect the very lives of the indiliduals using it. I would hope they would do their very best and ensure it is the most accurate infonnationlanalysis possib e. Bottom line if you are putting your name to it, don’t you want to make sure you get it right?

(Reader 3) Interesting thoughts, Lance.
Reminds me of the mix between bloggers and what they call “Developer Advocates” or what not in the software world. As
this whole Internet-hosted, “cloud” and Iaas/Paas/Saas thing has taken off, there’s a lot more direct interaction between a
company and an individual delevoper.
So where you previously had tech Journalists reporting at magazines like Dr. Dobbs, and then tech bloggers like
TechCrunch, ReadWriteWeb, etc, you nor also have people working at cloud hosting companies that write articles or
screencasts on what their company provides.
I guess they are technically marketing/sales folks, but they are similar to a cross between a journalist and an analyst in that they might not be a SME, but they aren’t teallY just offering quick/shallow news articles, either.
Personally, from my limited viewpoint, I itill don’t really care for this idea of news-reporting style analysis, where an
article comes, goes and never gets update1 or pointed to again and that’s where LivingJntcJ really seems like a great idea.
But I can definitely see the need for someone who acts a a go-between for analysts who are too busy/too involved to sit
and chat it out with others every day, or ate naturally better at quiet thinking and research, versus interviewing or
collaborating across issues.
That’s why I dropped out of my own journalism ideals back in college – trying to get people to talk to me was a pain (and
scared me), whereas messing with a computer was a whole lot easier.

(Reader 4) +1 to james. Saying analysts need to be more like journalists in order to incorporate more balance is like saying chocolate needs to be more like vanilla in order to be more chocolatey.

(Reader 5) It is my belief that most analysts are pret deep in terms of knowledge with respect to the subject matte’ they write on” Man, I would love to work where you work.

My Podcast Process and Thoughts

Posted in Web2.0 Productivity with tags , , , , , , on March 6, 2011 by Lance Strzok

So here are some lessons learned from my recent podcast.

Content gathering
– Gathered from various sources, and be sure to get the source information for each part
* Official Emails
* Company portal highlights
* Interviews with people
* Newsletters (internal and external)
* Questions
* Ask for content from Social Media sources
* Send email request for input with links to pages
* Make some phone calls to personally invite someone to interview with you
* RSS feed for items that matter to everyone
– I put all of the content into a shownotes page on a wiki for the production end of things and invite (encourage) others to begin to edit there, otherwise I just put the content in myself from email, or whatever source they are sending it to me from
– After writing it all down and smoothing it over for speaking it aloud, I am ready to record
– Create a section at the beginning in which you mention the contents of the episode, and the date so that listeners may choose to listen or skip that particular podcast (thank you readers for that feedback)

Recording
– I started to record them as mp3 files with a Zoom H1 hand held recorder, but now under lessons learned, I will save them as wave files since the Levelator tool provided by the Conversations Network takes that as an input later in the process and I want to reduce the number of conversions (which only add noise as evidenced in the first podcast). I use the 48khz sample rate with 16 bit because it is the best that can be converted by the Levelator or converted to mp3. I also use the autolevel setting on the back, as well as the low cut on.

During Recording
– Have a glass of something you like to drink near by
– I don’t mind making a long recording, just make sure that if you make a mistake while recording, to pause, regain composure, pick the spot you wan to redo, and after a noticeably long enough time start the section over. In this way when editing, you will clearly see a long pause that will indicate the location of the edit. (Thanks to that tip from Robert and Tiffany Rapplean from their podcast – Intellectual Icebergs)
– Find a quite place, and give some thought to the room you are in with regard to sound waves and how they will arrive at the microphone as well as materials that will absorb sound

Save Raw Recording
– Save the raw recording before doing anything else and store in a folder

Levelator
– You can use the Levelator tool to even out the different levels in the sound file and bring it to a consistent output sound level so that episodes are generally equal from show to show
Editing
– I use Audacity to Edit the wave files, (again, switching to wave files to reduce the number of conversions that reduce sound quality)
– Edit out the bad sections and shorten up long pauses
– Add intro and extro music or words as desired
– Insert commercials as desired (I don’t do this – yet)
– There are other resources within Audacity to do more editing
– Save this file as an edited wave file so that if you have to add sections (insert additional entries), that will be easy


Convert
– Now using Audacity export the edited file as an mp3 file for upload to the server

Last Listen
– Give the show the last listen while following along with the shownotes
– Make sure all the content that is in the show notes is represented (I forgot a section in my first podcast)
– Make time hacks in the shownotes so that if people want to skip to a section, they can do so

Upload Link and Market
– Upload the file to the host server
– Copy the show notes and time hacks from the wiki page where they were created into a blog post and email for linking and feedback
– Make links wherever possible in the shownotes to sources and important nouns
– Link to the podcast, shownotes, and feedback from various locations
– Include a link to subscribe to the podcast or updates when possible
– Post the blog, and verify that all the links work – if not, fix them
– Let your users know that there is a new podcast available with a link to automatically download the mp3 file

– email the podcast distro list you may have and include in the email the time hacks and topics for the show

Follow up on Feedback
– Make sure you stay engaged and follow up on feedback that comes back to you on the blog

If you have additional thoughts on improving this process, please let me know, I aim to make it better as I go, and thanks for your thoughts in advance.