Since software teams facing similar challenges develop similar solutions, they will naturally accumulate redundant software artifacts. Data pipelines, queries, scripts, pieces of infrastructure, libraries, data definitions will repeat, or at least “rhyme” across verticals and business units.
They will also contain localized knowledge, experience, and valuable insights into the particular needs of their creators - needs that are not universal across the organization.
Standardization of tooling, lean technology stacks, common deployment infrastructure or centralized data definitions reduce total complexity and cost of software systems. However, they also introduce additional dependencies between teams, limiting the scope of decisions they can make autonomously.
Instead of trying to address redundancy right away, it is good to take a holistic inventory of what has been built so far, and assess whether there is enough value in consolidation. After all, team autonomy is valuable as well, and consolidation will have technical and organizational costs which are yet to be discovered.