
Anyone who works with a group of people needs to understand the idea of bike-shedding (as known as the law of triviality). Let me jump right to the Wikipedia entry to explain it:
The law of triviality is C. Northcote Parkinson’s 1957 argument that people within an organization commonly give disproportionate weight to trivial issues. Parkinson provides the example of a fictional committee whose job was to approve the plans for a nuclear power plant spending the majority of its time on discussions about relatively minor but easy-to-grasp issues, such as what materials to use for the staff bicycle shed, while neglecting the proposed design of the plant itself, which is far more important and a far more difficult and complex task.
The law has been applied to software development and other activities.The terms bicycle-shed effect, bike-shed effect, and bike-shedding were coined based on Parkinson’s example; it was popularized in the Berkeley Software Distribution community by the Danish software developer Poul-Henning Kamp in 1999 and, due to that, has since become popular within the field of software development generally.
Coming from the software development community, I’ve known about and seen countless examples of bike-shedding in meetings I’ve attended. I just assumed everyone knew the term. It was only when talking to people outside of software did I realize the term was not as well known.
Now you know it. And now that you do know it, you will see examples of it in many of the meetings you attend this week. 🙂