DEV Community

Cover image for Parkinson's Law
Ben Link
Ben Link

Posted on

Parkinson's Law

Hey friends! Today on The Adventures of Blink, we're starting a new series on "The Laws of Software Engineering". Each week we'll have a different law to explore.

Before we begin: "Law" can be a loaded term

These laws are less "rules for behavior" and more "proverbs about what actually happens in the world". I don't want you thinking that I'm giving you a to-do list!

Instead, I want you to think about each of these as "Natural Forces" that describe expected behaviors. Are they airtight? Of course not. Nothing is ever perfect at describing reality. But you're going to need something specific to overcome the inertia of these laws!

Ok, that's enough of an intro. Let's get started!

Parkinson's Law

Work expands to fill the available time.

What does that even mean?

The "Parkinson" in Parkinson's Law was a British naval historian and author, C. Northcote Parkinson. In 1957, he wrote a satirical book Parkinson's Law, or The Pursuit of Progress which started with the axiom.

The book was satire, but it was written with the intent to expose the realities of bureaucracy, corporate growth, and human behaviors in large organizations.

Some key ideas from the book

First, the core law... If you give yourself a deadline of one week to complete a two-hour task, you'll end up spending the whole week on that task... often by complicating it unnecessarily.

Next, the rise of bureaucracy: Parkinson makes the argument that managers want to increase their subordinates (which increases their "power" in the organization). As a result, organization size tends to increase regardless of how much work actually needs to be done. So when people are assigned a task that they could complete quickly but a due date that exceeds that timeframe, they'll find ways to keep busy by increasing the complexity of their task.

Then there's the Law of Triviality. This suggests that the amount of time spent on any agenda item is inversely related to the importance of the item. For example, an organization might spend dozens of hours of meetings trying to decide on a color scheme for their new product while meeting to approve funding for a multi-million-dollar consultant contract in just a few minutes.

Parkinson also suggests that budgeting and spending habits within an organization will adapt to match the amount of money available.

How Parkinson's Law affects Software Engineering

The cursory example - taking a week to complete a two-hour task, and making it needlessly complex - is pretty common in our industry. In big organizations, things like this show up a massive productivity sinks.

But there's another facet of this to consider, isn't there? The manner in which we expand the task to fill the time creates "compound interest" for us! We're making things more complicated... which means the outputs are harder to maintain. Our codebase gets larger, contains more integration points, and ends up sucking even more of our time to manage.

We're not just wasting the week it took us to do the two-hour task. We're now incurring waste throughout the entire life cycle of our output.

How we overcome Parkinson's Law

There are a few techniques we can employ to prevent Parkinson's Law from eating our time.

  • Artificial Constraints. The core cause of the failure is that we allot more time than is needed, so a key tactic to combat it is to introduce some scarcity. Consider something like the pomodoro technique.

  • Defining "Done". If the temptation exists to expand the complexity, we establish a definition of "done" for every task before we start it.

  • Accountability. Making public commitments (that include your artificial constraints!) gives you some external accountability from friends or colleagues. If your problem is about distraction, you could try working without wifi or without your charger, minimizing the time that your distractions are available.

What Have We Learned?

Parkinson's Law reveals a way that our human psychology fails us. It's not something to be ashamed of, but we do need to be aware of it so that we can mitigate the risks. By setting strict artificial constraints, defining "done" early, and holding ourselves accountable, we can keep simple tasks simple and protect our codebases from unnecessary complexity.

Let's turn this into a conversation; think of a time you caught Parkinson's Law creeping into your sprint. Drop a comment below or reply to this post — I'd love to hear your stories!

And of course, I'd love to see you follow the blog so you remember to stop in two weeks from now when we tackle the next law... there won't be a post next week as we're observing Thanksgiving here in the U.S. See you in two weeks!

Top comments (0)