What is Core Competencies?
Prahalad and Hamel (1990) defined a core competency as a bundle of integrated skills, technologies, and knowledge streams that provides three benefits: (1) access to a wide variety of markets, (2) contribution to perceived customer benefits, and (3) difficulty for competitors to imitate. They argued firms should think of themselves as a portfolio of competencies, not a portfolio of businesses. The classic example: Honda's competency in small engines underlies cars, motorcycles, lawnmowers, generators, and outboard motors — seemingly unrelated businesses unified by one competency. The implication: invest in the competency, not just in individual product extensions.
How Core Competencies actually works
The framework breaks down into the following moving parts. Knowing what each piece is — and what it is not — is what separates a B-grade answer from an A-grade answer in a written assignment.
- Test for market access — does it open multiple markets?
- Test for customer benefit — do customers care about the underlying capability?
- Test for imitation difficulty — can competitors replicate within five years?
- Map competencies to businesses to find leverage
- Invest at the competency level, not the business unit level
A worked example: Honda
Honda's small-engine competency underlies businesses across cars, motorcycles, lawnmowers, generators, outboard motors, and snowblowers. The combustion-engineering knowledge, the manufacturing precision, and the supply-chain relationships all transfer. Customers in each market benefit (reliability, fuel efficiency). Competitors cannot easily replicate the competency without decades of investment. Honda's ability to enter and dominate adjacent markets — most famously the US motorcycle market displacement of Harley-Davidson in the 1960s — flows from the competency, not from any one product.
Don't lose marks for these
- Confusing core competency with capability or asset
- Listing too many "core" competencies (3–5 maximum)
- Over-leveraging a competency into businesses where customers do not value it
How to use this on the exam
Score-maximizing moves
- Cite Prahalad & Hamel 1990
- Apply the three tests
- Map to multiple businesses
When to use Core Competencies (and when not to)
Use Core Competencies when your assignment asks you to analyze, structure, or recommend — and when you have at least two data points to populate every cell of the framework. Skip it when the question is asking for a numerical answer or a single recommendation, since Core Competencies is a structuring tool, not a calculator.