@al3xicon @llfcf as a former member of N, I do agree with your sentiments. There's just a lot of politics going on like in any other company. It really boils down to the business impact of N. Like 100 complaints of a certain functionality may not be prioritized but a problem reported by a single client that is account specific may do cause it is critical to N's performance. You might be surprised to know that some features introduced are really because of a demand from big clients. Internally, there's an assessment done on the severity of the issue, which is the basis for resource prioritization of QA engineers in fixing these bugs - so if there's not much detailed justification placed by the support rep or team filing the issue in behalf of the client, QA/DEV would not even bother looking at it. That's where support's role becomes critical. Well for performance issues, it has been a long standing problem for N since 2013 when the volume of performance related issues tend to be more recurrent up until now. If you are keen enough, N framework is really similar to Quickbooks when it started so a lot of core functionalities overtime had to be remodelled which requires certain backend tweaks and 'behind the scenes' changes that are mostly internal - One of the biggest challenges in Prod Dev. in N is coping up with making sure how these changes may impact certain functionalities cause as they grow bigger; one Prod Dev. team may not be aware of what the other Prod Dev. team's project is.