VRIO analysis
Examine value, rarity, imitation costs and organizational support for specific resources, preserving uncertainty in each judgment.
Use VRIO when a useful asset is being called a competitive moat. Examine a resource or capability within a competitive scope, rather than scoring the whole company or a product name.
Specific resources, value records, a competitive scope, acquisition and imitation evidence, and organizational arrangements.
A resource-by-resource evidence table, conditional implications and checks on evidence or organizational gaps.
How to use it
- Define rivals and period, and identify specific resources or capabilities.
- Check V for usefulness and R for availability among relevant rivals.
- Examine acquisition, copying and substitution costs for I.
- Check roles, routines, incentives and supporting arrangements for O.
- Interpret each resource conditionally and plan evidence or organizational work.
Keep its limits in mind
Useful is not rare; rare is not costly to copy; ownership is not organized use. Examine acquisition, imitation and substitutes. Unknown means unknown. Do not sum judgments into a score, success probability or claim of achieved sustained advantage.
Separating software from an exception-follow-up capability
Fictional teaching example: Alder Lunch is reviewing its direction. S3 contains three provider cards (E1, Oct 5–9, 2026), Alder's 100-order ledger (E2), ratings by three fictional respondents (E3), capability records (E4), and supply/entry questions (E5). These are synthetic records, not market research. Proposed actions have not been carried out.
On a small screen, scroll across the diagram to read it.
Choose the resource: R1 is an exception-follow-up capability; R2 is standard software. Ten issues and eight closure records describe record coverage, not faster handling or savings.
Check each condition: R1 lacks rarity and imitation-cost evidence and has no assigned backup. R2 supports traceability and has an owner, but its standard license and lack of exclusive customization do not support a rare, costly-to-copy resource claim.
Result: The two rows identify different checks. No scores are added and no sustained competitive advantage is certified. The proposed organizational follow-up has not occurred.
Eight of ten is closure-record coverage, not an efficiency gain. R1's rarity and imitation costs are unknown; standard software is not a scarcity advantage.
Next step: The lead should confirm backup and handoff arrangements, then collect comparable rival capability and cost evidence.
Three reasons to keep an advantage claim conditional
First, pause when the row is a product name or the whole company. “Our ordering system” can combine purchased software, a person’s judgment, and a handoff routine. These may have different evidence for value, rarity, imitation, and organized use. Separate the resource or capability that the decision actually concerns before judging its conditions.
Second, do not treat missing rival information as proof of rarity or high copying costs. Lack of a visible competitor feature can reflect incomplete research. Ask which alternatives, acquisition paths, copying efforts, and substitutes matter in the stated competitive scope. Keep unknown entries unknown; they are neither positive findings nor negative findings.
Third, stop if four judgments are being added into a moat score. A resource useful for daily work may be widely available and still deserve maintenance. An unusual capability may lack the organization needed to use it reliably. The framework guides conditional reasoning about each resource; it does not certify a lasting advantage, predict success, or measure financial benefits by counting favorable cells.
Separate a resource test from a capability or activity investigation
Use VRIO for a specific resource or capability in a defined competitive setting. Choose another method when the task is mapping a capability combination, tracing work activities, or collecting a broader situation inventory. Keep the evidence status when moving between them.
| Input and question | Method | Output and boundary |
|---|---|---|
| A resource may underpin competitive advantage | VRIO analysis | Four evidence conditions and gaps; no summed score. |
| Skills and coordination may work together across settings | Core competence analysis | A capability candidate and transfer tests; no expansion authorization. |
| Operating activities may explain value or cost | Value chain analysis | Activity links and measurement questions; no assumed margin. |
| Internal and external factors need an evidenced inventory | SWOT analysis | Situation factors; a strength is not automatically a defensible resource. |
Separate Alder’s exception capability from its standard software
The complete fictional resource packet concerns Harbor preordered lunches during October 5–9, 2026. It supplies 100 order IDs tracked by standard software and ten issues requiring follow-up, of which eight have closure records. The standard license is available to others, has no exclusive customization, and has an owner with a weekly export routine. Exception follow-up depends on one coordinator, with no assigned backup or handoff. Rival capability evidence, copying costs, and actual savings are absent.
Create two rows: R1, exception follow-up, and R2, standard ordering software. Eight of ten is 80% closure-record coverage among those ten issues. It is not an order-level failure rate, a speed measure, or a cost reduction. The packet does not establish how the issues map to distinct orders, so dividing eight by 100 would answer an unsupported question. The software’s IDs support traceability without proving a performance improvement.
For R1, keep rarity and imitation costs unresolved and organized use incomplete. A capable coordinator does not remove the backup gap. For R2, standard availability and no exclusive customization do not support a scarcity or high imitation-barrier claim. Its owner and export routine are organizational evidence for that software, not evidence that the exception capability has a substitute coordinator.
| Resource | Value evidence | Rarity and imitation evidence | Organization and current conclusion |
|---|---|---|---|
| R1: exception follow-up | 8 of 10 issues have closure records; benefit and cost untested | Rivals, acquisition, copying, and substitute costs unknown | Backup and handoff absent; investigate before an advantage claim. |
| R2: standard software | 100 order IDs traceable; performance gain unmeasured | Standard license available; no exclusive customization or high barrier shown | Owner and weekly export routine present; useful common support, not established scarcity. |
Resolve organizational gaps without promising a moat
The conclusion is two different work requests. For R1, ask who could cover an absence, how unresolved issues would be handed over, and what records define closure. A proposed backup is not an accepted assignment. A documented closure may still need a quality or customer-outcome check; do not assume the issue was resolved satisfactorily just because a field is complete.
For rarity and imitation, define relevant rivals and a comparable task before collecting evidence. Ask what capabilities are actually available, how they could be acquired or reproduced, and what substitutes could achieve a similar result. An inaccessible competitor process should remain an evidence gap. No investigation or cost estimate is supplied in this case.
At review, preserve the original rows and add actual role confirmations, handoff observations, and comparable external evidence separately. Check whether backup arrangements work when needed, rather than marking O complete after writing a procedure. Any claim of faster service or lower cost needs a baseline, units, scope, and an observation window. Those outcomes cannot be derived from 8/10 or from owning software.
The next decision may be to strengthen an ordinary operational capability, maintain common software, or investigate a possible advantage further. A useful investment does not require declaring a rare resource. Record the bounded decision and actual approval. No sustained competitive advantage, completed organizational change, or measured commercial gain is established here.
Check your work
- Each row defines a resource, scope, period and records.
- The four dimensions remain distinct, with unknowns preserved.
- No total score or sustained-advantage guarantee replaces evidence and follow-up.
Framework references
References explain the framework and its scope; they do not validate the fictional example's results.
Put the framework to work
Copy the outline and add your question, evidence, and open questions.