Working Up

Working Up in Project Management, Systems Engineering, Technology, and Writing

Working Up header image 2

Two Unspoken Requirements

November 24th, 2014 · No Comments

by Dwayne Phillips

Many projects make no sense. They are driven by two unspoken yet paramount requirements.

I have seen many projects that were driven by two unspoken but paramount requirements:

  1. The project must cost a certain amount of money—no more and no less
  2. You have to look like you are trying to do something

Allow me to elaborate.

  1. The spoken requirements for a system are published.
  2. Analysis shows that a system that will meet the requirements will cost $1,000,000.
  3. The managers of the organization decide to build a system that will cost $100,000.
  4. Analysis of system #3 shows that it will not meet the requirements, i.e., it won’t work.
  5. The organization builds system #3 anyways.

One way to tell if the project is driven by the two unspoken but paramount requirements is to inject a step 3.b. by suggesting:

Let’s build a system that costs $1. It won’t work either, but it will cost even less.

This suggestion is laughed out of the room immediately.

Logic argues for system 3.b. in that it won’t work either, but it will cost much less money. Logic, however, fails the paramount requirements in that the $1 system doesn’t appear like you are trying to do something, other than trying to show the silliness of the entire situation, and doesn’t cost the required amount.

These silly requirements stem from the concept that people are earnest, well intentioned, and want to do something about a need. Reality, a $1,000,000 is needed, bursts the bubble, but still,

there must be something we can do.

Tags: Culture · Expectations · Magic · Management · Requirements

0 responses so far ↓

  • There are no comments yet...Kick things off by filling out the form below.

Leave a Comment