After two independent experiences I am convinced I have found a new anti-pattern. I am going to call it "Design by Framework".
Antipattern name: Design by Framework
Also known as: There is no other way
Most frequent scale: Small department in large organization or small company
Refactored solution: Download and use available software from the internet
Refactored solution type: Software, Communication
Root Causes: Fear, Arrogance, Lack of Feedback, Lack of Knowledge of available solutions
Unbalanced forces: Design and Team work, Feedback
Anecdotal evidence: "There is no other framework that has the same functionality",
"Our software is so much better than what is available"
A certain framework has evolved over time. The framework has been successfully used in perhaps one or two projects. Nevertheless, the added value of the framework is doubtful when compared to the currently available software. Also, the functionality of the framework is typically incomplete and requires a lot of development at every new project. Regardless of these factors, the framework is almost forced upon new projects because of the fear of trying a different solution and the lack of knowledge of existing solutions.
As a result, designs start from the framework instead of from the domain model and the functionality to be implemented. In some cases, people struggle for weeks to get the framework going after which they finally give up. Despite this, the situation persists since the Framework has a few fanatic followers (the people who designed it), and since there is fear of giving honest feedback about the framework.