Eterdis Vrio

VRIO + Dynamic Capabilities: What You Have and Whether You Can Keep It

Loading Company Context

Before starting, look for a company-context.md file. Read it if available. If you have access to a document library, retrieve anything covering resources, competitive position, and current strategy.

If you find context with an existing Resources table:

• Note every resource already listed, its VRIO status, and the last-validated date.
• Check: is any resource more than 6 months stale? Flag it immediately. Stale VRIO ratings are worse than no ratings — they create false confidence.
• Use the existing inventory as the starting point. Don't make the user rebuild from scratch.

If no context is available, ask:

• What business are we analysing?
• What are the 3-5 resources or capabilities you consider most important to how you compete?
• Who are your most relevant competitors?
• Have you done this kind of resource analysis before? (If yes, what changed since then?)

Additional documents that add value: resource/capability inventory, competitive analysis, strategy deck, prior VRIO or core competency work, post-mortems from lost deals or failed initiatives.

Determine the Mode

Ask: "Is this a first run or a deep refresh, a quick review, or are we setting up alert triggers?"

Then follow the appropriate track below.

Mode 1: Diagnostic (Full Session)

Time guidance: Expect to spend at least 30 minutes to get something of value. This isn't a race — sit with the hard questions overnight if you need to. The best insights from VRIO come after you've slept on the uncomfortable ones. If a resource feels obviously strong, you probably haven't interrogated it hard enough yet.

This is the deep session. Run it the first time, or when enough has changed that the old picture can't be trusted anymore.

Part A: Build the Resource Inventory

Most businesses think they know what makes them competitive. They're wrong about at least half of it. VRIO (Jay Barney, 1991) strips away the self-congratulation and forces four honest questions about every resource you think matters. Think of it as a lie detector for competitive advantage.

Get the user to lay out their most important resources and capabilities. Push them across all four categories — people always forget at least one:

• Tangible: equipment, facilities, financial reserves, proprietary technology, data assets
• Intangible: brand, IP, reputation, customer relationships, regulatory positions, network effects
• Human: specific skills, institutional knowledge, key people, culture, talent pipeline
• Organisational: processes, systems, decision-making speed, partnerships, coordination mechanisms

If they stall: "Forget what you're proud of. What would make a well-funded competitor lose sleep trying to replicate? The thing that would take them years, not months." That's where the real stuff lives.

If they only list assets they're proud of: "Now tell me the ugly ones. What do you actually depend on that you'd be embarrassed to put on a slide?"

Part B: VRIO — The Four Tests

Work through these for each resource. No softballs. The value is in surfacing uncomfortable truths, not handing out gold stars.

V — Valuable

Does this resource help you do something the market rewards?

• Does it let you deliver more value to customers, lower your costs, or respond faster than alternatives?
• Or is it just dead weight you keep paying for out of habit?
• The trap: organisations love resources that customers don't care about. The beautiful headquarters. The award-winning internal process. The patent on something nobody wants to buy. If the market doesn't reward it, it's not valuable. Full stop.
• Ask specifically: "If this vanished overnight, would your customers notice within 30 days?" If the answer is no, you're probably looking at overhead, not advantage.

Not valuable: This isn't an asset — it's a distraction. Flag it and move on.

Valuable: Move to R.

R — Rare

Do your competitors already have this?

• How many of your direct competitors have the same thing or something close enough?
• Is this just the cost of admission in your market?
• Table stakes are not advantages. Every restaurant needs a kitchen. Every accountant needs software. Having them doesn't make you special — not having them makes you dead.
• Watch for rarity inflation: "We have great people" is not rare. "We have three engineers who've spent 15 years solving this exact problem and the knowledge lives in their heads" might be.

Not rare: Competitive parity. You need it to play, but it's not why you win. Stop putting it in pitch decks.

Rare: Move to I.

I — Inimitable

Could a well-funded competitor replicate this within a few years?

This is where most "advantages" die. Ask:

• What would it actually take for a well-funded competitor to build what you have? Just money? Or something money can't buy?
• Is this tied to your specific history, people, or circumstances — something you couldn't replicate yourself if you started over?
• Is there causal ambiguity — meaning even you aren't fully sure why it works? (Ironically, that's a feature. If you can't explain it, competitors can't reverse-engineer it.)

Three things make resources genuinely hard to copy:

• Path dependency: It took years to build and there's no shortcut. Like a 20-year-old vineyard — you can't just buy time.
• Social complexity: It's woven into relationships and culture. You can't hire it away or buy it in a transaction. This is why "our culture" can be a real advantage, but only if you can't describe it in a PowerPoint bullet.
• Tacit knowledge: It lives in people's heads, not in a manual. Good luck extracting that.

