An Email alternative: four dimension of feeds (RSS) in organizations

August 10, 2007

To continue with my post “What is enterprise2.0,” I wrote a case study for organizational blogging. Inspired by the posts from EnterpriseRSS, Paul Dunay and Splash Cast, rss.jpgI want to focus this time on RSS and feeds. In my opinion feeds can make a decisive difference in getting the right information at the right time in the right place, and can also reduce the email overload. As we still have to wait for the semantic web, RSS offers great potential for organizations in the following four dimensions:

  1. Transmitter: Don’t email it. RSS it. Feeds deliver the latest information from themes and projects: Discussions in group blogs, solutions for problems in personal blogs, the status of documentation in wiki, interesting website through subscribed links feed, etc. This information is transparently available, showing organization wide activities otherwise hidden in email boxes. It is possible to get information from all kinds of projects inside an organization, and knowledge creation can be seen through news tickers from everybody’s browser.
  2. Filter: Contrary to email push technology, feeds are a pull technology. One can decide by himself what to follow and escape the email flood. Some feeds are binding, such is the case of the department protocol or the follow-up of a milestone for a project; but most feeds can be subscribed by interest. Project steps can be easily monitored, links in a specific community of practice exchanged, or discussions can be followed. With evaluation tools such as AideRSS, valuable and most discussed content can be filtered.
  3. Overview: Imagine that an intranet homepage would be like a feed aggregator. A look on the page shows exactly what is happening right in that moment in the whole organization. A feed aggregator would present all kind of feeds sorted by topic, projects, departments, date etc. Each topic or bigger projects have their own aggregator and can be browsed through tagclouds in every direction to find quickly a topic. Knowledge creation and information exchange can be followed from anywhere in the organization. Information does not have to be pushed into singly categories and limited databases.
  4. Mashup: Like Yahoo pipes presented a while ago, these feeds can be easily combinable. Project developments are connected to a map application so one can see geographically where about and who it’s own organization is dealing with or discuss about it. In a multilingual organization, feeds can be redirected through translation services. Every employee can build his own aggregator and can mix data for his individual purpose.

No doubt this approach cannot be implemented easily. The problem is not technological, but it does need an open organizational culture. It does shift vertical to horizontal communication. Clearly, there can be numerous obstacles listed. The transparency must not always be in the interest of the management. It demands from the staff a great capacity to absorb all this feeds, sort, process, and digest them. Or how David Weiberger says it: “The task of knowing is no longer to see the simple. It is to swim in the complex.” Another obstacle are feed-readers, which are until now very basic and have to be further developed to easy sorting, archiving (tagging) and so forth.

Connect lessons learnt through tagging

July 25, 2007

Yesterday, I read a blog post about “How do you convince people to share failures?” and I also heard about an interesting lessons learnt website project which was implemented some years ago.

In that project station masters were asked to give regular information about their stations such as statistics. Secondly to list problems and challenges throughout the last years. They were asked to describe how they tackled the problems. What were the failures and the success? This information combined with some criteria were filled to a database. With that every station master could find colleagues with similar problems and could contact them.

Taken from Flickr by Trooper3d (CC)To me, it seems like a simply mechanism with a great result. A knowledge sharing tool which concentrates on learning experiences and connects people and knowledge.
But how would you do this nowadays in the realm of web2.0? Two questions came up to my mind:

  • Does web2.0 really help us exchange lessons learnt in such an effective manner?
  • Can tagging be the right way to find each others lesson learnt easier?

Web2.0 and lesson learnt
I have my doubts whether web2.0 goes this far yet to connect the right people with same problems in such an effective way. Social network tools give you features such as recommendations, feedbacks and a whole range of perspectives. But is that all you are looking for in that moment? In the best case, you can have a community of practice where you can address your questions. Valuable experiences are still hidden behind numerous links, which I can identify easier with social bookmarking, but still have to hope that Google will deliver me good results.

Tagging
In my opinion tagging is very powerful, but often underestimated, because it gives us relevance. Look at a tag-cloud and imagine you can click through endless relevant sub-tag-clouds. You can navigate through an ocean of wisdom, connecting knowledge and the people behind it. Imagine tagging is used wider than to just give broader information (e.g. general topic) but includes many much more information such as the “character” of a lesson learnt (success, failure, slow, expensive, high impact etc.). Many people already do that in social bookmarking, though it is very individual.

  • Would that mean I can connect experiences the way it was down with a sophisticated application for the station masters? I wonder whether tags for evaluation can work as good as the topic-wise ones.
  • How could the word “slow” be separated in a tag cloud from the word “software” so they do not stand next to each other?
  • Do I really need this, or do topic clouds bring me anyway quicker to the field of my interest, and comments deliver the evaluation to me?

