Sunday, 22 November 2009 00:00

The Garage Syndrome: Everything Swells To Fit Its Defined Boundaries

Rate this item
(0 votes)

A garageWe have all noticed how there is never enough space, money or time. It escapes no one and nothing. If there are two weeks to do a task it will take two weeks, if there is a $10,000 budget it will take $10,000 to do whatever it was. It is human nature. The goal has been set, it must be acceptable, so we strive to meet it. I refer to it as the "Garage Syndrome"—junk swells to fill the space in the garage.

Think about a project schedule. A task is scheduled to take two weeks. What is the incentive for people to get it done in less time? When asked when a task will get done, workers assure you they will be done on time. Of course, targeting to be done on time, leaves no room for error and, hence, many tasks end up being late with few being done early to compensate.

Resources Include Pad To Meet Odd Requests

Here is the typical course of events:

  1. Joe gets ready to work on his task. He has two weeks to do it.
  2. Pamela, his boss, asks if he can slip in some other work she really needs to have done. Joe looks at his estimates and agrees to do the extra work. He thinks he has time to get it done.
  3. You, the project manager, ask Joe how it's going. He responds, all is well and he will be done on time. You walk away blissfully ignorant thinking he is working on your project.
  4. Joe runs into trouble on his boss's task; it takes a little longer than he thought.
  5. Joe reaffirms he is on schedule to complete your task...

There is no need to continue the scenario because you know where it is going. So what is the problem?

The problem is that Joe had more time than needed to do the project task. He thought he could fit in his boss's request. His boss knows he has extra time since she always gets her staff to fit in other tasks. The corporate culture works that way—Garage Syndrome. Had Joe only had enough time to do the project task, he would tell Pamela no.

This is no different from a garage filling up with junk. If you lived in downtown with no on-street parking your garage would have minimal junk since your car would have to be in it.

Management's Attempt To Control

People complain about managers that cut the budget and the timeline to produce some product, but everyone knows that the Garage Syndrome exists so they try to constrain the project to prohibit its growth. Why does this never work? Because Pamela is the one that cut the budget and Pamela is also the one to ask Joe to do the extra work. Management is only following half the formula. If they are trying to get the project back to what it really needs, they cannot expect there to be slack to handle more work.

Anytime I bring this up, I get huge push back, just like when I say people should not be multitasking. People decry they are great multitaskers and must do it since that is way in today's business functions. I think that is all bunk and is a direct result of people being unable prioritize and make hard decisions.

Muffins?
The theory's testing continues...

Urgency reigns. The burning request filled by a worker makes them a hero and gets them the kudos for be the firefighter and problem solver. However, the result is just no more problem of late deliverables somewhere else. Get the instant gratification and ignore the deferred setback. We need to stop firefighting and get back to prevention.

It Manifests in Scope Creep

By the way, the attitude does not stop here. It is pervasive in how we work.

Lately, I rebuilt my website. It used to be custom html and php and finally the maintenance was more than the benefit. I figured that tools like Drupal, Joomla, Wordpress, etc. had more features than I could ever have developed. I generated my requirements list, got through the evaluation and chose the tool that was the best fit. During implementation, though, I had to keep fighting back the urge to implement this feature or that. The fact that the other neat features existed were a huge temptation to implement just one more little thing and have just that much cooler a site.

It struck me, as I caught myself doing this, how on a recent project I had to fight the message bus team to keep them from implementing dozens of features that were outside the scope of the original design. I also remember how they thanked me twelve months later when they found out those features were incapable of doing the tasks they wanted.

Yes, even scope will swell to fill the holy grail of technology.

Read 6097 times

Related items

  • Success vs Culture

    The other day a Latvian student contacted me for my views the connection between culture and success criteria—an important and intriguing topic. After working in Taiwan, Singapore, Korea, Japan, Israel, United States, and Canada, I wear many scars of both blatant and subtle cultural violations. I also know that within a culture one person's success is often another person's failure. So, after dispelling concerns about clicking on some random email link, I completed her survey (please feel free to take it yourself). In the process, I struck up a friendship with the student, Kristine Briežkalne, who is studying at Riga International School of Economics and Business Administration . She has some interesting views and presented me with a Venn diagram showing four frames to a project (business, client, project management, and growth perspectives) and how they intersected. As the diagram is part of her Master's thesis, I will let you ponder the how to label the overlapping areas (an eye-opening exercise).

  • Kill The White Knight

    There is a reason we do not teach classes on fixing failing projects. Many a cynic feels that we simply do not want to teach our trade, however, our reason is far nobler—we should be teaching prevention rather trying to create white knights to save the day. It is the same philosophy as building a fence at the cliff's edge rather than an emergency room at its base. Our language is replete with idioms telling us to look past the symptom and address problems at their root cause. 'An ounce of prevention versus a pound of cure' or 'a stitch in time saves nine.' Please, feel free to supply your own in the comments. Unfortunately, most of our businesses loathe this philosophy, waiting to address an issue until it is irrefutably broken.

  • The Executive-Project Manager Gap

    It was such an innocuous question, "Working on an article; what is the biggest problem you see with project governance at orgs? Can you comment?" Can I comment? Really? That is like cheese to a mouse. Where could I start—bureaucracy, draconian process, poor executive sponsorship, disengaged leaders? Plenty of fodder, because they all lead to project failure. I fired off, "Creating an over bureaucratic morass stifling innovation & implementing process instead of cultivating leaders." Then the maelstrom started and it went directly to the gap between the executives and projects managers. Naomi Caietti, Robert Kelly and I had a great conversation. Most of the thread is below.

  • Disband Your PMO

    After nearly 30 years of project work, I struggle to understand the role of a project management office (PMO). Even though, I have written of the pros and cons, and read a plethora of articles, opinions, and how-to guides little has been done to convince me that the PMO is reducing project failure. It seems to be nothing more than a tool to fill a void in leadership? Even the acronym, which is so widely thrown around, has little meaning as the "P" has no less than four meanings. It is an executive's crutch for their lack of understanding in how projects work. These, like other, unattended holes in the corporate accountability create opportunities for new and greater bureaucracies and empires that further obfuscate accountability.

  • The Catch-22 of Organizational Change Management

    "Kotter, ADKAR, or CAP which methodology should we be using to build our approach to improving project adoption?" I hear this question repeatedly from people trying to implement an organizational change management (OCM) program. The problem is that is the wrong question. Take a perfunctory peek at any of the models and you will see that in the quest for an answer people have mistakenly jumped over the first few steps and they head down the road of failure. It is a Catch-22; unless you already have an OCM process in place, you will most likely fail at implementing it. Putting one in place, however, is a change—one of the most difficult cultural transformations your company will undertake. As a result, people jump to the solution stage, which is well down the change management process path (which, they did not know, ironically, since there was no procedure in place).

Leave a comment

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References

Sitemap