This one has been doing the rounds today (probably among people like me who are supposed to be writing a status report ;-) : Rands In Repose: Status Reports 2.0

"There needs to be some creative incentive for individuals to write stuff down. For the Wiki, there is the promise that if you write it down, maybe you can avoid future lame redundant questions. For the weblog, the timely conversational style of the medium keeps the content focused on news of the moment and that's really the question; is news of the moment interesting to an engineering organization?

What I'm curious about is if anyone has had any success using web-based collaboration tools as a means of augmenting or replacing status reports. I know Wikis have successfully emerged as semi-structured information repositories... have they evolved into anything? How in the world can I get out of writing Status Reports?"

And while we are on the subject, John Moore would like to add: Process? Schmocess!