Core Competencies
5 min read · 4 principles · apply it by lunch
Good morning. Take your product away. What’s left is what actually competes.
If your current product were made obsolete tomorrow — the whole category gone, not just a competitor winning — what capability would your company carry into whatever comes next, and if you can’t name it in one sentence, why haven’t you worked out whether you’re building an organisation or just a product with staff?
In 1990, C.K. Prahalad and Gary Hamel published ‘The Core Competence of the Corporation’ in Harvard Business Review, and it became one of the most influential articles the journal has run. Their image was a tree: the products a company sells are the fruit and leaves, visible and countable; underneath sit the roots — the core competencies, the collective learning of the organisation, above all its ability to coordinate diverse skills into something rivals cannot easily assemble. Judge a company by its fruit and you will misread it. Honda was never really a motorcycle company; it was a company with a deep competence in engines, which is why motorcycles could become cars, generators and lawnmowers without the firm losing its identity. Canon’s competencies in optics and precision mechanics yielded cameras, then copiers, then printers. The trap runs in both directions: teams that declare everything core — ten ‘competencies’ that are really just activities — end up focused on nothing, while teams that outsource for short-term cost quietly hand a supplier the very learning that made them worth buying from. Most people define their company by what it sells. The dangerous competitors define theirs by what it knows.
Core Competencies is Day 57 of 365.
In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.
$29 a month · cancel any time · 7-day money-back guarantee