A Passing Thought About Knowledge Management Systems

I have been spending time this afternoon working on my UMUC Contemporary Topics in Informatics class. One of the topics my students have been commenting on relates to information sharing. One of the questions I have posed is why are some information sharing efforts successful and some failures.

A student wrote:

“Who has time to share information? Codifying one’s knowledge can be a very time intensive task. While many people share their knowledge via blogs, wiki’s and other such tools, getting individuals who are already overburdened to do this can be a challenge.  I’ve seen organizations try to force its employees to do this kind of thing resulting in very shallow products.”

From this conversation, I started to consider how this relates to some of the work my company, Powertek Corporation, www.powertekcorporation.com, has been doing with knowledge management. It seemed to me that in the end in the simplest sense knowledge management like information sharing solutions are all built upon the foundation of tagging information in a fashion that allows retrieval.

In the interactions I have had with Jeff Jonas, http://jeffjonas.typepad.com/, one of the smartest people I have met who studies all of this, he has impressed on me the importance of tagging information when it is ingested. Doing so afterwards is something liking trying to add the Dewey Decimal coding to a book after you put it on the shelf in the library. It would take so long to find the untagged books you typically wouldn’t get around to it.

If I can digress for a moment, and since this is my blog I guess I can write anything I want anyway I want to, while I was at the Department of Transportation and while watching what Vivek Kundra is trying to do with dashboards, I have pondered a similar issue – what tends to make some performance measurement systems and dashboards successful and some not.

I have come to believe that those dashboards whose metrics are automatically generated by the performance of the action being measured have a greater chance of surviving over time. The reason is that whenever an intermediate step is needed to generate the dashboard entries, organizations have many reasons to reassign or eliminate altogether the resources used to perform the intermediate step. Thus useful and even pretty successful measurement systems often last only as long as their sponsor stays and stays engaged.

So the common thread would be that the ‘sharing’ and ingesting into the knowledge management system, that is the tagging, should be accomplished when the information is created.

Looking specifically at knowledge management implementations that I am familiar with, most do the knowledge management part after, and often long after, the knowledge creation. The question then becomes whether it is necessary, or practical, to move tagging and ingesting to the actual knowledge creation.

I am sure experts in the field already know the answer to these questions, but if so, they often don’t seem to have sufficient impact on the large number of unsuccessful knowledge management implementations.

Writing Winning Proposals

This morning I was discussing with some partners how to write winning proposals.

I seemed to remember that I had talked before on this blog about proposals but upon searching around, found the only other time was in fact my first post where I provided anecdotes but not brilliant insight, https://www.ourownlittlecorner.com/2009/06/08/first-post/.

So, while recognizing that I am now giving away the secrets I have learned over my many (many) years of working on proposals, here are the rules I follow:

  • Answer yes. Engineers take multiple pages to respond with what is functionally ‘maybe’.
  • Answer with what the Government wants, not what they are asking for. Requires knowledge and courage.
  • Prove it. “No, this time I REALLY mean it.” is not a proof.

There you have it. Follow the three rules and you win, do not and you lose. Well, also bid low. That helps also.

On Leadership

I often refer to Leadership as being the ability to get people to do things when you are not in the room.

For most of my professional career I did not particularly think about the differences between management and leadership. I was not in a position where it mattered particularly; I was always ‘in the room’.

Generally I was either managing a single large program generally customer facing or managing people who themselves were managing single large programs. The way one achieved results was to use the importance of the program, either due to the importance of the customer or the size of the program, to leverage the rest of the organization I was working for.

“You need to listen to what I am asking”, a typical interaction would occur, “This is worth $100 million to us this year.” Few had the nerve to say no at that point.

When the projects were small it generally meant the other part of the conversation WOULD have the nerve to say no.

As the years passed, I was given additional responsibilities and had to learn to prioritize and help my staff prioritize better, but fundamentally had the same kinds of responsibilities.

In early 2006, I was appointed the CIO for the US Department of Transportation. Suddenly I was in a situation where I had hundreds of people reporting to me directly and thousands who I had at least nominal impact on through the myriad policy responsibilities that a Departmental CIO was responsible for.

I had sort of very faint dotted line relationships to all of the DOT agency CIO’s, created by the Clinger-Cohen Act, which established what I refer to as the negative authorities of CIO’s. By negative authorities I mean the Act gave CIO’s the authority to prevent results, for example not agreeing to a budget submission, but much less power to implement results, for example, without Department or Agency specific legislation or implementing authority, a CIO couldn’t consolidate or modify the resulting budget.

