You're advising an engineering organization where different teams have adopted different tools for source control workflows, CI/CD, observability, and project tracking. Leadership is feeling the cost in onboarding, support, compliance reviews, and cross-team collaboration, but teams argue that local choice helps them move faster and fit tools to their needs.
How do you decide whether to standardize on a common tool or let teams choose their own?
Local team productivity can conflict with enterprise efficiencyHidden costs sit outside license spend, especially support and governanceDifferent tool categories warrant different policiesClient constraints can make full standardization unrealistic