← HR strategy

Capabilities that last

The resource-based view

Look beyond headcount to the knowledge, relationships and routines that enable an organisation to do something distinctive.

Jay B. Barney · 1991 · Original editorial explanation
The resource-based view — simplified model sketchValuable · Rare · Hard to imitate · Non-substitutable. Editorial interpretation, after Jay B. Barney (1991).ValuableRareHard to imitateNon-substitutableADM HR · ORIGINAL INTERPRETATIONJay B. Barney · 1991
Original simplified sketch after Jay B. Barney (1991). Read the explanation for assumptions and limitations. Download SVG ↗

The core idea

Barney’s 1991 resource-based argument links sustained competitive advantage to heterogeneous resources that competitors cannot easily reproduce or replace. Its familiar criteria are value, rarity, imperfect imitability and non-substitutability: VRIN. Later VRIO formulations add organisation as an explicit question, but should not be presented as the identical 1991 framework. HR applications often focus on collective knowledge, coordination and relationships rather than an isolated “star” employee.

Source and attribution [1]

Using it in practice

Describe a capability as something the organisation can reliably do. Identify the people, tools, routines and relationships supporting it. Ask what a competitor could buy tomorrow and what would require years of shared learning. Then assess fragility: a supposedly distinctive capability held by one exhausted specialist may be a continuity risk. Development, knowledge sharing and fair retention practices can be more useful than simply paying for scarce credentials.

An example, not a reported case

Worked example · illustrative

A small engineering firm resolves unusual installation problems quickly. Its advantage is not just certification: technicians trust one another, share failure histories and know which design specialist to call. HR builds mentoring time and succession cover into the operating plan. It evaluates whether new technicians can solve unfamiliar cases with support, rather than counting course attendance as the capability itself.

What to watch for

Value is contextual and can disappear as customer needs change. A valuable workforce should not be treated merely as property: employees have agency, rights and options.

Define the capability in observable terms

Move beyond statements such as 'our people are our greatest asset'. Identify what the organisation can reliably do that matters to its service: mobilise a complex contract, solve unusual customer problems or develop supervisors internally. Describe the combination of skills, relationships, routines and knowledge involved. A capability often sits between people rather than inside one individual. This distinction changes the investment decision from buying a star performer to strengthening the system that enables coordinated performance.

Test strategic relevance

Ask which customer or operational problem the capability solves and whether that problem is likely to remain important. A rare skill that has little connection to the strategy may not justify priority investment. Compare the capability with alternatives: technology, partnerships, redesigned work or different service choices. Do not assume that a competitor's difficulty copying something automatically makes it beneficial. A deeply embedded routine can also preserve an outdated way of working.

Protect continuity without trapping knowledge

For an illustrative specialist team, identify tasks dependent on one experienced colleague. Pair work, structured handovers and supported practice can reduce fragility while preserving expertise. Give people time and recognition for teaching others; otherwise knowledge sharing competes with their measured workload. Avoid treating employee mobility as disloyalty or attempting to 'own' a person's knowledge. The practical objective is an organisation that learns and remains resilient, with employees gaining development opportunities rather than becoming indispensable bottlenecks.

Build evidence of capability development

Track demonstrated proficiency, coverage of critical tasks, internal progression and service quality, not just training expenditure. Examine whether teams can perform under less familiar conditions or when a key person is absent. Compare the cost of development with the risks of continued dependence and alternative approaches. Resource-based thinking helps frame a strategic argument, but it does not prove that a particular HR investment will generate sustained advantage. That claim still needs evidence and a realistic account of changing demand.

Distinguish having talent from organising its contribution

Employing experienced people does not guarantee that their capability creates advantage. They may lack information, authority, equipment or relationships needed to use it. Examine how individual expertise combines with routines and teamwork. For example, excellent analysts create little value if decision makers cannot interpret the findings or act on them. The organisational arrangements that connect expertise to useful work may matter as much as the scarcity of the expertise itself.

Test the fragility of the proposed advantage

Ask what would happen if a key expert left, a competitor hired similar people or technology changed the task. Invest in development, collaboration and knowledge transfer while respecting that employees can choose to leave. A capability can be valuable without being permanently rare or difficult to imitate. Use the framework to examine investment priorities and dependencies, not to claim that people are owned resources or that a competitive advantage has been proven by an impressive skills inventory.

Take it into your next conversation

Three useful questions.

  1. What can we do reliably that matters to customers?
  2. How is that capability reproduced?
  3. Where is the single point of failure?

Related terms

Go to the evidence

Sources & attribution

[1] Barney, J. (1991). Firm Resources and Sustained Competitive Advantage. ↗

The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.

Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained.

Published 2026-09-20 · Reviewed 2026-09-22. Editorial approach

Keep exploring

A little more context.

People analytics · models & decisions01

The HR value chain & causal chain

Connect HR investment with employee, operational and business outcomes—and test the links.

David E. Guest6 min
AMO framework02

Ability, motivation and opportunity

A performance problem may be about capability, willingness, or the chance to contribute. Diagnose before prescribing.

Thomas Bailey5 min
There is no single best way03

Contingency theory & strategic fit

Choose HR practices that fit the work and its context, while keeping legal and ethical standards consistent.

Paul R. Lawrence5 min