TDC Group: New Ways of Working Custom Case Solution & Analysis

1. Evidence Brief

Financial Metrics

• Acquisition Value: TDC Group was acquired for approximately 40 billion DKK in 2018 by a consortium led by Macquarie and three Danish pension funds.
• Revenue Profile: Nuuday reported 14.8 billion DKK in revenue for 2020, representing a decline of 3.4 percent compared to the previous year.
• EBITDA Performance: Nuuday EBITDA stood at 4.2 billion DKK in 2020, a 2.5 percent decrease from 2019.
• Cost Reduction Targets: The group aimed for significant operational expenditure reductions to service the debt incurred during the 2018 leveraged buyout.
• Investment in Transformation: Significant capital was allocated to the separation of TDC into two distinct entities: Nuuday (services) and TDC NET (infrastructure).

Operational Facts

• Organizational Split: The company underwent a legal and functional separation into Nuuday (customer-facing brands) and TDC NET (physical network and wholesale).
• Agile Scale: Nuuday implemented the Spotify model, organizing over 3000 employees into approximately 350 squads and 10 tribes.
• Legacy Systems: The IT environment consisted of over 600 legacy systems, many over 20 years old, creating significant technical debt.
• Productivity Gap: Prior to the transformation, product development cycles for new features averaged 6 to 12 months.
• Workforce Composition: High reliance on external consultants for IT maintenance, with a strategic push to insource digital talent.

Stakeholder Positions

• Michael Moyell Juul (CEO, Nuuday): Champion of the agile transformation; views the shift as a survival necessity against digital-native competitors.
• Jens Munch-Hansen (Senior Executive): Focused on the operational decoupling of the two business units and ensuring service continuity during the transition.
• Macquarie and Pension Funds (Owners): Demand rapid efficiency gains and a clear path to value realization to justify the acquisition premium.
• Middle Management: Often described as the frozen middle, experiencing role ambiguity as traditional command-and-control structures are dismantled.
• Front-line Employees: Mixed reception; some embrace the autonomy of squads, while others struggle with the lack of clear hierarchy and increased accountability.

Information Gaps

• Customer Retention Data: The case lacks specific churn rates during the transition period to measure if internal upheaval affected customer experience.
• IT Decoupling Costs: Specific budgetary allocations for the 600 legacy system migrations are not detailed.
• Competitor Response: Limited data on how Danish competitors like Telenor or Telia adjusted their strategies in response to Nuudays reorganization.

2. Strategic Analysis

Core Strategic Question

How can Nuuday successfully transition from a legacy telecommunications incumbent to a software-led service provider without the massive technical debt of its 600 legacy systems causing a total collapse of operational speed and service reliability?

Structural Analysis

Applying the McKinsey 7S Framework reveals a profound misalignment between new Strategy/Structure and old Systems/Skills:

• Structure vs. Systems: The new squad-based structure (Agile) is designed for speed, but the underlying Systems (600 legacy platforms) require slow, centralized management. This creates a friction point where squads are empowered to decide but unable to execute.
• Strategy: The shift to a digital-first service provider requires decoupling from infrastructure (TDC NET). However, the shared IT history makes clean separation difficult.
• Skills: The workforce is transitioning from telco-engineering to software-product mindsets. The gap in digital native talent remains a critical bottleneck.

Strategic Options

Preliminary Recommendation

Nuuday should adopt the Platform-First Decoupling strategy. The current agile implementation is a cultural success but an operational failure because squads are tethered to monolithic IT. By focusing the next 12 months on building an abstraction layer (APIs) over the 600 legacy systems, Nuuday enables true squad autonomy. This path accepts a temporary slowdown in new product launches to ensure that future development is not permanently hindered by technical debt.

3. Implementation Roadmap

Critical Path

The transformation must pivot from organizational design to technical enablement. The following sequence is mandatory:

• Month 1-3: Architecture Audit and API Layering. Identify the top 20 legacy systems that handle 80 percent of customer transactions. Task specialized tribes with building API wrappers to allow squads to access data without modifying the legacy core.
• Month 4-6: Middle Management Re-skilling. Transition former department heads into Chapter Leads and Product Owners. Focus training on backlog prioritization and removing blockers rather than task assignment.
• Month 6-12: Gradual IT Insourcing. Reduce reliance on external vendors by 30 percent. Redirect those funds to hire internal full-stack developers who will own the new modular architecture.

Key Constraints

• Technical Debt: The 600 legacy systems act as a gravity well. Any implementation plan that assumes squads can move at Spotify-speed without fixing the back-end is unrealistic.
• Talent Scarcity: Copenhagen is a competitive market for developers. Nuudays legacy reputation may hinder the recruitment of the high-caliber talent needed for the decoupling.

Risk-Adjusted Implementation Strategy

To mitigate the risk of service disruption, Nuuday must implement a Shadow Backend approach. New digital features should be built on the new cloud-native platform while the legacy systems continue to run in parallel. Only when the new layer proves stable should the legacy system be retired. This doubles the short-term maintenance cost but prevents a catastrophic failure of core billing or provisioning systems that would alienate the customer base.

4. Executive Review and BLUF

BLUF

Nuuday is attempting to solve a structural IT problem with a cultural solution. While the shift to 350 agile squads has improved employee engagement, it has not yet yielded the required gains in speed to market. The primary bottleneck is the 600 legacy systems that prevent squads from being truly autonomous. Nuuday must pivot its focus from organizational rituals to technical decoupling. Without an API-led architecture, the agile model is merely a veneer over a slow, traditional incumbent. The recommendation is to prioritize back-end modernization over further squad expansion. This is the only path to achieving the efficiency targets demanded by the ownership consortium.

Dangerous Assumption

The analysis assumes that the organizational split between Nuuday and TDC NET will automatically lead to operational efficiency. In reality, the two entities remain deeply intertwined through shared legacy IT. If TDC NET does not modernize the infrastructure at the same pace Nuuday modernizes its services, Nuuday will remain trapped by its partners technical limitations.

Unaddressed Risks

• Risk 1: Cultural Fatigue. The scale of the change (3000 people) is massive. There is a high probability (60 percent) that the workforce will experience transformation burnout before the technical benefits are realized, leading to the loss of key talent.
• Risk 2: Debt Service Pressure. The leveraged buyout structure requires immediate cash flow. If the transformation takes longer than 24 months to show margin expansion, the owners may pivot to aggressive cost-cutting that dismantles the agile experiment entirely.

Unconsidered Alternative

The team did not consider a Spin-off and Re-acquire strategy. Nuuday could have launched a completely separate, greenfield digital brand (built on modern cloud architecture) while slowly migrating customers from legacy brands. This would have avoided the friction of trying to transform a 3000-person organization and 600 legacy systems simultaneously.

VERDICT: APPROVED FOR LEADERSHIP REVIEW