As you pointed out in the question, there are a number of reasons why this happens and there are any number of formal or informal ways to describe it, so perhaps I can suggest some here and see if other people in the community would like to add to it.
Teams/individuals not talking to each other = working in silos
Deficiencies in the handover process resulting in gaps = throwing
something over the fence
Differences in the maturity/skill level of teams = delivery team
I would say that what you are essentially describing also covers the fact that the first part of the double diamond process is intended to find the 'right problem to solve' which is about coming up with the root cause of a problem or identify an opportunity, and the second part of the double diamond is about 'solving the problem right', which is about designing and building to the specifications.
That means there could also be incorrect assumptions made in the initial research process or perhaps changes or differences in the requirements during the delivery process (e.g. UI was designed and tested on faster hardware and pushed to less capable hardware).