Increasing Jointness and Reducing Duplication in DoD Intelligence

Today I’m publishing an important guest-essay, with a brief introduction.  Last month the Wall Street Journal published a 12-part online series about college graduates and their paths to success, featuring surveys and input from job recruiters. One thing caught my eye, at least when blogged by an acquaintance, Prof. Kristan Wheaton of the Mercyhurst College Institute Of Intelligence Studies. The WSJ’s study included a look at recent graduates’ job satisfaction in their new careers, and as Prof. Wheaton strikingly put it in his own blogpost:

“Intelligence Analysts are Insanely Happy.” 

I’m pretty sure that’s not really true by and large; Prof. Wheaton seems slightly dubious as well. Many readers of this blog are intelligence analysts themselves, so I’d love to hear from you (in comments or email) about your degree of giddyness….

We all know that the intelligence-analysis field as currently practiced in U.S. agencies bears many burdens weighing heavily on job satisfaction, and unfortunately weighing on successful performance.  Our youngest and our most experienced intelligence analysts have been battling those burdens. 

One analyst has now put constructive thoughts on paper, most immediately in response to a call by Defense Secretary Bob Gates asking DoD military and civilian employees to submit their ideas to save money, avoid cost, reduce cycle time and increase the agility of the department (see more about the challenge here).  

Enabling Eureka via Citeability

The story of Archimedes resonates with everyone, because we all regularly feel that rush of excitement that he famously felt when discovering the principle of water displacement: “Eureka!” he shouted, “I have found it!”

Whether it’s car keys or the perfect birthday present for a loved one, we know that feeling. But how often do you feel like shouting “Eureka” when you’re surfing the web looking for a particular piece of government information?

Departure of the Pentagon CISO

I’ve had the good fortune to work with talented folks in my (short) time in Washington, since moving back East in 2002, particularly in the Intelligence Community and Department of Defense.  And one such fellow at DoD has been Bob Lentz, the outgoing deputy assistant secretary of Defense for information and identity assurance – the Chief Information Assurance Officer and equivalent to a private-sector CISO.

I gave an interview this afternoon to Federal News Radio (AM 1500 in the DC area, worldwide at www.FederalNewsRadio.com), on Bob’s tenure, and what will come next for DoD in the wake of his departure. You can read the news story about the interview here, or listen to the entire 15-minute interview as an mp3:

Shepherd interview on Federal News Radio, 10/13/2009

How to Run a State-of-the-Art Technology Program – Quietly

FACT: In the new movie “Iron Man,” defense-contracting billionaire and engineering genius Tony Stark (played by Robert Downey Jr.) designs and builds a suit capable of individual flight (highly engineered control surfaces powered by an “arc-reactor” – it is Hollywood after all). During his first test flight, zooming straight up from Malibu and stressing the system to its max, he asks his onboard computer, “What’s the altitude record for the SR-71?” His computer responds back, “85,000 feet,” whereupon he zooms past that ceiling.

ANALYSIS: Funny moment, and excellent movie.  In its honor, below I’m going to give you access to a remarkable, recently declassified document describing one of America’s boldest Cold War technical achievements.  If you’ve ever run (or wanted to run) a high-tech company or program, like Tony Stark in the movie, you’ll appreciate the startling scope of the work – and if you’ve recently worked in DoD or the Intelligence Community you’ll marvel at how they did it “in the good old days.”

Opening Doors to Interoperability

I had to write a freshman term paper on Immanuel Kant, and chose as a topic his role in sparking the German Enlightenment, from which I at least learned the word Aufklarung … which surprisingly doesn’t come up much in normal conversation, even when I’m in Germany. But I’ve been thinking about that movement and its ramifications quite a bit, because of the ongoing technology enlightenment driven by “open-source” approaches.

When I announced I was joining Microsoft, several of my friends in the open-source-software “movement” raised their eyebrows and ribbed me for joining the dark side… although the brighter ones also pointed out several important trends and markers through 2006 and 2007, changes in Microsoft behavior and approach which appeared to signal that the company was tacking in a much more open direction. Ray Ozzie’s joining of the company, and his announced projects, were taken as significant, along with several software launches (both in the Live world and elsewhere) with fundamentally open foundations.

Today the company is making public what Steve Ballmer and Ray Ozzie are calling “important changes to our technology and business practices that will enhance the interoperability of our products and expand the technical information we share with developers, partners, customers, and competitors.” All to the good, including more comprehensive information about the new “Interoperability by Design” approach.