CJM and why does the tester need it ?

Product metrics are slightly underestimated among testers. Every time the conversation turns to how to prioritize a defect or choose which test cases will fall into regression, I ask: “Do you know the CJM of your product?”, and often this question puts people at a dead end, people either do not understand why they need it, or do not know what it is. Although this metric contains the answer to such questions as how the client moves around the project and what the list of the most visited pages/screens and browsers is. Such information is highly appreciated by testers, as it helps to determine the priority of the error, see the growing conversion rate (as in my case), and also helps in sketching a strategy for test automation. These metrics strongly influence both the testing itself in the project and the rollout of the release, help to minimize the risks when planning technical works. It is important for testers to understand these metrics and be able to apply them on projects.