eRoom spruces up hosted collaboration offering. "NEXT WEEK COLLABORATION software provider eRoom plans to roll out an updated version of its hosted digital workplace offering, featuring integrated real-time communication tools and new business process capabilities."
Dody Gunawinata has set up a Manila/Radio community for his organization: AIESEC. Nice. [John Robb's Radio Weblog] I like it too. Is it possible to do something like this (I mean the home page) for Radio Community Server?
You cannot make people smarter. Curiouser and curiouser! quotes Mathemagenic:
And continues with his concerns: "My fear is that klogging will only thrive in organisations that are healthy, and that there may not be enough of them. Or, worse, that klogging will thrive as a control mechanism imposed by insecure and fearful management. I don't want to be a part of that." [Curiouser and curiouser!] Very good point. I don't that the former is something to be afraid of. It may work as a nice indicator of the health of the company ;).
[from my PhD proposal] Learning is best described by the metaphor “you can lead horse to the water, but you cannot make it drinking”, or as Joseph Kessels says “you cannot make people smarter”. Even in the case of formal learning an organisation does not have control over employee’s brain and heart, so in order to benefit from employee learning, companies have to find the way to support and encourage it without full control. The author believes that the answer lies in supporting interplay between individual and organisational needs by relating and integrating employee-driven informal learning and organisation-driven formal learning.
Ray Ozzie: Architecture matters: The Rebirth of Public Discussion. "In traditional discussion, topics and their responses are contained and organized within a centralized database. The relationship between topics and responses is generally maintained in a manner specific to the nature of the database - that is, in newsgroups the messages might be related by Message-ID hyperlinks or crudely by title, in Notes they are related by the $REF hyperlink, and so on. Summary-level "views" are generated through database queries. And that has been the general architectural design pattern of public discussions for quite some time.
But blogs accomplish public discussion through a far different architectural design pattern. In the Well's terminology, taken to its extreme, you own your own words. If someone on a blog "posts a topic", others can respond, but generally do so in their own blogs, hyperlinked back to the topic's permalink. This goes on and on, back and forth. In essence, it's the same hyperlinking mechanism as the traditional discussion design pattern, except that the topics and responses are spread out all over the Web. And the reason that it "solves" the signal:noise problem is that nobody bothers to link to the "flamers" or "spammers", and thus they remain out of the loop, or form their own loops away from the mainstream discussion. A pure architectural solution to a nagging social issue that crops up online."