Tag: management

One more thing

Last year Matt Mullenweg wrote this post and I somehow missed it.

There is a dark time in WordPress development history, a lost year. Version 2.0 was released on December 31st, 2005, and version 2.1 came out on January 22nd, 2007. Now just from the dates, you might imagine that perhaps we had some sort of rift in the open source community, that all the volunteers left or that perhaps WordPress just slowed down. In fact it was just the opposite, 2006 was a breakthrough year for WP in many ways: WP was downloaded 1.5 million times that year, and we were starting to get some high-profile blogs switching over. The growing prominence had attracted scores of new developers to the project and we were committing new functionality and fixes faster than we ever had before.

What killed us was “one more thing.” We could have easily done three major releases that year if we had drawn a line in the sand, said “finished,” and shipped the darn thing. The problem is that the longer it’s been since your last release the more pressure and anticipation there is, so you’re more likely to try to slip in just one more thing or a fix that will make a feature really shine. For some projects, this literally goes on forever.

On working hours

I’ve recently started advocating for flexible working hours in all the offices I can get my foot into.  With our recent power cuts there was an extra possibility for a few companies to try remote working and more flexible schedules.  It went very well with some, and so well with others.  The lack of self-discipline is often mentioned as a primary roadblock to such flexibility.  I used to agree with that.  But now I don’t.  I think that internal company communication tools and channels have a much larger impact on whether flexible schedules and remote work will work or not.

Why am I suddenly speaking about flexible hours?  Because I came across this blog post by Zach Holman, one of a few GitHub employees.

By allowing for a more flexible work schedule, you create an atmosphere where employees can be excited about their work. Ultimately it should lead to more hours of work, with those hours being even more productive. Working weekends blur into working nights into working weekdays, since none of the work feels like work.

Read the whole thing, it’s not that long and it is well written.

On status meetings

Web Worker Daily shares an insight on status meetings:

It will probably come as no surprise to WebWorkerDaily readers that a recent survey found that 70 percent of information workers don’t believe status meetings help them accomplish work tasks. Additionally, almost 40 percent of respondents feel that such meetings are a waste of time, even though 55 percent of respondents spend one to three hours per week attending such meetings.

The survey also found that 67 percent of respondents spend between one to four hours per week just preparing for status meetings, and 59 percent said that preparing for status meetings often takes longer than the meeting itself. In addition, 57 percent of those surveyed indicated that they multitask during status meetings — so maybe there’s more work getting done than one might think!

The survey was conducted online within the United States from June 6–8, among 2,373 information workers.