The Optimal Team Topologies Strategy for Legacy Modernization

Legacy modernization is a complex challenge, but the right Team Topologies strategy can significantly enhance efficiency and success. This article explores the most effective approach, backed by industry data, trends, and real-life case studies, to guide your organization through modernization.

The Four Key Team Topologies for Legacy Modernization

Based on industry best practices and success stories, the ideal Team Topologies strategy for legacy modernization teams typically involves a combination of:

• Stream-Aligned Teams – The frontline of modernization
• Platform Teams – The foundation that accelerates the process
• Enabling Teams – The catalysts that bridge old and new systems
• Complicated Subsystem Teams – Specialists for highly complex components

Let’s break down each one, supported by industry insights and real-world examples.

Stream-aligned Teams: The Modernization Frontline

Role: Focus on specific parts or functions of the legacy system.

Key Benefits:

• Improved focus and faster delivery
• Better alignment with business goals

Real-Life Example: Retail

At Footasylum, a UK-based fashion retailer, the transition to stream-aligned teams addressed issues of siloed knowledge and slow delivery that had emerged as the company grew rapidly. By organizing teams around clear business domains like e-commerce, retail, and warehousing, Footasylum was able to give teams clearer purpose and autonomy.

Industry Numbers:

• McKinsey: Companies aligning roles to transformation goals are 1.5x more likely to succeed.
• Gartner: By 2024, 80% of tech products will be built by non-tech professionals, reinforcing the need for business-aligned teams.

Platform Teams: The Modernization Foundation

Role: Provide infrastructure, tools, and services to streamline modernization.

Key Benefits:

• Standardization of modernization practices
• Acceleration of the modernization process

Real-Life Example: Insurance

The Norwegian insurance company Gjensidige has created several platform teams to accelerate delivery by their stream-aligned teams. These include platforms for design, analytics, web applications, CRM, and DevOps tooling.

Industry Numbers

• Companies with platform teams report a 20-50% faster feature delivery.
• State of DevOps Report: Strong platform teams reduce downtime to less than a day.

Enabling Teams: The Modernization Catalysts

Role: Support stream-aligned teams with specialized knowledge and facilitate technology adoption.

Key Benefits:

• Faster knowledge transfer
• Improved adoption of new technologies and practices

Real-Life Example: Health

PureGym started with short-term project teams, then moved to longer-lived but still temporary teams, before finally adopting stable stream-aligned product teams supported by platform and enabling teams. Each step brought improvements, but the final Team Topologies-inspired structure delivered the greatest benefits in terms of ownership, speed, and quality.

Industry Numbers

• Organizations with dedicated enabling teams report a 28% increase in developer productivity.
• Companies using enabling teams see a 23% reduction in time-to-market for new features.

Complicated Subsystem Teams: The Modernization Specialists

Role: Handle complex, mission-critical legacy components that require deep expertise.

Key Benefits:

• Specialized handling of intricate legacy components
• Reduced risk in modernizing critical, complex subsystems

Real-Life Example: Banking

In a large Dutch Bank, the IT department consisted of specialized component teams. There is a huge variety of tools, applications, products, and systems in use. And they had not yet succeeded in simplifying the architecture and infrastructure. The core banking systems, for example, are old and very specific. It makes no sense and the risk is high for all teams to learn these systems. For these environments, the choice was to establish complicated subsystem teams.

When to Use this Approach

• For legacy systems with highly complex, mission-critical components.
• When specific parts of the system require specialized knowledge that can't be easily distributed.

Balancing Team Topologies: When Not to Use All Four

Not every modernization effort needs all four team types. Consider:

• Organizational Size and Complexity: Smaller organizations may not have the resources or need for all team types.
• Project Scope: Some modernization projects may be straightforward enough to manage with just stream-aligned and platform teams.
• Legacy System Characteristics: Not all legacy systems have components complex enough to warrant dedicated complicated subsystem teams.

Potential Pitfalls and Change Management

Common Challenges

• Cultural Resistance: Employees may resist changes to established processes. Fostering a culture of innovation and continuous learning is essential to mitigate this.
• Skill Gaps: Legacy systems often require skills that may not exist within the current workforce. Investing in training and upskilling is crucial.

Change Management Strategies

• Leadership Support: Ensure that leadership is visibly supportive of modernization efforts and communicates its importance to the organization.
• Employee Involvement: Involve employees in the modernization process to gain buy-in and reduce resistance.

Next Steps to Ignite Your Legacy Modernization Journey

• Assess Your System – Map dependencies, identify risks
• Set Goals – Define objectives & KPIs
• Choose Teams – Align structure to needs
• Train & Equip – Upskill teams, adopt AI tools
• Run a Pilot – Test on a low-risk system
• Refine & Iterate – Hold retrospectives
• Foster Innovation – Celebrate progress

To gauge the impact of your Team Topologies strategy, track key metrics such as:

• Time-to-market for modernized features
• Reduction in legacy system dependencies
• Increase in development velocity
• Improved system reliability and performance

By aligning your approach to your organization's unique needs, you can drive a seamless and impactful modernization journey. Embrace the transformation and turn legacy systems into agile, future-ready assets.

---