English Language & Usage Stack Exchange is a question and answer site for linguists, etymologists, and serious English language enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is there a name to characterize certain requests that look like a good idea at first, but ultimately have a false premise?

Example 1: We need our software product to be extremely configurable!

Supporting extreme configuration shifts some responsibilities from product designers to end users. It also creates inconsistent user experience, and makes product looks unsure of its own identity.

Example 2: I need real-time stock market data to make better trading decisions!

Looks like a good idea: a user can react on stock market fluctuations faster than anybody else and beat the market. The truth is that they will be picking up more noise and making bad decisions.

Those were just examples, I'm not looking for arguments on those statements.

share|improve this question
A note: your examples are not premises, just statements. I think you assume them to be conclusions, but still it is not clear if they were made based on a false premise or wrong reasoning. If I ignore these ambiguous elements from the question all that is left is: "Name for a requests that look like a good idea at first, but ultimately are not." If you need something more specific, please clarify further. – Unreason Nov 11 '11 at 10:42
up vote 3 down vote accepted

MYTH came to my mind, although it might not fit your case.

From dictionary.com:

An unproved or false collective belief that is used to justify a social institution
share|improve this answer

The best word that I can think of to describe the request is "pitfall."

From Merriam-Webster:

a hidden or not easily recognized danger or difficulty

I am a software developer myself so I get these kinds of requests from clients all the time. From the perspective of the client the feature request is perfectly rational. It is only you, the professional software developer, that can spot the hidden danger in implementing such a request.

share|improve this answer

The examples may be instances of ignoratio elenchi, that is to say, irrelevant conclusion or irrelevant thesis informal fallacies.

Informally and less specifically, one could refer to faulty reasoning, being over-hasty, jumping to conclusions, or making premature judgements. The examples also can be said to ignore the design principle of least surprise (or least astonishment).

share|improve this answer
Isn't it also, after a fashion, 'petitio principii'? – Barrie England Nov 11 '11 at 8:42

Such requests or requirements reveal themselves to be impracticable or unfeasible.

You can say that the idea turned out to be a blind alley:

Blind alleys and garden paths leading nowhere are the principal hazards in research. [Lewis Thomas]

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.