Project X and Y at Hex_Tech-Team and Leadership Challenges - A Custom Case Solution & Analysis

Evidence Brief: Project X and Y at Hex_Tech

1. Financial Metrics

Project X Revenue Contribution: This legacy initiative accounts for 72 percent of total annual recurring revenue as noted in Exhibit 2.
Project Y Investment: Hex_Tech allocated 40 percent of the current fiscal year R and D budget to Project Y despite its zero revenue status as of the case date.
Operating Margins: Project X maintains a 22 percent margin while Project Y projections suggest a negative 15 percent margin for the first 24 months.
Headcount Costs: Project Y personnel costs per capita are 30 percent higher than Project X due to specialized talent requirements mentioned in Paragraph 14.

2. Operational Facts

Development Methodology: Project X utilizes a traditional Waterfall process with 6 month release cycles. Project Y operates on a continuous deployment Agile model.
Resource Overlap: 15 percent of the engineering staff are shared between both projects leading to 20 percent reported overtime in the last quarter (Paragraph 22).
Geography: Project X leadership is based in the primary headquarters while the Project Y core team is located in a satellite innovation hub 200 miles away.
Tooling: The teams use incompatible project management software which prevents a single view of resource utilization as shown in Exhibit 4.

3. Stakeholder Positions

Mike (Team Leader): Believes Project Y is the future but feels obligated to protect the cash flow of Project X. Stated in Paragraph 8 that he feels torn between two masters.
Sarah (Project X Lead): Expresses resentment regarding the resource drain toward Project Y. Claims her team is treated as a legacy burden despite funding the company.
David (Project Y Lead): Views Project X processes as bureaucratic and a threat to the speed required for market entry.
The Board: Demands 15 percent growth in Project X while expecting Project Y to launch by the end of Q4.

4. Information Gaps

Market Size: The case does not provide external market validation for the Project Y technology.
Customer Feedback: There is no data regarding whether Project X customers are willing to migrate to the Project Y platform.
Competitor Response: Data on rival firms working on similar technologies to Project Y is absent.

Strategic Analysis

1. Core Strategic Question

The primary dilemma is how to balance the operational stability of a high-revenue legacy product with the high-velocity requirements of a disruptive innovation.
The secondary problem involves resolving the cultural friction and resource competition between two teams with divergent methodologies and incentives.

2. Structural Analysis

Applying the Ambidextrous Organization Framework reveals the following:

Exploitation (Project X): The company is successfully exploiting its current market but doing so with declining morale and resource starvation.
Exploration (Project Y): The innovation track is isolated and lacks the institutional support needed to scale.
Structural Misalignment: Hex_Tech is attempting to run two different business models under a single management structure without clear differentiation in KPIs or culture.

3. Strategic Options

Option 1: Complete Structural Separation

Rationale: Spin off Project Y into a separate business unit with its own P and L and leadership.
Trade-offs: Reduces friction but loses the ability to share technical knowledge or customer relationships.
Resource Requirements: Separate HR, Finance, and Marketing functions for the new unit.

Option 2: Hybrid Integration (Recommended)

Rationale: Maintain distinct development teams but create a unified executive layer to manage resource trade-offs.
Trade-offs: Requires high management capability to balance competing interests; may not fully resolve cultural tension.
Resource Requirements: A dedicated resource manager and a shared incentive pool based on total company performance.

Option 3: Rapid Convergence

Rationale: Force Project X to adopt Project Y methodologies and begin immediate migration of customers.
Trade-offs: Highest risk of revenue loss if the transition fails; likely to cause high turnover in the Project X team.
Resource Requirements: Intensive retraining and a significant increase in customer support.

4. Preliminary Recommendation

Hex_Tech should pursue Option 2: Hybrid Integration. The company cannot afford the overhead of a full spin-off, nor can it risk the revenue of Project X through forced convergence. Success requires Mike to step back from day-to-day management of either project and instead act as an arbitrator of resources and a bridge between the two cultures.

Implementation Roadmap

1. Critical Path

Phase 1 (Days 1-30): Establish a Resource Allocation Committee. Define clear, non-overlapping KPIs for both teams. Project X KPIs focus on margin and retention; Project Y KPIs focus on development milestones and beta user acquisition.
Phase 2 (Days 31-60): Implement a shared technical architecture board. This group will ensure that Project Y is built in a way that allows for eventual migration of Project X data, preventing future technical debt.
Phase 3 (Days 61-90): Launch a cross-training program. Rotate 5 percent of staff between projects to build empathy and transfer knowledge.

2. Key Constraints

Leadership Bandwidth: Mike is currently overextended. Failure to delegate operational control of Project X will stall the entire transition.
Incentive Misalignment: If Project X bonuses remain tied only to their own revenue, they will continue to hoard resources. The bonus structure must include a component of company-wide success.

3. Risk-Adjusted Implementation Strategy

The strategy assumes a 15 percent attrition rate in Project X during the methodology shift. To mitigate this, Hex_Tech must identify 10 key engineers in Project X and offer retention bonuses tied to a 12 month window. Contingency plans include a pool of contract developers ready to step in if turnover exceeds 20 percent. The timeline will be extended by 4 weeks if the technical architecture board identifies significant compatibility gaps in Month 2.

Executive Review and BLUF

1. BLUF

Hex_Tech must immediately transition to a hybrid management model. The current structure forces Project X to fund its own obsolescence while starving Project Y of the focus needed to launch. Mike must delegate the operational management of Project X to a deputy and assume a strategic oversight role. Failure to separate the incentives and methodologies of these two units will result in the stagnation of Project Y and the collapse of Project X morale. The objective is to stabilize the 72 percent revenue base while securing the future growth engine through disciplined resource arbitration.

2. Dangerous Assumption

The analysis assumes that the Project X customer base is willing to transition to the Project Y platform once it is ready. If the market prefers the legacy Waterfall-style stability over the new Agile-driven features, the entire investment in Project Y becomes a stranded asset.

3. Unaddressed Risks

Talent Flight: High probability. Specialized engineers in Project Y may leave if they feel the legacy culture of Project X is slowing their progress. Consequence: 6 month delay in launch.
Revenue Cannibalization: Medium probability. If Project Y is launched without a clear pricing strategy, it may pull customers away from the higher-margin Project X prematurely. Consequence: 10 percent drop in overall margin.

4. Unconsidered Alternative

The team did not consider a Strategic Partnership or Acquisition. Instead of building Project Y internally, Hex_Tech could have acquired a smaller firm with the technology. This would have allowed the internal team to focus entirely on maximizing the tail of Project X revenue while the acquired entity operated independently with its own culture and speed.