Core competence is the foundational concept of Prahalad's strategic framework, introduced in a 1990 Harvard Business Review article co-authored with Gary Hamel. The argument reordered how organizations understood competitive advantage: durable success derives not from products or market position but from the collective learning embedded in an organization's capacity to coordinate diverse production skills and integrate multiple technology streams. The key word was collective — competence did not reside in any individual engineer, any single patent, or any particular product line. It resided in the patterns of coordination between people, in the organizational memory that enabled a company to do things its competitors could not replicate.
The canonical examples Prahalad marshaled remain diagnostic. Honda's core competence was not engines but the organizational capacity to apply engine expertise across motorcycles, automobiles, lawnmowers, and generators — a capacity residing in the ability to transfer learning across product boundaries. NEC's competence was not semiconductors or telecommunications equipment but the organizational capacity to integrate computing and communications technologies, requiring hundreds of engineers across dozens of divisions to collaborate in ways that silo-organized competitors could not replicate. Canon's competence in optics, imaging, and microprocessor controls allowed entry into markets as diverse as cameras, copiers, and laser printers.
Prahalad and Hamel proposed three tests for identifying core competence. First, it provides potential access to a wide variety of markets. Second, it makes a significant contribution to the perceived customer benefits of the end product. Third, it should be difficult for competitors to imitate. Applied to the Trivandrum team described in The Orange Pill, all three tests are satisfied with a precision Prahalad could not have anticipated in 1990.
The distinction that matters most for the AI transition is between individual skill and collective capacity. A tool has arrived that multiplies individual productivity by factors that make existing headcount appear extravagant to the arithmetically inclined. But the multiplier is not a property of the tool. It is a property of the interaction between the tool and the collective capacity of the team that wields it. Give identical tools to twenty strangers with equivalent individual skills but no shared history, and the multiplier collapses to a fraction.
The 1990 HBR article emerged from a decade of Prahalad's research on diversified Japanese corporations, whose systematic outperformance of American conglomerates in the 1980s resisted explanation through the dominant strategic frameworks of the period. Prahalad and Hamel proposed that the Japanese advantage was organizational rather than technological — a different way of accumulating and deploying collective learning across divisional boundaries.
Collective, not individual. Core competence resides in patterns of coordination between people, not in any single expert.
Cross-functional integration. The capacity to combine skills across traditional boundaries is what makes competence strategically valuable.
Three tests. Market access breadth, customer benefit contribution, and imitation difficulty distinguish core competence from ordinary capability.
Invisible to accounting. The asset cannot be measured, which is why it is the first asset destroyed when financial optimization is the metric.
Foundation of AI strategy. The productivity multiplier is a property of collective capacity directing the tool, not of the tool itself.
Critics have argued that core competence is unfalsifiable — identified only retrospectively after success has been achieved. Defenders respond that the framework's predictive power lies in diagnosing why certain organizations can enter new markets while others cannot, a test the AI transition is running in real time.