(Re)Building a Global Team: Tariq Khan at Tek Custom Case Solution & Analysis

Evidence Brief: Global Technology Solutions Case Data

1. Financial Metrics

• Tek operates as a multi-billion dollar global electronics entity with a complex cost structure distributed across regional hubs.
• The Global Technology Solutions (GTS) unit functions as a critical internal service provider where delays directly impact time-to-market for consumer electronics.
• Restructuring costs included significant severance packages and the closure of redundant regional offices, leading to a 15 percent reduction in headcount.
• Product delay penalties are estimated at 500,000 dollars per week for the upcoming flagship launch.

2. Operational Facts

• The GTS team is distributed across three primary time zones: Bangalore (India), Shanghai (China), and California (United States).
• Workflows rely on a 24-hour development cycle where code and designs pass between regions at the end of each local workday.
• GTS headcount post-restructuring stands at 120 engineers and project managers.
• Internal surveys indicate a 40 percent drop in cross-regional communication frequency since the reorganization.

3. Stakeholder Positions

• Tariq Khan (Director of GTS): Khan views the current friction as a temporary byproduct of the merger. He prioritizes output over cultural integration but recognizes the decline in velocity.
• Bangalore Lead: Expresses frustration over the lack of autonomy. Reports that the US team treats the India office as a back-office support unit rather than a strategic partner.
• Shanghai Lead: Concerned with the lack of clarity in technical specifications arriving from the US. Prefers hierarchical communication and feels bypassed by informal US-India chats.
• Executive Leadership: Demands the new platform launch within six months. They view GTS as a unified entity and ignore regional nuances.

4. Information Gaps

• The case lacks specific data on the attrition rate of high-performing engineers in the Bangalore office.
• There is no detailed breakdown of the budget allocated for cross-cultural training or travel.
• The exact software development methodology (Agile vs. Waterfall) used across the sites is not explicitly defined.

Strategic Analysis: Restoring Global Velocity

1. Core Strategic Question

• Can Tariq Khan rebuild the trust and operational cohesion of a fractured global team in time to meet a high-stakes product deadline?
• How can GTS move from a fractured collection of regional silos to an integrated global delivery model?

2. Structural Analysis

The primary issue is a breakdown in the 7S framework, specifically regarding Shared Values and Staff. The restructuring destroyed the informal networks that previously bridged cultural gaps. The current structure creates a parent-subsidiary dynamic rather than a peer-to-peer network. In Bangalore, the perception of being a low-cost resource creates resentment. In Shanghai, the lack of formal process causes confusion. The strategy of a 24-hour development cycle is failing because the handoffs lack context and mutual respect.

3. Strategic Options

• Option 1: Centralized Command. Move all critical decision-making and architectural design to the US office. Regional hubs execute specific modules with zero overlap.
  Trade-offs: Increases clarity but destroys morale and local innovation. High risk of losing top talent in India.
• Option 2: Regional Empowerment (Decentralization). Assign entire product lines to specific regions. Bangalore owns one product, Shanghai another.
  Trade-offs: Reduces handoff friction but creates knowledge silos and prevents a unified platform approach.
• Option 3: Integrated Global Matrix. Redefine KPIs to reward cross-regional success. Implement mandatory rotating leads for every major project phase.
  Trade-offs: Requires significant time investment in the short term but builds long-term scalability.

4. Preliminary Recommendation

Pursue Option 3. The current crisis is a failure of integration, not a failure of talent. Khan must pivot from a task-based manager to a culture-architect. Success requires shifting the incentive structure so that a US manager only succeeds if the Bangalore and Shanghai teams meet their local targets. This aligns the fragmented interests into a single operational goal.

Implementation Roadmap: 90-Day Integration Plan

1. Critical Path

• Weeks 1-2: Alignment Summit. Khan must convene the regional leads in a neutral location. The goal is to define the new Operating Model and set shared KPIs.
• Weeks 3-6: Process Standardization. Establish a single source of truth for technical documentation. Eliminate informal side-channels that exclude the Shanghai team.
• Weeks 7-12: The Pilot Project. Launch one high-priority module using a cross-regional sprint team with a rotating lead.

2. Key Constraints

• Time Zone Friction: The 12-hour gap between California and Bangalore is a physical constraint. Over-reliance on synchronous meetings will lead to burnout.
• Cultural Communication Styles: The directness of US feedback conflicts with the face-saving culture in Shanghai and the hierarchical structure in Bangalore.

3. Risk-Adjusted Implementation Strategy

The plan assumes the current staff will remain. To mitigate the risk of attrition, Khan must immediately implement a local recognition program in Bangalore that highlights strategic contributions, not just volume of work. For the Shanghai team, formalize the feedback loop to ensure they receive specifications 48 hours before work begins. This buffer allows for clarification without delaying the 24-hour cycle. Contingency: if the pilot project fails, Khan must be ready to temporarily move key engineers from India to the US to finish the product launch manually.

Executive Review and BLUF

1. BLUF

The GTS unit is at a breaking point. The restructuring has left a legacy of distrust and regional resentment that threatens the upcoming product launch. Tariq Khan must immediately shift from technical oversight to organizational repair. The recommendation is to move to an Integrated Global Matrix where performance metrics are tied to cross-regional cooperation. Failure to act now will result in a missed launch and the permanent loss of the high-value engineering talent in Bangalore. Speed and trust are the only metrics that matter in the next six months.

2. Dangerous Assumption

The analysis assumes that the regional leads are willing and able to change their management styles. If the Bangalore lead has already checked out or is planning to leave, no amount of KPI restructuring will save the project.

3. Unaddressed Risks

• Regulatory Risk: Changes in data privacy laws in China may restrict the flow of technical data between Shanghai and the US, breaking the 24-hour cycle.
• Competitor Poaching: Competitors are aware of the restructuring at Tek and are likely targeting the demoralized engineering staff in India with higher pay and better titles.

4. Unconsidered Alternative

The team did not consider a full divestment of the internal GTS unit in favor of a specialized external partner. If the internal culture is too damaged to repair, outsourcing the development to a third-party global firm would provide the necessary process discipline and remove the internal political friction immediately.

VERDICT: APPROVED FOR LEADERSHIP REVIEW