Practically all software suffers from problems: Maybe it runs too slowly, sometimes crashes, doesn't look as nice as the competitors' product or changes take too long. Apart from hello-world applications, there is always room for improvement. Here we show you how to detect such problems. Check use of appropriate technology: The choice of underlying technologies and frameworks can significantly influence the changeability of a system. Example: In early architecture and programming paradigms of Enterprise Java, development teams had to configure their systems manually in XML-based deployment descriptors besides fulfilling complicated programming requirements. This was both time-consuming and error-prone. Simplified models such as Spring Boot reduce the cognitive load for development teams and, therefore, most times lead to systems that are easier to change. Therefore, you should check the technologies and frameworks used to determine whether necessary or frequently recurring changes are made easier or more difficult as a result.