Tag And Flow: Connecting The End Points

For oponia, we had a planning session with some really great ideas that came up for the enterprise space. Since we don't plan to focus our efforts there I thought I would put up the ideas in hopes that they spark some thoughts for other people developing applications.

The basis of the concept was merging tags with the concept of flow. What am I taking about?

Traditional business works hierarchically. We create project folders. And yet that mode of working doesn't necessarily help work flow across projects. How does one then accommodate enterprise 2.0 concepts of viewing things by ideas? Or type?

What if project folders automagically created tags? What if files did the same? What if people in your network automagically were tags as well? Couldn't you then search by project (if that's what you wanted) or also then across projects by idea or type? You could then even search by person.

Alfons liked the idea so much he put some initial screens together. One is the search screen and the other is the results. Of course, if everyone on the network is a node (which is the basis of the ucaster concept) we can do some things that others can't right yet.





Conceptually though the idea is that you can create a results page that is centered around a project (trad style), centered around an idea (enterprise 2.0 style) or centered around YOU (always the best style).

We still plan to implement some of the cool parts into the consumer product when we can get to it. I'd be interested in what people think.

update: R/WW has an intersting post on what the big players are thinking. Check it out...