My ability to get things done was almost completely dependent, not on managing a project, but on providing leadership, whatever that was, to get people to do what I wanted without the direct ability to tell them to do it.

Now that I serve as the Chief Operating Officer at Powertek Corporation, www.powertekcorporation.com, while a bit smaller than the Department of Transportation, I still have the same issue of having indirect impact.

Having thought about this a lot over the last almost five years, I have come to five thoughts that provide me with some direction as to how be a good leader, or being perhaps a bit more realistic, to be as good a leader as I can be.

THE NARRATIVE. In my opinion the best leaders are storytellers. They explain how they want people to behave and what values are important to them by telling stories of behavior illustrating those values and actions. It amazes me how often I find out that the stories I have told are repeated to others. Amazed and pleased.

If you have read biographies of President Lincoln you will read how many anecdotes he told.

Even people who do not consciously or explicitly do this, they still are conveying a narrative about themselves and what they expect from others. How often they talk about their family, what they wear, the jokes they tell (or don’t tell), how they deal with people, whether they raise their voice or not, and so on.

NIGHT AND DAY. If you are in a leadership position everything you do and how you do it is watched and analyzed. It all becomes part of that narrative thing, whether you like it to or not or intend it to or not.

My father-in-law, a wonderful person I have been very lucky to get to know, used to tell me when he was President of a manufacturing company in Michigan, that when he was feeling sick and acted that way around the office, this impacted negatively the work of everyone at the plant. At first this surprised him, but over time he came to understand how important how he acted every day was.

About a year after I started at DOT, a young woman who worked for me asked for a meeting. When she came in she told me that she had heard that I was in a good mood and thus wanted to go over some difficult issues that she needed to be resolved. I reflected on the fact that never before in my business life had anyone cared about what mood I was in, or generally noticed.

I reached out to a wonderful person, Shelley Metzenbaum, who is now an appointee within OMB, who gave me advice about being a political appointee at DOT. Shelley told me “Political appointees are unable to talk in a whisper.” Wise advice. Over time I have come to recognize that this advice is true for all people in very senior positions in any organization.

BE TRUE TO YOUR SCHOOL. My final comment about narratives is to emphasize that the most important aspect of the narrative is to be true to who you are. Over time people can tell if you aren’t. The rare exceptions being if you are an extraordinary actor or a professional politician. When people detect a false note, everything else you say or do will be much less likely to be paid attention to.

I have read many books about leadership which provide lots of advice on how to act. All the advice in the world is of limited value if it is inconsistent with your nature. Understand yourself and go with that.

ROADRUNNER VERSUS COYOTE. I tell people who work for me that sometimes you have to go running off the cliff without knowing if you are the Roadrunner or the Coyote, http://www.youtube.com/watch?v=fUq9hynzCVo, and not knowing how far down the ground is.

If you want people to attempt great things and run off cliffs for you, you need to be there to catch them and not blame them for trying. Toleration for the occasional failure is a characteristic to me of great leadership.

EMPATHY, NOT SYMPATHY. I read somewhere that leaders needed to show empathy, but not necessarily sympathy.

What I take that to mean is that it is important to understand the motivations of the people who work for you. You want to use those motivations to support your goals. You double the level of energy by having people working toward your objectives both to support you and to achieve their own goals.

At the same time, you have obligations to the entire organization, not just one person within it. Sometimes you are able to scratch individual itches, but often you cannot or at least not in the way that the individual might like.

TREAT PEOPLE WITH RESPECT. I say frequently that people will never act better than they are treated.

If you treat them poorly, not sharing information or objectives, just ordering them around, not empowering them in any fashion, most will act just like they are treated and no more. To have a successful organization you need people to take ownership of their responsibilities.

IN SUMMARY. So there you have it my five rules of leadership, reworded slightly:

  • Understand and articulate a coherent narrative that explains to everyone what kind of person you are and what kind of organization you want to lead
  • Recognize that everything you do regardless of the setting impacts on that narrative
  • Be authentic, people will see through a false story over time
  • Tolerate risk taking and its inevitable partner, the occasional failure
  • Treat everyone with respect

I divide leaders into two types, those that want to win and those that want to avoid losing. These rules will help you be the first type, the winners, who are much more enjoyable to be around and build the best organizations.

Four Negative Rules of Life

In todays complex world it seems that many of us are looking for structure and guidance on how to make decisions.

Years ago I remember reading (or hearing) about four negative rules which if in their explicit form or derived implication deal with all decisions that we might face.

I hope everyone enjoys my contribution to the discussion, in no particular order of importance:

