Information: Lifeblood of Enterprises (2)

Yesterday, I blogged about the statement: Information is the lifeblood of enterprises.29-bloodflow

Today I'd like to use this metaphor to explain why structured and unstructured information should be managed under architecture. Or in an integral way.

I've been thinking and posting about this topic for some time now - it's basically the core of my job. To point to a few posts. Just recently I posted about 'PLM (product lifecycle management) and enterprise 2.0'. And longer ago about managing unstructured and structured information under architecture.

As I've said before: I distinguish between unstructured and structured information in organizations. But they are not distinct. Regrettably this is common practice in most companies. You have people working on Product Lifecycle Management and Enterprise Resource Planning on the one hand. On other you have those that are implementing the intranet, rolling out wiki's and blogs, building document management systems and helping employees use their email effectively. These are two distinct ventures, that seem to have little or no relatedness.

And it's true when you look at the kind of people working in both areas, they are as different as night and day. The first group despises and wants nothing to do with the other. Most knowledge workers hate working in the formal product management and resource planning tools. They're to strict, non-creative, etc. On the other hand the guys and gals that own the formal tools complain that everyone is creating information which is not shared and stored in the 'right' tools.

So, you have two camps. One touts: all should be done in the PLM or ERP system. The others say: throw away the expensive, formal systems, let's just use the 'good' stuff like wiki's, blogs, etc.

Although I relate best to the second group... I don't think one or the other is right. To explain my approach/proposal, let's get back to the thesis in the title of this post: 'Information is Lifeblood of the Enterprise'.

How does blood flow through our body? It 'uses' arteries, veins, smaller and larger blood vessels to transport a.o. oxygen to the right places. Let's say the formal systems, like Product Lifecycle Management and Enterprise Resource Planning tools are the main arteries in the organization. They (should) support the main business processes in the best possible way. But everyone knows these business processes don't summarize the company as a whole. Lot's more stuff is going on in the company. Less formal stuff. People talking to each other, talking to customers, small ideas that are documented and built upon, reports are written to fuse decision making, etc. Oh, yes, these all (should) relate to the main business processes somehow and someday. As the micro and small blood vessels connect to the main arteries. But most of the work starts at the knowledge worker's desk. In his inbox, in his Word document. Typically a very informal process, which seems inferior to the main, formal process. But it's not, relating to blood vessels. If we would cut away the smaller vessels, the whole production and transportation of oxygen will stop!

For this reason, I find it important to define an information management program comprising unstructured and structured information without telling 'unstructured' to become 'structured' or the other way around. Maybe this will mean that wiki's and blogs will become more leading in companies, than they have before. Maybe this will mean that the workflow and change functionality of PLM and ERP tooling will be used to relate wiki pages and blog posts together into a workflow as I proposed commenting on John Tropea's post about Workflow 2.0.

Does this make sense? Does this metaphor help explain the distinction and relatedness between structured and unstructured information? I'd love to hear your thoughts.

---

If You Read This and Like It, Tweet This to your Followers:
Information: Lifeblood of Enterprises (2) http://twurl.nl/6pyk4h

Comments

  1. UnknownApril 9, 2009 at 9:28 AM

    Thanks Clark! (or Joannah?)

    ReplyDelete
  2. Toronto CondosMay 27, 2009 at 1:05 PM

    Nice Info. I have visted first time on this blog. It seems to be interesting and informative.

    ReplyDelete

Post a Comment

Please leave a comment! Just log in using one of the formats and if you want me to get back to you. Otherwise comment anonymously.

Popular posts

Keep the Intranet Small

Image
This tweet by Jonathan Phillips ( @digitaljonathan ) triggered to finalize this post, that's been burning in my draft box. I've always been intrigued by how unsuccessful many intranets are. And there are all kinds of good reasons for intranet failure. One of the things that is hardly ever mentioned is: Shouldn't the intranet be smaller? Usually intranets are huge. Lots and lots of pages with lots and lots of content. With complex navigation. The intranet  evaluation surveys almost always show employees only use the news page and people finder. But still we build and maintain nice big intranets. Not only stats point to smaller intranets. There are others reasons as well. I came up with a few. If you have more, just leave a comment. Here's my list: -            user requirements: users don't require large intranet -            search/navigation: searching and navigating a small intranet is easier than in a large intranet -            mobile: the content of the
Read more

Enterprise 2.0 Research

Image
There's not too much fundamental research on Enterprise 2.0. Deloitte recently published interesting research done on enterprise 2.0 implementations and their return-on-investment. In the EU research has also done as well. Study is being done for the European Commission and it was carried out by Tech4i2, IDC and Headshift. What was the goal of the study? Goals of the study To provide a clear definition of Enterprise 2.0 is, describe the market and the positioning of EU industry, also in comparison with US and Asia; To analyze the take-up of Enterprise 2.0, the organizational requirements, and the role on the transition to a knowledge based low-carbon economy; To collect evidence on its macro-economic impact, as a market opportunity for the European Software industry and as a productivity tool for European business; To identify and analyse both the direct and contextual challenges, including the need for Next Generation Access and the legal barriers; To analyse an
Read more

Innovation in Turbulent Times

Image
I love reading articles about innovation. And every now and then you read one that is very interesting. "Innovation in Turbulent Times" by Rigby, Gruver, Allen (in HBR, June 2009) is one of them. This article takes fashion companies as an example for continuous, year-by-year innovation. And how successful fashion companies are usually led by two people: a left-brainer and a right-brainer. "If you don't have highly creative people in positions of real authority, you won't get innovation. Most companies in other industries ignore this lesson." They extend this to show that successful non-fashion companies have the same kind of leadership. And this kind of leadership is usually also characterized by a long-term relationship. I think this concept can also be extended to teams and projects as well. More often than not, people are good at one or the other: thinking up great concepts or ideas, or, making them. In teams and projects we can learn from this as
Read more