What is consolidating on tunes
Are they sharing outputs like code libraries, documentation, design asset libraries? If you are considering consolidating, the first step is compare and rationalize differences.Your objective: help makers, customers, and sponsors get a sense of how things differ and could change as a result.Other times, systems keep experiences and teams apart. So an approach to consolidation is best shared, rational, and yet also decisive.
Yet change will be slow and and lack authoritative oomph.Is the acquired product community and system team willing to yield to the design, code and documentation already on offer? Are organizational units migrating to a new system willing to engage regularly and drive change so teams use the system, faithfully? Will a shared cost model work for previously independent sponsors, or will the team drift towards one or the other existing cost center, biasing the results?