Real-Life Decision Making
You're a programmer at a small company specializing in computer systems
for retail outlets. In this position, you often deal with clients whose technical
knowledge of computers and computer software is limited.
Servicing the needs of these clients can be like walking a fine line. It's
just as important not to over-build, or make a system too expensive, as it
is to make sure the system can grow with a client's needs.
This balancing act can be complicated by a client's lack of technical
knowledge or misinformation. Today, you are staring right down the tightrope.
A client has come to you, explaining a problem at her business. She has
seen the expensive new system you've designed for one of her competitors,
and she thinks this system will solve her problems. Since her company is much
smaller and her needs much simpler than her competitor's, you know she
doesn't need such a complex, expensive system. She could spend a lot
less money and still solve her problem.
You explain this to her, and begin to tell her about the cheaper, more
appropriate option. She's not impressed. She's convinced she needs
the larger system, in spite of your suggestion.
It's a difficult situation. The difference between the two systems
represents big income for your company. The more expensive of the two systems
would definitely be overkill for this customer, but if the more
expensive system is what she wants, maybe you shouldn't question your
good luck. And maybe, at some point, her company will grow into the larger
system.
What are you going to do?