It came a bit accross like that 
Then the planning ahead opportunity is already missed. If it was foreseeable that the teams might share resources, have them start with the same structures.
Im sure at Epic they have a strict set of guidelines on how how to even name assets.
In this case, I would have made both teams use a common structure. If it really that specific for each team, they could use a single folder in their content structure root, called “TeamA”, and “TeamB” for the orher team. When they toss things back and forth, they both have a “TeamA” and a “TeamB” folder in their root.
If TeamB gets stuff from TeamA and they move it around, they should immediately run the “Fixup redirectors” command.