(Not) Lost in Translation

Today I was given a fine compliment and told that I was a translator. After writing about having to "traverse the stack" and Business Intelligence as a bad word it felt good to hear evidence that bridging the gap between the technical world and the healthcare world is doable by mere humans. Like many things in our culture this talent isn't nurtured early enough and it seems that the school of hard knocks is the primary teacher. For example, how many computer science programs emphasize non-technical writing, non-academic presentation and business skills? It's been a while since I got my Bachelors Degree but I don't see the core of these programs doing a good job in this area.

There are a few ways to try and get there faster. A double major in business management, communications or an MBA. In fact many of the best and most effective translators I know got their MBAs early in their careers and I admire their grace. In a pinch though an organization can help this happen by cultivating these skills internally, not slaying people for making mistakes and committing to the development of their people. These things will evolve into part of a hard-wired culture of learning and culture definitely eats strategy for lunch!

Back to sharpening the saw...

Why Business Intelligence is a Bad Word

We're off and running with discovery (in depth evaluation) of an initiative that could be termed Business Intelligence or Analytics but we aren't going to call it that. Business Intelligence has become a bad word and in the never ending quest to support the needs of our hospital administrators we can't afford bad words. The challenge of communication between the clinical and IT communities is much too important. I was once told by an ex-boss that "why?" is my favorite question. Actually "how?" is my favorite. I like to understand things sooooo....

How is it that Business Intelligence became a bad word? In looking back I think there have been a variety of factors.

• Business Intelligence (BI) is a technology label and technology labels are usually dreamt up by salespeople to make product offerings sound cool. Over time best practices cause the labels to refer to some sort of architecture or other anatomy that is recognizable. The label endures however and lacking the newly evolved context suffers.
• Recently in reading an enterprise architecture text the difference between deploying IT solutions vs IT capabilities was highlighted. Deploying IT capabilities is a more forward looking and strategic endeavor. The difference however isn't always clear and when (as I have on occasion) heard IT folks talk about deploying a "robust business intelligence application" the wrong picture emerges. BI is an IT capability and should be treated strategically. Individual projects should focus on solving problems.
• When working with business leaders on developing IT capabilities it's extremely easy to fall into the "solution looking for a problem" trap. Unless the value of the capability can be defined in terms of business value or mitigation of risk it's like telling a joke and forgetting the punchline.

So again the challenge of communication between the clinical and IT world highlights itself. So if you want to start being pro-active and develop IT capabilities you best watch your language.