*    Never get involved with someone who has more problems than you do

*    Never help a friend move

*    Never order the seafood combination

*    Never play cards with someone named Doc

There you have it, follow these rules and your life is guaranteed to be improved.

I leave as a homework assignment to further interpret the broader meanings of each of these.

WikiLeaks

Since the latest set of releases associated with US diplomacy through WikiLeaks there has been endless commentary on all aspects of the leaks. I have read through many of the comments and columns and been thinking about whether I had any particularly new insights to offer.

My conclusion is that I do not and therefore wanted to reuse a few old ones.

While there will be a lot of closing the barn door after this particular horse has left action steps, in my opinion the bigger message is to reinforce the premise that the battle between information protection and information sharing is over and done with. Information protection has lost. I remain convinced that security planning focused purely on protection, in particular focusing on periphery protection, is a waste of time and money.

The underlying reason remains that the value of sharing information, or conversely the penalty of not sharing information, is so great for any organization of any type today that this need will drive decision making. Unless an organization is prepared to make the kind of investments that the Government does in setting up a structured set of security levels, e.g. confidential, secret, top secret, and so on, then it not possible to cause corporate culture to both share and protect very well at the same time. And even the Government security apparatus with its enormous associated investments leaks information, WikiLeaks being only the most recent example.

If I ran the security world I would focus on the following:

  • Security hygiene
    • Achieving situational awareness
    • Implementing security policies associated with situational awareness, see my post https://www.ourownlittlecorner.com/2010/12/18/brief-thoughts-on-security-and-other-it-policies/
    • Identify the data I really want to protect and focus only on that limited data, if more than ‘limited’ rethink what you want to protect
    • Create a strategy that takes into account that no individual component of your system is impenetrable
      • If concerned about availability – consider a biological construct with multiple copies of your applications and data available; e.g. the human body works fine, mostly, even with viruses all over the place
      • If concerned about penetration – consider increasing your OODA loop speed, observe-orient-decide-act, http://en.wikipedia.org/wiki/OODA_loop

Run Lola Run, Brief Comments

Finished Run Lola Run, http://www.rottentomatoes.com/m/run_lola_run/, Lola Rennt (literally Lola runs).

I guess this is one of those films I had to see in the theatre to really appreciate rather than my usual 20-30 minutes at a time on the elliptical walker down in the basement.

Got high marks on Rotten Tomatoes, I remember the noise when it first came out. I had some difficulty getting involved with a young woman who dates a guy who considers doing drug deals a step up, has to beg money from her banker-father who is having an affair and has evidently gotten a member of the Board of Directors pregnant, and who has what seems to be Raggedy Ann orange-red hair. Well, I did like the hair.

I guess it was considered clever integrating a bit of animation into the middle of the film and having repetitions of the plot with different endings, each cycle punctuated with the young woman shouting loud and high enough to break glass. There was even a tiny bit of Donny Darko, with at least the young woman seemingly remembering what happened from the previous repetitions.

I found it uninvolving and thought the boyfriend should have ended up in jail. If one of my daughters showed up with that twit, it would make me very unhappy.

Thoughts on Tron Legacy

I sometimes reserve weekend and/or holiday mornings for seeing movies my wife, Ellen, will not see with me. There is no particular rhyme or reason as to which movies she is interested in going with me to see and those not, with the one mild exception perhaps of quality – the lower the quality the more likely she won’t go. Thematically, other than that quality thing, films that tend to be science fiction and/or contain violence of some sort are often on the do not go with Dan list.

The movie theatre that starts showing movies earliest, at least the one that is close to us, is the AMC Movie theatres at Tysons Corners. Since they also have an IMAX theatre, they are my most likely to be the go-to-a-movie-theatre-by-myself location.

Anyway, that is why I found myself, by myself, at Tysons, for the 10am showing of Tron Legacy, http://www.rottentomatoes.com/m/10011582-TRON_legacy/, in 3D IMAX, Christmas morning.

I suspect that anyone who is particularly likely to see Tron has already done so. And since I don’t really do movie reviews, I will note that if I accidently write a spoiler or two I apologize in advance for doing so.

For those who haven’t seen Tron Legacy, I will say that having only read about, but not seen, the original, http://www.rottentomatoes.com/m/tron/, I suspect I didn’t really understand all of the references.

My quick summary is that if you like relatively mindless, loud, cgi-intensive movies Tron Legacy provides a few hours of distraction. Though, I kept thinking I was watching a version of The Big Lebowski, http://www.rottentomatoes.com/m/big_lebowski/,  versus the Super Mario Brothers.

