A couple of years ago I predicted that Weblogs would emerge within the enterprise as a great way to manage project communication. I'm even more bullish on the concept today. If you're managing an IT project, you are by definition a communication hub. Running a project Weblog is a great way to collect, organize, and publish the documents and discussions that are the lifeblood of the project and to shape these raw materials into a coherent narrative. [Full story at InfoWorld.com]

 

Here at Macadamian we’ve been evangelizing the use of the intranet to let anybody publish information for several years. We developed a technology to actually implement this easily in Corporation; we call it Syndeo Project Server. We got a handful of Corporations going.  We’ve spent much time working at convincing organization of the value of power to the people to publish what they want. We’ve had a hard time convincing them.

• If it’s not in the corporation culture, it tough a tough sell.
• E-mail is in there culture though, and we should leverage that medium.
• In corporations we deal with, several employees have their own website(s)
• We’re asking them to give this up, and work with a central one. Big no-no now that I think about it.
• From Corpo stand point bad, we thought, since no formalism in presentation, impossible to find info on all dif sites.
• Weblogs have a shot here, because they actually encourage multiple websites, and RSS ties it all together for the corporate knowledge hive
• The ROI is hard to quantify, just like any knowledge management techno if you ask me.
• weblogs are  simple, and it’s about techno/concepts that in the mind of the potential buyers have been around for ages,  they’ve all thought about it but didn’t consider complex, important enough to pursue.
• ASP toolkit coming up with a weblog sample gives them credit for that.

 

Anyhow my 2cents…it’s very interesting, and I’m continuously thinking about it.