> If the new common dependency is consumed by different projects with different pressures for change / different rates of change / different levels of software quality then factoring out a common idea that then introduces coupling may cause more harm than good.

This reminds me of the recent post on HN about a company migrating from microservices back to a monolith, for this exact reason.