ISYS90026 · Concepts In Information Systems
Core Competency
Core competency is ISYS90026's internal strategy lens: a core competence is the collective learning in an organisation — the ability to coordinate diverse skills and integrate multiple technologies — not a product, a patent or a single person. Prahalad & Hamel's tree metaphor (roots = competencies → core products → business units → end products) and their three tests (access to many markets, contribution to customer value, hard to imitate) are the exam's favourite tools. This chapter opens Theme 1 (worth roughly 25 of the 100 exam marks) and returns in IT sourcing (keep the core in-house) and AI transformation (data/AI as an emerging competence).
What this chapter covers
- 011. Core competence defined — collective learning that coordinates skills and integrates technologies (internal lens, vs Porter's external lens)
- 022. What it is NOT — not a product, a patent, a single technology, or a star employee; it must cross organisational boundaries
- 033. The tree metaphor — roots = competencies → trunk = core products → branches = business units → leaves/fruit = end products
- 044. Core product vs end product — intermediate embodiments (engines, chips, a navigation module) vs what the customer finally buys
- 055. The three tests (MVP) — access to a wide variety of Markets, significant contribution to customer Value, Protected-from-imitation
- 066. The multiplier effect — one competence feeds many products (Canon's competence matrix); investment is leveraged repeatedly
- 077. Strategic architecture — a road map naming which competencies to build, making resource-allocation priorities transparent
- 088. The tyranny of the SBU & governance — imprisoned resources and hoarded people; cap of ~5–6 competencies, keep the core in-house
Is it a core competence? Run the three tests, then classify on the tree
- +2Test 1 — access to many markets: the roast-profiling capability feeds three distinct channels (cafes, supermarket retail, home capsules), so it opens a wide variety of markets. Cite the three channels as evidence. (1 judgement + 1 evidence)
- +2Test 2 — contribution to customer value: a consistent, recognisable flavour is something the buyer directly tastes and pays for, so it makes a significant contribution to perceived customer benefit. Tie it to a benefit the customer feels, not an internal metric. (1 judgement + 1 evidence)
- +2Test 3 — hard to imitate: rivals buy identical beans but cannot match the cup, so the edge lies in accumulated, integrated know-how (causal ambiguity — outcome visible, recipe not), not the raw input. (1 judgement + 1 evidence)
- +3Classify on the tree: the roast-profiling know-how = roots (the unseen core competence); a bag of roasted beans = a core product (an intermediate embodiment that feeds several end products); a home capsule = an end product (what the final customer buys).
Key terms
- Core competence
- The collective learning in an organisation — the ability to coordinate diverse production skills and integrate multiple streams of technology — harmonised across organisational boundaries to deliver customer value. It is an internal capability lens, not a product or single technology.
- Collective learning
- Know-how built up and shared across functions and units over time. Unlike physical assets, it does not deteriorate with use — it grows as it is applied and shared, and typically takes a decade-plus to develop.
- The tree metaphor
- Prahalad & Hamel's image of the firm as a tree: roots = core competencies, trunk/limbs = core products, branches = business units, leaves/fruit = end products. Judging a competitor by end products alone is like judging a tree by its leaves.
- Core product
- An intermediate physical embodiment of a competence (e.g. Canon's laser engines, Honda's engines, a robot's navigation module) that feeds many end products and business units — distinct from the finished end product a customer buys.
- The three tests
- A capability is a core competence only if it passes all three: (1) provides access to a wide variety of markets, (2) makes a significant contribution to perceived customer value, and (3) is difficult for competitors to imitate.
- Multiplier effect
- Because one competence feeds many products (Canon's competence matrix: precision mechanics × fine optics × micro-electronics → cameras, copiers, printers), investment in a competence is leveraged again and again; every product draws on at least one competence.
- Strategic architecture
- A 'road map of the future' that identifies which competencies to build and the technologies inside them, making resource-allocation priorities transparent and guiding diversification.
- Tyranny of the SBU
- The danger of an organisation split into independent strategic business units: imprisoned resources, bounded innovation, underinvestment in shared competencies, and hoarded key people — which starves company-wide competencies.
Core Competency FAQ
What is the difference between a core competence and a competitive advantage?
They are complementary lenses on the same firm. A core competence (Prahalad & Hamel) is INTERNAL — what the firm is uniquely good at, built from collective learning. A competitive advantage (Porter, next chapter) is EXTERNAL — how the firm positions itself against rivals in the market. The exam explicitly tests this discrimination, so name which lens you are using and don't mix the vocabularies; a strong answer links them (a competence enables an advantage).
What are the three tests and do all three have to hold?
Yes — all three must hold. (1) Access to a wide variety of markets, (2) a significant contribution to perceived customer value, and (3) difficulty of imitation. Remember them as MVP. The customer-value test is the one most students forget; being hard to imitate alone is not enough.
How do I label the tree metaphor correctly?
Roots = core competencies (the invisible know-how), trunk/limbs = core products (intermediate embodiments that feed many businesses), branches = business units, and leaves/fruit = end products (what the customer buys). The common slip is calling the visible end product the 'competence' — the competence is always the unseen root.
Why does the course say competencies 'don't deteriorate'?
Unlike a machine that wears out, collective know-how compounds the more it is used and shared across the firm — Prahalad & Hamel's line is that competencies 'grow' with use. MCQ distractors flip this by claiming competencies depreciate like physical assets, which is wrong.
How is this chapter examined?
As part of Theme 1 (Core Competency & Competitive Advantage, ~25 marks). Expect 1–2 MCQs on the definition or the three tests, plus an applied essay that hands you a firm and asks 'is X a core competence?' — you run all three tests with case evidence, conclude, and classify the parts on the tree. It also returns in IT sourcing (don't outsource a core competence) and AI transformation (data/AI as a competence).
Exam move
Don't memorise the definition and stop there — the marks are in application. For any case, run the three tests (MVP: Markets, Value, Protected-from-imitation) one at a time and quote the case as evidence for each, then conclude and classify the parts on the tree (roots = competence, trunk = core product, fruit = end product). Drill the two highest-frequency traps: calling a product or single technology a 'competence' when it must be collective learning across boundaries, and blurring core competence (internal) with competitive advantage (external). Practise on small invented firms until the move is automatic, and connect the idea forward — it is the reason the sourcing chapter says keep the core in-house and the AI chapter treats proprietary data as an emerging competence.