So Jeff Bridges in the original evidently went into a digital world, created a copy of himself called CLU which stands for three words that being with C-L-U, and a helper called Tron. Whatever happened in that original one, he never returns to ‘real life’. I could call real life, off-grid but evidently you can be on the grid inside the digital world or off the grid, so we will call the outside world off-off-grid.

The movie starts off-off-grid, where Bridges son has grown up and has lost control of the company that Bridges owned/founded (whatever) and which the son, Sam, is the largest shareholder in. The company is called Encom, which is an interesting name though the original movie was released years before the Enron scandal.

The obligatory Hollywood poke at everything capitalistic, except that is in Hollywood, is gotten over with at the beginning of the movie when it is announced that Encom is releasing its newest, most secure operating system called version 12 (I guess five is better than seven?). When the CEO is asked what has been changed about the new operating system, the answer is we put the number 12 on the box. There is lamenting about how the operating system should be open and free to the public; coincidentally Sam has copied and released the operating system to the world during the course of this conversation. My supposition is that Encom at this point represented Microsoft, which it seemed to me hasn’t been doing well enough these days to be represented as such an evil organization.

In any event, after a while, Sam through the help of an old friend of his father, imported from the original Tron movie, played by Bruce Boxleitner, who I liked better in Babylon V, enters the grid, where he wanders from the grid to off-grid and back on the grid. I cannot summarize, or in fact even afterwards entirely understand the plot from that point until the end of the movie.

While in the grid, Sam meets Clu who evidently is an actor with Jeff Bridges face looking like it did in the original film, which was a bit creepy and his actual father, played by Jeff Bridges with his current face, who as I mentioned earlier is channeling The Dude. I noticed that in the key age old question as to whether the male hero should end up with the blonde, Beau Garnett in this case, or the brunette, Olivia Wilde, Tron Legacy came down on the side of the brunette. This is always a key issue in fanboy movies.

My favorite performer was Michael Sheen who played a nightclub owner pretending to be Martin Short. Michael Sheen is wonderful in every movie I have ever seen him. Even when my younger daughter, forced me, to see Twilight New Moon, he represented the one part, and I emphasize in that case, the only part of the movie I found more than drivel.  Well, in the interests of honest disclosure the reality is that I wasn’t forced, I went because of my endless need I have to spend even a few minutes with either or both my daughters; though if asked to go to another Twilight movie would be the ultimate test of that need.

In any event, another movie checked off. I suspect if it stays in movie theatres long enough, my next by-myself movie will be Rare Exports, http://www.rottentomatoes.com/m/rare_exports/.

BTW, does anyone know why the Tysons in Tysons Corners has an s and no apostrophe?

Brief Thoughts On Security and Other IT Policies

I am finishing up grading final papers for my Syracuse University class on security policy.

Each semester I find I learn a great deal from reading the papers and interacting with the students about them.

I have drawn three conclusions about policy creation from my past experience at the Department of Transportation, modified slightly from the current set of papers:

(1) Policies whose impact cannot be measured cannot be enforced.

(2) Measurements which are not created in some kind of automated fashion will not persist.

(3) Measurements which are not made visible don’t exist.

Signature Lines on Email

Apropos of nothing in particular and to take a brief break from grading research papers from my University of Maryland class I teach, I was again reminded of one of the problems I have with signature lines from emails (have I mentioned this before?).

Many people have a permanent signature that has some generic sign-off like “Gratefully yours” or “Many thanks” or  “Respectfully yours” or something like that and then their first name on the final line.

However, there are tons of emails where this signature ends up being jarring.

“Dear Second Rate Person,

You have been unreasonable for ever. You don’t return calls, you don’t respond to emails.

Your company provides lousy customer service.

Your children are ugly.

I can’t even believe you found someone willing to mate with you for money let alone be a fellow parent.

Respectfully yours,

– Me”

And such is the electronic world we live in today.

Cloud Computing Thoughts – Part II

In my previous entry regarding Cloud Computing, I discussed briefly one of the major reasons why organizations are turning to the cloud, saving costs. I pointed out some of the issues involved in achievable that goal.

While I also consider the possibility of cost savings associated with Cloud Computing important, I believe other implications are more important in the long-term. I discuss a second one today, and will touch on two more in the next few blog entries.

When we start thinking about moving applications to the cloud it leads us to reconsider how we develop applications. This change in thinking has, as a foundation, the move to object oriented design, and has been encouraged by  a change in conceptual ownership. I talk about both of these in this post. Continue reading “Cloud Computing Thoughts – Part II”