This is a type of error that is often found in code and data modeling. I haven't come across a name for it yet. It most definitely can and does fall through the cracks, in small, medium, and large organizations. It is a code smell and should be eliminated whenever it starts happening. However, it is often quite subtle, and a developer's ego is often stronger than the explanation for why it should not be done that way.
I shall dub it "Krystian's Overoptimistic Denormalization Error", or KODE for short.
I shall dub it "Krystian's Overoptimistic Denormalization Error", or KODE for short.