Let's try status blogs
Document Actions
Long ago we made all of the developers do weekly status reports online. After a while they went mostly unwritten and almost entirely unread. Well now we're trying again, but this time we're doing it in a group blog format.
How it works
Every employee gets a
blog that will live at http://software.cnx.rice.edu/devblog/<username>/. These get combined into an aggregated group blog. Just login to http://software.cnx.rice.edu (use your Connexions machine password, not the Connexions authoring password) and click on the MY BLOG
link that will appear in the user bar. The rest is up to you. Customize
the title (within reason) and blog away. When you're done
Save it and change the state to
published using the dropdown in the upper
right corner. I'm asking that everyone (including me) do at least
one blog entry a week before the staff meeting. As an incentive, the
more you put in your blog entry the less we'll have to cover in the
meeting and I know everyone likes shorter meetings, right?
Why
Several reasons:
- Shorter meetings
- Better transparency - people can see that we're actively working on things
- Keeps us up with these newfangled blog whosamawhatsits
So dive in. Try it for a couple weeks and then let me know what you think. We've got lots of fliexbility in how we structure and approach this.
