09
Back to Case Library

DESIGN CASE · PROPOSED / NOT IMPLEMENTED

When shared resources stopped being shared.

Diagnosed resource-governance failures in an anonymized fast-growing technology company’s matrix structure and proposed, but did not implement, a shared-capability and governance model.

DESIGN CASE · PROPOSED / NOT IMPLEMENTED
Case TypeDESIGN CASE · PROPOSED / NOT IMPLEMENTED
Evidence status

OBSERVEDANONYMIZED

01

Context

A fast-growing technology company had adopted a matrix structure combining multiple business units with shared functional teams.

02

Visible problem

Engineering resources assigned to individual business units had gradually become difficult to move across the organization, while business units competed for scarce specialists.

03

Signal

Interviews with business and functional leaders, and mapping of where organizational friction consumed capacity, identified de facto private shared resources, disconnected resource ownership and use, and functional KPIs insufficiently linked to business delivery.

04

Reframe

What appeared to be a communication problem was a resource-governance problem.

05

Diagnosis

Project management could track schedules but could not resolve cross-business resource conflicts, and management visibility increasingly influenced performance evaluation as the organization grew. The diagnosis was not that the matrix itself was wrong, but that it lacked the mechanisms required to work.

06

Design

The proposal retained the existing business-unit structure while adding a shared capability layer for common engineering and operational resources. It separated three roles—small business-facing front ends, shared capability platforms, and standardized corporate functions—and proposed four governance mechanisms: project value scoring, resource arbitration, dual performance accountability, and resource visibility. It also separated project contribution from functional performance and included recurring review for recalibration as real operating data accumulated.

07

Second-order consideration

The proposal documented its own limits: a centralized shared-capability layer could become another political resource center; quantitative coefficients would still contain judgment; time records could be distorted; and performance ratings would never become completely objective.

08

Reflection

The design premise was not to optimize for the theoretically perfect organization, but for the best organization that could actually be implemented.