Now beeing back from my recent voyage to the high regions of big visions, I deliberatly came down a bit to get a closer view of the land I glanced from high above and naturally enough besides the natives to whom I wish to bring enlighenment, there already are some missionaries abroad, but I didn’t see no chapels let alone any cathedral yet. Unfortunatly but not unexpectedly, there are also no paths or roads yet and my ever so knowing google maps would refuse to come up with a route from my current position to the new land of glory and instead presented me only with a general direction where to head to.
But lets stop this metaphorical nonsense.
I did a little research and looked for people who also work on this topic (which was quite clumsy work, not really having defined the topic itself so far) and being not that successful, I called up a friend of mine, who I really hope will get involved also in the future. I then quite ruthless (mis)used him and my wive by confronting them with masses of unsorted thoughts for a couple of hours – which in my experience is a good way to get things sorted out. I was not very successful in communicating this vision of mine, but I think I could at least light a spark which is the most important thing to get things moving. But anyway. Let’s see, if now I can put down some of the thoughts on the topic so far.
What is “information streaming in a corporate or enterprise context” all about?
One problem with todays enterprise information systems is, that they mostly regard information as a rather static ressource which is to be gathered, stored aggregated and then provided to those who beforehand where identified as the recipients who might benefit from it. The handled pieces of information are mainly information about “state”, let’s say for example “company xy has between 1.000 to 5.000 eployees”. While this is certainly useful or even necessary the real useful information in terms of identifying opportunities and such is the information about the change of state, not of the state itself
Opportunities are all about timing and the recognition of a change of state.
This information about “change” has a much more volatile nature and its value more often than not decreases fast after quite short a time. Todays approaches to handle changes mostly trigger some kind of workflow that in the end brings the information to the attention to someone who hopefully will make something useful of it.
The implementation of such a “trigger and workflow” system quickly becomes rediculously complex since the value of the information largly depends on many also volatile factors. For example:
“We’re about to lose a project to competitor xy” (degrading the rating of a opportunity in the companies CRM system) in combination with the information “competitor xy is in financial trouble (from a stock market news ticker) will create an opportunity whereas both single pieces of information will not (to the same degree).
There is no way to implement a fixed set of rules, which kind of information should be forwarded when to which person. These rules are much too complex and volatile by their very nature and the amount of information to be handled too big.
Instead of trying to let the sender or creater of a message determine the relevance of a piece of information you shift this authority over to the reader or recipient.
Practically speaking:
The goal is to react faster and to miss less chances and opportunties.
The way is to generate a large stream of seemingly homogenous information about all kind of changes of state in “objects” that might be commercially relevant and to provide the recipient with tools to sieve and fish in it and to add their own value by repeating and forwarding it. This is what twitter does in a really unrestricted and uncontrolled environment.