So part of my job involves reviewing existing applications from a UX perspective and then take a consultative approach and suggest improvements. This task however runs in parallel with other teams who also review the application but from other perspectives like functionality, performance, security etc. All teams work pretty much in silos.
Recently I came across an application where the user would receive some data from multiple sources (cannot provide specific data as it's all proprietary). This data is then tweaked using the application and then a final report is generated. Basically once the user is satisfied with the tweaked data, a button needs to be clicked and a PDF report would be automatically generated.
While reviewing the application, I realized that the report did not display some of the data appropriately. Basically if part of the data was 'x' and the user changed it to 'y', the report would still reflect 'x'.
I documented this as a UX issue, however my boss said that while this would affect the user experience, it should be categorized as a functional issue rather than a UX issue as it only means that the application isn't functioning appropriately.
While I agree with his point, I still felt it could also be categorized as a UX issue because the user would be performing a set of tasks to accomplish a certain goal(in this case generating the report). However, when the report is not the way the user expected it to be, it would lead to frustration.
This thought got me thinking further, all issues, whether functionality, performance, security, compatibility would all directly or in some cases indirectly affect User Experience. Hence any and every issue in an application could have a UX angle to it.
So in such cases, how does one define the scope of UX as compared to other facets of the application like security, functionality etc.
I understand this could be a little broad and subjective, hence to make it a little more objective I've reworded and made it a little more specific below
Are there any standard parameters / principles / rules of thumbs in distinguishing an issue a UX or non UX one
Has there been any research / paper / article written around this area
While answers for all contexts are welcome, this question focuses more only for scope when it comes to tasks like review and assessments.