Hurry Up And Wait

no comments

In the corporate world, I would never consider this phrase a positive job description.

It basically means that your job consists of lots of work, though it only comes in bursts. In between bursts is a non-productive lull. What causes this lull? Why can’t the bursts be alleviated by simply spreading things out? I feel that this description dictates a position that relies on many other positions in the same position. The bursts occur when something happens at the end of a very long chain of “Hurry-Up-And-Wait-ers” that causes a reaction all the way down the line. Each person rushed to complete their part to pass things along to the next.

I personally don’t like relying on other people to move forward. I also despise inefficiency. Mainly because the combination of the two is absolutely not productive. The “Hurry Up And Wait” model is one of these combinations.

HUAW Diagram

In the above diagram, chalked full of “Hurry-Up-And-Wait-ers” a total of 9 connections must be made, passing things on along down the line. These would actually back and forth connections since the initial two would be sent, and then waited on for return information. Whereas below, in the “Adam Is Awesome” schema, the excess “Hurry-Up-And-Wait-ers” are required to do nothing, since 3 direct connections are made. Both efficient, AND time delays are minimized since there are only 3 people to “wait” on.

AIA Diagram

What a ridiculous post. There are many other things I’d much rather write about, though this seems like the only appropriate thing at the moment.

Written by Adam

November 14th, 2007

Posted in Personal

Leave a Reply