Core Competence
Core Competence
What is core competence?
- Not the product, but the root capability beneath it
- Three conditions: value, hard to imitate, extensible
- A compass for new business direction
What a core competence discussion really changes is how you read the org chart. Meetings that used to start with “what business are we in?” shift to “what capabilities are we selling?” Once that shift happens, you begin re-cutting the company by capability instead of by business unit. Design staff tied to a single unit are reclassified as company-wide assets, and a business that is small in revenue but builds that capability survives. The practical result is a change in where budget and top talent flow.
A capability must pass three tests to be called a core competence: Does it directly touch the reason customers pay? Would it be hard for competitors to catch up within three years? Can it move across multiple markets rather than serve a single product? In practice, the third test screens out the most. Responsiveness that works only for one particular client is a good thing to do well, but it is not a core competence. Prahalad and Hamel also held that even a very large company can build only five or six world-class competencies. If you cannot cut the number, you are left with a declaration while resource allocation stays the same.
Drawing a line between neighboring concepts speeds up the discussion. Key success factors (KSF) are conditions every player needs just to survive in an industry, so they can’t justify differentiation. Where VRIO’s resources ask “what do we have?”, a core competence asks about how you combine multiple resources to deliver results again and again. Equipment and patents can be bought and sold, but the combination of people, processes, and decision-making habits that put them to use cannot be traded. That is why competitors can install the same equipment and still miss the yield.
The most common failure in practice is a list that grows past ten items. Once “good quality” and “on-time delivery” make the list, you have effectively chosen nothing. Riskier still is retroactively approving the capabilities of the biggest business unit as core competencies, which turns the document into an alibi for the status quo. The opposite mistake is just as common: a process labeled “non-core” in a cost-cutting project and outsourced turns out to have been the root. Years later, when you try to bring that technology back in, the people and data are gone, and your partner has become a competitor.
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum Consulting
Ara LimSpecialist in global leadership, AI, and business communicationC.K. Prahalad and Gary Hamel introduced it in their 1990 Harvard Business Review article “The Core Competence of the Corporation.”
Consider a hypothetical case. Company A is a tier-2 auto parts supplier with annual revenue of KRW 140 billion (≈ US$104,743,400) and 320 employees. Over the past three years it put a combined KRW 8 billion (≈ US$5,985,300) into three new businesses (electronic modules, logistics automation, and industrial heaters) and exited all of them. At a management meeting, the CEO asked, "We tried everything that looked promising, so why do we have nothing to show for it?" The strategic planning team launched an eight-week core competence assessment.
- When the head of strategy planning asked 11 business unit heads what “we do better than others,” 37 items came back, and 22 of them were phrases any company uses, like quality, on-time delivery, and responsiveness.
- The head of sales visited the purchasing teams at six key clients in person. Five gave the same reason for reordering: "Even when the drawing changes, they revise the mold and get us samples within two weeks."
- When the head of production engineering traced the source of that speed, it wasn’t the equipment. It was 15 years of revision history data built up by keeping the mold design team and the test line on the same floor. Buying machines wouldn’t replicate it.
- Re-examining the three abandoned new businesses against that standard, not one had used this capability. The CEO summed it up: "We chose by looking at the market, not at our roots."
- They narrowed their competence to one thing, 'speed of developing high-mix, low-volume molds,' and reallocated 60% of the R&D budget and 9 design engineers. Six months later, prototype lead time fell from 18 days to 11, and two new medical device component orders worth KRW 2.4 billion (≈ US$1,795,600) came in.