# Core Competencies The core competencies framework finds the deep proficiencies that are hard to copy and that can be reused across more than one product. **The question.** Which of our skills do customers notice in what they buy, and could we use them to build products in markets we are not in? Also known as: Also written core competence, the form used in the original article's title. ## When to use it - A diversified client holds business units that share only a parent, and the center has to decide what it adds. - A firm wants to enter an adjacent market and has to say why it would have a right to win there. - Divestment or outsourcing of an activity is proposed, and nobody knows whether other products depend on it. - Budget cuts are being applied evenly across units and could remove a skill that several products rely on. ## When to avoid it - The client sells one product. The exercise collapses into an ordinary capability review, and a plain list of what the team does well will serve. - The question is how to price or position an existing offer. Market tools answer that, and competencies do not. - Management wants a label for what it is good at. The word "core" gets attached to anything, and the exercise produces a flattering list. Use a plain capability audit, or no framework. - The decision has to be made this quarter. Competencies take years to build or redirect, so the framework is for decisions with a longer horizon. ## Overview Prahalad and Hamel used core competence to describe a bundle of skills and technologies that runs through several of a company's products and that customers can see in the result. The idea supports corporate-level choices: which activities to invest in, which to outsource or sell, and which adjacent markets the firm has a right to enter. A core competence is narrower than a strength. It has to open many markets, make a visible difference to customers, and be hard for competitors to copy, and most firms have only a handful that pass. The usual misuse is a long list of virtues produced in a workshop. Treat any list longer than a few items with suspicion. ## The tests and the link to products ### Access to many markets Prahalad and Hamel's first test. The competence should open the way to a wide variety of markets, and not serve a single product. A skill used by only one product line is a specialty of that line. ### A visible benefit to the customer The competence has to make a real contribution to what the customer values in the end product, such as precision, speed, or reliability. If customers would not notice the difference, it may be efficient, and it is not core. ### Hard for competitors to copy It is usually a combination of skills, technologies, and organizational learning, which is hard to reproduce by hiring one person or buying one machine. Ask how long a well-funded rival would need, and what it would cost. ### Core products The physical embodiment of the competence, such as a component or platform that feeds many end products. Core products are the link between a skill and the products customers buy, and they show where the competence is held and who has to fund it. ## What it is not - Something the firm is good at. Many things done well, such as payroll or compliance, fail the first and third tests. The original meaning is often diluted to "our strengths." - A capability in the narrower sense some authors use. Terminology varies. Some use competence for the skill and capability for the management ability to turn skills into products. Agree the terms with the client before you start. - A property of a business unit. Prahalad and Hamel meant something shared across the corporation, which is why the center, and not a single unit, has to manage it. ## The steps 1. **List what the firm can do.** Write skills and technologies as verbs, for example "design miniature motors," and not as products or units. Draw them from engineers and operators as well as from executives. You should have a list of fifteen to thirty. 2. **Map skills to the products that depend on them.** Build a grid of skills against products and units. Skills used by only one product fall out of the running. Skills used by several, especially where the units do not know about one another's use, are the candidates. 3. **Apply the three tests.** For each candidate, ask whether it opens many markets, whether customers notice its effect in the end product, and how hard it would be for a rival to copy. Use customers, win-loss data, and price premiums as evidence. Expect only a handful to survive. 4. **Name the core products and their owners.** Identify the component or platform that carries each surviving competence into products, and who funds and staffs it today. If the answer is "each unit separately," note that as a finding. 5. **Decide where to invest and where to stop.** Concentrate investment and the best people on the surviving competencies. Check each candidate adjacent market against them before entering it, and look at outsourcing or divesting activities that serve none of them. 6. **Check for rigidity.** Ask what would make each competence obsolete, such as a shift in customer demand or a new technology, and whether the competence is narrowing what the firm looks at. Set a date to review the list again. ## In practice The board of a diversified industrial group had agreed to sell its smallest division, a maker of industrial scales, because it earned little and shared no customers with the rest of the group. The consultant built a grid with skills down the side and products across the top. The scales team turned out to be the group's main source of precision sensing know-how, which three other divisions used in their own products, though none of them paid for it. The sale, as drafted, would have handed that skill to a buyer and left three divisions to rebuild it. The board kept the sensing engineers as a shared unit funded by the three user divisions, and sold the rest of the scales business with a licensing agreement. Nobody had listed sensing as a strength, because it did not appear in any division's accounts. ## What you leave with - A grid of skills against products and units. - A short list of competencies that pass all three tests, with the evidence for each. - A list of core products, and who owns and funds each. - A set of decisions on what to protect in a budget cut or divestment, which adjacent markets are open, and what to stop doing in-house. ## Failure points ### Core by proclamation The list comes out of an offsite and reads "customer focus," "innovation," "people." None of it has been tested, because no one built the skills-to-products grid. The result is a statement of values. ### Competence owned by a unit Each business unit protects its best people, so the competence is treated as a unit asset and cannot be moved to where it is needed. The P&L structure rewards the hoarding. This is the problem Prahalad and Hamel were writing against. ### Searching only where the competence applies The firm enters markets because it can use its skill there, without checking that customers value it. The second test fails quietly, and the firm builds products nobody asked for. ### A core rigidity A competence that served the firm well becomes a barrier when technology or demand shifts, because the organization is built to protect it. Leonard-Barton described this in 1992. Ask what would make the competence stop mattering. ### Cutting a hidden dependency Cost reduction removes a skill because unit accounting does not show which other products depend on it. The savings are visible in the first year, and the loss shows up later in someone else's results. The failures above are usually [Leverage & IP](https://usefulconsultingframeworks.com/your-edge/#leverage): it was used once, and nothing was left that makes the next engagement easier. ## Origin C. K. Prahalad and Gary Hamel introduced the idea in "The Core Competence of the Corporation," published in Harvard Business Review in May-June 1990. The article compared NEC and GTE in the early 1980s to argue that corporations should be judged on their ability to identify and build a few competencies, and not only on how they manage a portfolio of separate businesses. They also introduced core products, the components or platforms that carry a competence into many end products. They developed the argument further in their 1994 book Competing for the Future. The concept is closely related to the resource-based view, and later writers have debated the difference between competence, capability, and resource. Dorothy Leonard-Barton's 1992 paper on core rigidities showed how a competence can become a handicap. The concept is not trademarked or licensed. ## Further reading - [The Core Competence of the Corporation](https://hbr.org/1990/05/the-core-competence-of-the-corporation). C. K. Prahalad and Gary Hamel, Harvard Business Review, May-June 1990. The original article and still the best statement of the tests. HBR meters its content, so expect a paywall or a reprint fee. - [Core competency (Wikipedia)](https://en.wikipedia.org/wiki/Core_competency). A short summary of the three tests and the link to core products, with a section on how the idea relates to the resource-based view and to core rigidities. Check its claims against the original. ## Related frameworks - [Resource-Based View](https://usefulconsultingframeworks.com/frameworks/resource-based-view/): The wider theory that tests any resource for lasting advantage. Pick it when you need the tests applied to a single resource, and core competencies when the question is reuse across a portfolio. - [Ohmae's 3C Model](https://usefulconsultingframeworks.com/frameworks/ohmaes-3c/): Checks whether a competence matters to a given customer segment and how it compares with rivals, which is the second and third test in a different form. - [VRIO Framework](https://usefulconsultingframeworks.com/frameworks/vrio/): Tests a single resource for value, rarity, imitability, and organization. Pick it for one asset, and core competencies when the question is reuse across products. Last updated October 19, 2026.