I am not disagreeing with your reading of the article, but adding on my own interpretation, as this general advice is tossed around on multiple teams I work wit

I am not disagreeing with your reading of the article, but adding on my own interpretation, as this general advice is tossed around on multiple teams I work with. The way I see this is not as a diktat, but as an acknowledgement that if you find a problem, you have enough domain knowledge to be able to contribute to a solution, and the fact that you are the first to identify the problem lends evidence to support the fact that you understand (at least a portion of) the source of the problem better than your team. Don't pass the buck by reporting the problem and assuming it will be fixed. Take the time to fix it to improve things for you and for your team. Obviously there is a huge range of appropriate responses, but I think keeping this sort of understanding is important. A problem that you identify is a problem in something that at least touches your team's primary responsibility.