My aim is to use the power of a network itself to connect to experiences directly. I think that in most cases an application such as the station master is too much of an effort. It needs criteria and complicated programming. Can’t this be done easier with web2.0 technology and the wisdom of crowd?

NPK4DEV – a collaborative tagging experience

June 14, 2007

I remember when I came across those weird looking different size word aggregations on websites and wondered what were they? When I read about tagging and tag clouds I was first skeptical about it and asked myself what is the benefit of them?

Nowadays I am fascinated, how tags can solve or at least improve how we sort information and make relevance between different tags. Through the wisdom of crowd one can extract very precisely the connections of themes and show the pattern of a community. To me classical hierarchical folder structure is only two dimensional, whereas tags are three dimensional, as long as the semantic web has not been implemented.

With social bookmarking through de.icio.us a single tag can be used to share links collaboratively. Peter Ballantyne had the idea of using collaborative tagging for the knowledge management for development network back in 2005. Next week another KM4DEV workshop will take place in Holland where I will prepare some visualization of the efforts throughout the last two years for the nonprofit knowledge management for development (NPK4DEV) tag.

NPK4DEV Tag Cloud (popular tags)
Tag Cloud

Joitske, a contributor of NPK4DEV wonders whether this tag experiment can form a community?

Tagging seems so superficial in terms of knowledge creation, it is more a flow of information. Can we say there is learning going on or is it just sharing information more rapidly? If people start tagging can we all that a community of practice?

In my opinion this tag cloud shows quite impressively what people associate with knowledge management for development in methods, countries, organizations and themes. It is a great way to share certain kind of information. In this regard it might be a passive community of practice keeping each other updated about new and interesting documents or new approaches such as vlogging. Furthermore it connects you to the people behind it.

However to deepen the effect of sharing and to have a broader learning effect, further steps would be necessary. For example Beth Kanter summarizes in her posts all links for the nptech tag, which is very useful. The communication between each other over delicious is close to zero, and one does not know whether the information behind the link is useful or valuable to his or her background. Commenting is rarely used and rating is not possible, and only bloggers involved reflect transparently the shared information.

Lastly, it is interesting to see how you can analyze tags, in this timeline. In the picture you can see the recent tags. Thanks to the blogger from www.unthinkingly.com, who did this timeline very nice with the nptech tag.

tagliner

Sun blogging turns communication upside down

May 31, 2007

Sun Microsystems’ blogging approach changes the company’s communication and knowledge management. In wikinomics I encountered Johan Schwartz, the CEO of Sun, with his unusual approach of not being him the only one blogging but also his colleagues, whom he encourages to blog publicly about their work and anything else they are interested in. His concept has an outcome of about 3000 bloggers (around 10% of all employees).

The Sun blogger Jörg Moellenkamp did an interesting presentation last April during the re-publica conference. He explained enthusiastically how he communicates directly with his clients or other programmers, and how ‘direct communication’ improved his personal learning. Beside of a policy, the basic limited rule for blogging at Sun is: don’t tell secrets. This evokes the question: “Have you ever had a situation where a blogger posted something they shouldn’t have?“, which Linda Skrocki answered in her blog. In other words Sun has shaped its own blogosphere with almost 70.000 articles mainly in the realm of its work – as a provider for network computing infrastructure solutions.

I think this blogging approach offers a combination of internal and external knowledge management offering all sorts of community of practice. Blogs contribute to codify tacit knowledge and connect people inside and outside the organization. It also offers a different concept for customer relationship management.

I asked Möllenkamp if this approach is limited to the software industry or even those ones with an open source concept? He answered that it is rather Sun’s unique culture, being it very open and putting a high level of trust in its staff. I wonder how this model could be applied to other industries or even non-governmental organizations (NGOs)? It could certainly enhance the accountability of NGOs and even more important, give opportunity to a real multiple networking for an organization in order to make their work more creative and effective. And as Allison Fine argues in her book Momentum: Igniting Social Change in the Connected it would make members or sympathizers participants for social change.


Possibly related posts:

Tags: , , , , , | Print this post | RSS Subscribe to my blog

Comments

Rounded corner top left
Rounded corner bottom left