It's Too Good to be True
Surprise! The client's business people loved the rule engine software (BRE #1) because they could write rules in an English-like language. The client's IT people didn't like it as much because they could write rules in an English-like language. It had something to do with, uh, you know, hey, if we actually used this thing we wouldn't need some of our IT business analysts because the tool is so good that the Subject Matter Experts / Domain Experts could author the rules themselves without IT Business Analysts... And if we ever figured how to really use this engine, we may not need some of our IT Programmers either... (See: "the usual suspects")
So, the client decided to use another BRE software package (BRE #2) that:
- Required the larger IT infrastructure investment and ongoing IT support that this client was used to
- Didn't have as "English-like" a language. Because it was more like a typical "programming language", it would be eaiser to the IT People to learn
- The rules were written in a "Java-like" language that IT People understood better
Now both the Business and IT are happy. BRE tool vendor #2 is happy. BRE tool vendor #1 is not - They lost this sale because their tool was too good to be true.