Comments on: BI 2.0?

By: BI 2.0 es “VaporWare”? « aníbal goicochea

BI 2.0 es “VaporWare”? « aníbal goicochea — Fri, 05 Feb 2010 18:36:16 +0000

[...] misma Web 2.0, podríamos “filosofar” muchas horas y no llegar a nada, como el post de Timo Elliot, Referente en SAP BI, que después de leerlo, sigo con similares interrogantes. Buscando en la Blogosfera, [...]

By: Antivia: The First Real BI 2.0 Solution? | BI Questions Blog

Antivia: The First Real BI 2.0 Solution? | BI Questions Blog — Wed, 18 Mar 2009 14:14:41 +0000

[...] I’ve written before, if BI 2.0 is to mean anything, it should be about “collective intelligence”: letting [...]

By: James Taylor

James Taylor — Tue, 06 Mar 2007 18:35:39 +0000

Interesting post and thanks for linking to my article on BI 2.0 and EDM. I think the comments you quoted are particularly interesting.
Unlike Mr Saylor I don’t
“want to know when … my equities are in trouble” I want a system to do something useful when my equities are in trouble or even better BEFORE they are in trouble. This is about taking action based on insight (Enterprise Decision Management), not just about insight (BI x.0).
Similarly If you want “A voice in your ear” to “caution you not to take that medicine” that requires the rules to manage drug interactions (as several companies are doing) not BI and so on.
People need informed decisions turned into a utility, not just or always information.
JT
P.S. Perhaps the Slate journalist meant to say “he will be its Edsel”?

By: Jeb Boniakowski

Jeb Boniakowski — Tue, 06 Mar 2007 15:42:23 +0000

Timo– very interesting post. At Proto, two of the things we talk about in the BI space a lot are:
1) Putting ability to tackle small, local BI problems into the hands of vastly more people. Right now, loads and loads of BI users out there are just dumping data out of their real BI system so that they can slice ‘n’ dice it in Excel. We want to give these analytical but not necessarily super technical users to ability to do more advanced and less error prone BI analysis, and to be able to share that easily with their colleagues.
2) Related to that, and probably our most “2.0-ish” belief is that there is a lot to be gained by making it easier for the whole continuum of users to collaborate on solving BI problems. If the guy who’s responsibility it is to write the report is really a DBA and doesn’t get the business problem, you’re headed to a situation where the end user and the technocal person go back and forth through loads of revisions to get something right. We’re trying to make it possible for people’s responsibilities to overlap a bit more, in the belief that this will lead to better solutions delivered more quickly.
Using Proto, a non-technical person can still drag and drop to create the screen they want to see, and they can send that to someone more technical to “wire up”. It’s amazing to see how quickly going through this exercise makes people realize “oh, no, I don’t actually want that field, I want this one.” Technical people can produce components that are easy for less technical users to consume.
Anyway, I apologize for getting rambly in your comment section so I’ll cut myself off, but if you have an opportunity to look at Proto I’d be very interested to hear your thoughts.