Yes, we’re doing this successfully19%
Too early to say — we’ve just implemented AI UX tools62%
No, AI tools were not a good fit for UX10%
N/A, we haven’t tried this10%
90 Days17%
365 Days50%
3 years33%
5 years
7 years
Other (share in the comments)
No selling.
No recruiting.
No self promotion.
Rules of EngagementFAQsPrivacy
© 2025 Gartner, Inc. and/or its affiliates. All rights reserved.
Some clear indicators that a software engineering team may require an organizational redesign include:
- Excessively large teams that hinder agile performance
- Unclear or overlapping responsibilities across roles
- Misalignment of job titles with actual responsibilities
- Insufficient leadership for Centers of Excellence or Practice
- A proliferation of siloed teams and fragmented practices
To convince the C-suite, start by defining the specific organizational and performance issues currently limiting the team. Emphasize how these structural gaps impact performance, culture, and business outcomes. Support this case with a detailed plan that includes a career ladder aligned to defined job families, roles, reporting structures, and growth paths. Highlight the cultural benefits of the redesign, demonstrating how it would enhance both collaboration and team coherence across the department.