You also have to be concerned about the time factor. When
we
look back at a program or project, we may see something that
appears to be a bad decision on its face, but in making such
judgments we sometimes see time compressed. Some bad
decisions
sometimes occur as a series of small, and at the time
seemingly
insignificant, decisions which, collectively lead to or
become
a bad decision.
How do we recognize these as they are occurring?
Case in point (true story):
Colonel is managing 17 different small projects. He has one
which
is a small business set-aside. Six people do it, literally,
in
a garage. They turn one person's garage into an office, and
they
sit together to do the job. It is to build a prototype of a
spreadsheet to be used for tracking foreign sales. It is
only
about 40,000 lines of code and it is done well. It is also
an
experiment to use a new fourth genration language known as
FOCUS.
Then the follow-on contract comes up and the small company
gets
the follow-on basd on their past performance. It is the
only
contract this company has, so the Colonel has no real club
to use
to counter non-performance.
The new contract is abut 400,000 lines of code and they have
to
rent office space, hire people, and act like a real company.
The contractor CEO comes to the Colonel and says, "You know
all
those standards the government has on these types of
contracts?
They only apply to third generation languages, so how about
we don't
use them on this contract?" Colonel, trusting the integrity
of
the CEO, says, 'Sure. Why not."
Then, later, CEO says, "You know that stuff called
documentation?
How about we do it once, at the end, so it will exactly
match the
code and you will save all the money on document revisions
as we
go along." Colonel says, "Ok. Just do the job."
One thing leads to another, and a year later the contract is
dead
in the water. Performance problems all over the place.
Consultant
comes in and does a complexity analysis and finds that the
software
modules are so complex that a third of the modues have a
complexity
over 100,and some are over 800. Testability and
maintainability and
documentability are out the window.
Then, after things really go south, Colonel tries to
negotiate a
warranty clause. CEO says no, but then, out of the kindness
of his
heart he reconsiders and agrees, for a 5 percent increase.
Colonel
calls me to let me know hre has a warranty. I remind him
that he
has nothing because he has no documentation, and wthout a
requirements
document there is nothing defined for erformance they have
to meet,
and that he just gave away 5 percent more money for nothing.
Things get really bad, and, trying to get what he can, wants
to have
the history of the project documented. CEO is the only one
who has
it, and he dies of brain cancer and the history goes down 6
feet with
him. Colonel is asked to retire. Contract is cancelled.
Company
goes away. End of story.
Jim Dobbins
"John L. Naman" wrote:
>
> John Naylor said, "By bad decision, I meant one that could be identified at
> the time it
> was made."
>
> Let me get you to clarify the context of analysis here. Are we talking about a
> single decision-maker or a group/organization decision? And are the criteria
> (values) for "bad" those of the decision makers or outside observers? I think
> these two questions can make a big difference in your search for bad
> decisions.
>
> When there is more than one person involved, there can be different views on
> the same decision. A board or committee meets and some feel that a course of
> action is "bad" and the majority feel otherwise, are blinded by greed or ego,
> etc. Or do you mean a decision that can be identified by as "bad" by academics
> or other outside observers (non-participants)?
>
> Another example: In some elections, there are quite a few who feel that
> electing Candidate A would be a "bad" decision and there are many editorials
> to that effect. However the majority vote for A and the "bad" decision results
> in the feared bad outcome (or worse). Examples can be found throughout
> history, in many countries and political parties.
>
> --
> Prof. John Naman Katz Graduate School of Business, University of Pittsburgh