Imitable (2-3 years with money): Temporary advantage. Ride it hard, but don't bet the company on it lasting. Set a review date.

Genuinely hard to replicate: Move to O.

O — Organised

Is your organisation set up to actually use this resource?

This is the question that exposes the most waste. Organisations sit on valuable, rare, hard-to-copy resources all the time — and do nothing with them. It's like owning a Ferrari and taking the bus because nobody updated the parking policy.

Ask:

• Who has access to this resource? Is it locked in one department while the rest of the company pretends it doesn't exist?
• Are the people closest to it empowered to use it, or do they need three approvals and a committee meeting?
• Does your current strategy actually build on this? Or does it sit in the background while you compete on things you're worse at?
• What would change if you reorganised the business around this resource?
• Is the resource growing or decaying? Are you investing in it, or coasting?

Part B Summary: Assign Status

For each resource, assign a competitive status:

Part C: Dynamic Capabilities — Can You Keep Winning?

VRIO tells you what you have right now. It's a snapshot. A photograph. But markets don't sit still, and neither do competitors. A beautiful VRIO scorecard from 2024 is toilet paper if the world shifted in 2025 and you didn't notice.

This is where David Teece's Dynamic Capabilities framework (1997, refined through 2014) earns its keep. It asks: can your organisation sense what's changing, seize opportunities before competitors do, and transform itself when the old advantages stop working?

Think of it this way: VRIO measures the hand you're holding. Dynamic capabilities measure whether you know how to play poker.

Sensing: Do You See What's Coming?

How good is this organisation at detecting shifts in the environment before they become obvious?

Probe:

• Where does your market intelligence actually come from? Is it systematic or is it one person who reads a lot?
• When was the last time you spotted a trend early and acted on it? When was the last time you were blindsided?
• Are you scanning for threats to your specific VRIO advantages, or just general industry news?
• How close are you to the edges of your market — the weird customers, the startups, the adjacent industries?
• Do you have mechanisms for surfacing uncomfortable information, or does bad news get filtered on its way up?

"The companies that get disrupted don't get disrupted because the signals weren't there. They get disrupted because the signals were ignored, or never reached the people who could act on them."

Seizing: Can You Actually Move?

When you see an opportunity or threat, can you mobilise resources and commit before the window closes?

Probe:

• How long does it take to go from "we should do something about this" to actually doing it? Be honest — not the best case, the typical case.
• When you last had a real opportunity, what happened? Walk me through the decision chain.
• Can you reallocate budget mid-year? Can you reassign people? Can you kill a project that's not working?
• Is your investment process designed for exploitation of known opportunities or exploration of new ones? (Most organisations are built for one and bad at the other.)
• Who can say yes? How many people can say no?

"Sensing without seizing is just well-informed paralysis. You see the wave, you write a memo about the wave, the wave hits you while you're still formatting the memo."

Transforming: Can You Reinvent When You Must?

When the environment shifts enough that your current model stops working, can you reconfigure?

Probe:

• Has this organisation ever meaningfully changed its business model, operating model, or resource base? What happened?
• What would it take to shift 30% of your resources from the current core to something new? Is that even imaginable?
• Are people's identities tied to the current way of doing things? (This is the real barrier — not systems, not money. Identity.)
• Do you have experience with managed decline of old advantages while building new ones, or is it always all-or-nothing?
• If your primary VRIO advantage became worthless in 18 months, what would you do? Not "what's the strategy" — what would you actually do on Monday morning?

"Transformation isn't a strategy retreat. It's the willingness to let go of what made you successful when the evidence says it won't keep working. Most organisations would rather die right than live differently."

Dynamic Capabilities Summary

Rate each dimension:

Then connect it to the VRIO results:

• For each sustained advantage: Is sensing strong enough to detect when it's eroding? Is transforming strong enough to pivot if it becomes obsolete?
• For each temporary advantage: Is seizing fast enough to extract maximum value before competitors catch up?
• For each unexploited advantage: Is the seizing/transforming weakness the reason it's unexploited?

Part D: Closing the Diagnostic

Skip the 40-page strategy deck. Hit them with what actually matters:

1. What are you underestimating? The resource that passed all four tests but isn't central to your strategy. Your buried treasure.
2. What are you overestimating? The resource you love talking about that doesn't actually pass V or R. Time to stop building around it.
3. What's the organisational fix? If you have unexploited advantages, what concrete changes would unlock them?
4. Can you keep winning? Where are the dynamic capability gaps that put your current advantages at risk?
5. What's the one thing? "Based on what we just found — if you could only do one thing in the next 12 months to strengthen your real competitive position, what would it be?"

Connect to the Strategy Map

Resources are step 1 of the strategy chain. The output of this skill feeds directly into the strategy map:

Resources (what you have) -> Delivery capability (what you can do) -> Customer value (why they buy) -> Results (what you get)

After this diagnostic, the "Resources" step should be populated with tested, honest assessments — not wishful thinking. If the strategy map skill has been run before, check whether the resources you've now validated actually support the delivery capabilities the strategy assumes. If they don't, that's your primary gap.

Update company-context.md

After the diagnostic, update the following in company-context.md:

Resources that matter table: Update every resource with current VRIO status and today's date as last-validated.

Add any new resources discovered during the session. Remove any that turned out not to be resources at all.

Add a row to the Session log:

If dynamic capabilities assessment revealed gaps, note them in the Open questions section.

Mode 2: Review (Quick Re-Assessment)

Time guidance: 10-15 minutes if nothing major has changed. If you start finding surprises, switch to Diagnostic mode — something shifted and a quick pass won't cut it.

This is the "since last time" check. Run it quarterly, or whenever something meaningful changes.

Steps

1. Load company-context.md. Read the existing Resources table and session log.

2. Walk through each resource:

   • Does this still pass V? Has the market shifted? Are customers still rewarding this?
   • Does this still pass R? Has a competitor closed the gap?
   • Does this still pass I? Has something changed that makes replication easier? (New technology, key person left, knowledge got codified and leaked?)
   • Does this still pass O? Are you still organised to exploit it, or has organisational drift happened?

3. Scan for new resources: "Has anything emerged since last time that might be a new advantage? A hire, a partnership, a capability you've built, a data asset that's accumulated?"

4. Quick dynamic capabilities check:

   • Any signals you've been sensing but not acting on?
   • Any opportunities you saw but couldn't seize? Why not?
   • Anything that suggests the transformation muscle needs exercise?

5. Update or confirm each resource's status and timestamp in company-context.md.

6. If anything changed: Note what shifted and why. This creates the trail that makes the next review faster and more honest.

Mode 3: Alert Triggers

These are the tripwires. Define them once, then use them as your early-warning system. When a trigger fires, you know it's time to re-run the relevant part of the assessment.

Setting Up Triggers

For each sustained or temporary advantage, define:

Erosion triggers (your advantage is weakening)

• "If [competitor X] launches [product/capability Y], re-test resource Z."
• "If we lose [key person / key customer / key partner], re-test resource Z."
• "If [technology shift] makes [our approach] replicable at lower cost, re-test resource Z."
• "If our [metric tied to this advantage] drops below [threshold], re-test resource Z."

Opportunity triggers (a new advantage may be forming)

• "If [market shift] happens, assess whether [emerging capability] passes VRIO."
• "If [regulatory change] occurs, check whether it creates a new barrier to entry we benefit from."
• "If we hit [milestone] with [initiative], test whether it's become a real resource."

Dynamic capability triggers (your ability to adapt is being tested)

• "If we see [signal] and don't act within [timeframe], our sensing-to-seizing pipeline is broken."
• "If a strategic initiative takes longer than [threshold] to get from approval to action, seizing is weak."
• "If we've known about [threat] for [duration] and haven't started adapting, transformation capability is atrophying."

Recording Triggers

Add triggers to the Active assumptions table in company-context.md:

When a trigger fires, run either a Review (if it's a single resource question) or a full Diagnostic (if the landscape has shifted broadly).

Framework References

• VRIO Framework: Jay Barney (1991), "Firm Resources and Sustained Competitive Advantage," Journal of Management. Refined in Barney & Hesterly, Strategic Management and Competitive Advantage (multiple editions).
• Dynamic Capabilities: David Teece, Gary Pisano, & Amy Shuen (1997), "Dynamic Capabilities and Strategic Management," Strategic Management Journal. Refined in Teece (2007), "Explicating Dynamic Capabilities," and Teece (2014), "The Foundations of Enterprise Performance."

VRIO + Dynamic Capabilities, applied through Eterdis consulting practice. This skill is step 1 of the strategy chain — it populates the resource base that everything else builds on. To connect this to strategic direction, competitive positioning, and organisational design, visit eterdis.com or book a conversation at eterdis.com/contact.