VRIN assets, microfoundations (sensing, seizing, transforming); building vs. buying.
The resource‑based view (RBV) and dynamic capabilities approach shift the strategist’s attention from external structure to internal distinctiveness. Where positioning asks, “Where is the attractive place to stand?”, RBV asks, “What can we uniquely and reliably do there?” Dynamic capabilities extend the inquiry: “How do we renew what we can do as conditions change?” Together they form a theory of advantage grounded in assets, routines, and learning rather than in market structure alone. This chapter clarifies VRIN/VRIO logic, unpacks the microfoundations of sensing, seizing, and transforming, and offers a practical guide to building, buying, or allying for advantage.
I. The Resource‑Based View: Advantage From Distinctiveness
RBV begins with heterogeneity. Firms differ in the resources they control—tangible and intangible—and in the routines that combine those resources into outcomes. Some differences are trivial; others are the root of persistent performance gaps. RBV proposes a simple test: to be a foundation for sustained competitive advantage, a resource or capability should be valuable, rare, inimitable, and non‑substitutable (VRIN). Many practitioners use the operational cousin VRIO—valuable, rare, costly to imitate, and the firm is organized to capture the value.
1) What counts as a resource or capability?
The term is broader than factory and patents. It includes:
Physical assets: specialized plants, sites, logistics networks, proprietary equipment.
Intangible assets: brands, reputation, regulatory licenses, data, algorithms, proprietary standards.
Human and relational capital: expert communities, trust with customers and suppliers, partner ecosystems.
Organizational routines and culture: the patterned ways of working—problem framing, handoffs, escalation—that produce consistent results.
A capability is not the asset itself but the ability to deploy it repeatedly with reliability (e.g., a supply chain that compresses lead times under volatility; an integration capability that absorbs acquisitions with low disruption).
2) Isolating mechanisms
Even valuable and rare assets do not ensure sustained advantage unless rivals are constrained from easy imitation. RBV emphasizes “isolating mechanisms,” including:
Causal ambiguity: outsiders cannot see which specific actions drive outcomes.
Social complexity: trust, norms, and shared language that are hard to transplant.
Path dependence and time‑compression diseconomies: the advantage reflects long accumulations of learning that cannot be rushed.
Cospecialization: assets fitted to one another (technology + channel + brand) such that copying one element is insufficient.
Legal protection: patents, trade secrets, exclusive rights.
Access bottlenecks: privileged data capture points, scarce locations, or certifications.
These mechanisms make the “copy cost” high or the “copy time” long, extending the life of advantage.
3) Appropriability: who actually captures the value?
Even when a capability creates value, the distribution of that value depends on bargaining and contracts. Complementors, powerful distributors, or key employees may capture the surplus unless the firm has appropriability mechanisms: ownership of IP, control of critical interfaces, credible alternatives to any one partner, and incentive systems that align internal talent with long‑run value capture.
4) Two cautionary notes
RBV invites two well‑known missteps. First, tautology: labeling whatever a successful firm has as a “VRIN capability.” Remedy: specify mechanisms ex ante and state what would falsify the claim. Second, inwardness: staring at capability lists while the basis of competition shifts. Remedy: link capability analysis to external change and to resource allocation, not just to taxonomy.
II. Mapping Capabilities: From Lists to Architecture
Most organizations already possess hundreds of routines. Strategy distinguishes among them and designs an architecture that concentrates investment where it compounds.
1) A practical classification
A useful scheme divides capabilities into:
Differentiating capabilities that drive the firm’s theory of advantage (e.g., demand insight, platform governance, precision manufacturing, clinical development).
Enabling capabilities necessary to operate but not by themselves differentiating (e.g., general IT, HR operations, accounting).
Commodity services better sourced from the market when scale or specialization exists outside.
The architecture exercise asks: Which 4–6 capabilities must be truly world‑class for our position? Which can be “good enough”? Which should be externalized to focus internal talent and capital? The answer anchors both the investment plan and later buy/ally decisions.
2) Capabilities as systems
Few differentiators reside in a single department. They are systems cutting across functions—data + process + talent + tooling + governance. For example, a “rapid product launch” capability might span market sensing, modular engineering, supplier qualification, regulatory prep, pricing, and post‑launch analytics. The strategist designs interfaces among these parts and ensures ownership is clear.
3) Measuring capabilities
Because capabilities are intangible, measurement relies on leading indicators and benchmarks:
For cost‑advantage routines: cycle times, yield curves, learning rates, density effects.
For market‑facing routines: win rates by segment, time‑to‑first‑value, retention and expansion, attach of complements.
For knowledge routines: time from insight to decision, experiment throughput, model performance stability.
Measurement supports prioritization and learning; it is not a performance‑management cudgel. The key is to tie indicators to the mechanisms the capability claims to operate through.
III. Dynamic Capabilities: Renewal Under Change
Where RBV explains what makes advantage defensible, the dynamic capabilities view explains how firms adapt that advantage when the environment shifts. The central idea is that beyond operational excellence, some firms possess higher‑order routines—sensing, seizing, and transforming—that let them sense change early, commit decisively, and reconfigure assets faster and more effectively than rivals.
1) Sensing
Sensing is systematic attention to weak signals about technology, markets, regulation, and user behavior. Microfoundations include:
Boundary‑spanning structures: customer advisory boards, field immersion, embedded product managers in client workflows, developer relations for platforms.
External search and partnerships: academic consortia, venture programs, open‑innovation pipelines, supplier scouting, patent landscaping.
Probe‑and‑learn routines: small experiments, pilots with lead users, controlled releases, living labs; the discipline lies in rapid feedback and clear hypotheses.
Sensing is not passive scanning; it is contact with the edges where change begins, with mechanisms to translate observation into options leaders can act on.
2) Seizing
Seizing converts insight into committed moves—with timing, scale, and configuration that turn options into advantage. Microfoundations include:
Investment governance that funds staged bets quickly, with explicit kill/scale thresholds (option logic).
Business model innovation: pricing architecture, channel changes, or platformization that unlocks adoption.
Deal capabilities: minority stakes, technology licensing, and M&A where appropriate—paired with integration playbooks (technical, cultural, and commercial).
Risk management: hedging and supply strategies that make bold moves survivable.
Seizing often requires leadership commitment in the face of incomplete evidence—credible decisions that reallocate people and capital, not rhetorical support.
3) Transforming
Transforming is the reconfiguration of assets and organization to sustain new ways of creating value. Microfoundations include:
Asset orchestration: retiring obsolete assets, redeploying people, and re‑sequencing portfolios; divestiture as a deliberate skill.
Modularity in organization and technology: clean interfaces and platform components that allow recombination without wholesale rebuild.
Culture and incentives: norms that favor learning, truth‑seeking reviews, and cross‑unit collaboration; incentive plans that reward outcomes of the new system, not legacy volume.
Governance refresh: decision rights, metrics, and cadence updated to the new theory of advantage.
Transforming is where many firms stall: they sense and even seize, but legacy structures and measures pull them back. Treat transformation as a capability with owners, routines, and a backlog—not as a one‑off “program.”
4) Distinguishing dynamic from operational capabilities
Operational capabilities keep the current model efficient; dynamic capabilities change what the organization is capable of. A robust supply‑planning routine is operational; the ability to shift the product architecture from integrated to modular, or to pivot sales from direct to ecosystem‑led, is dynamic.
IV. Building vs. Buying (and Allying): Choosing the Path to Capability
Once a firm identifies the capabilities that matter, it must choose how to obtain them. The classic options—build, buy, or ally—have distinctive economics and risks. The choice should be made capability by capability, with explicit criteria.
1) When to build
Building is favored when:
The knowledge is tacit and embedded in practice (difficult to acquire intact).
The capability is core to differentiation and must be deeply integrated with culture, data, and systems.
External markets for the capability are thin; suitable targets or partners are rare.
Time horizon allows staged development; the firm can compete while the capability scales.
Building requires a design (architecture, milestones, talent model) and patience. It also benefits from platform thinking: create shared components (data pipelines, design systems, compliance primitives) that future initiatives reuse.
2) When to buy
Buying—acquisition or acqui‑hire—is favored when:
Speed is essential and integration is feasible.
The capability is modular enough to be slotted in without rewiring the whole firm.
There is a healthy market for corporate control, with targets whose economics can be understood and whose leaders will stay.
The capability includes rights (IP, licenses, access) that transfer with ownership.
The risks are well-known: synergy illusion, cultural incompatibility, overpayment, and post‑deal attrition. A repeatable integration capability—playbooks for systems, incentives, and decision rights—is itself a differentiating dynamic capability.
3) When to ally
Alliances, joint ventures, and structured partnerships are favored when:
The capability is complementary—mutual dependence with shared surplus.
Appropriability is a concern: ownership would be too costly or politically impractical; contracts can align incentives.
The environment is uncertain; the firm wants an option without full commitment.
Ecosystem health matters more than unilateral control (e.g., standards, platforms).
Alliances demand governance: clear scope, decision rules, IP and data rights, termination paths, and joint metrics. Many fail not for strategic reasons but for lack of day‑to‑day operating routines between partners.
4) A decision framework
In practice, executives can ask:
Strategic criticality: Is the capability central to our theory of advantage?
Tacitness and cospecialization: How embedded is it in routines and adjacent assets?
Time to impact: How fast must we be good at it?
Control and appropriability: Do we need ownership to capture value safely?
Market availability: Are there credible targets or partners?
Integration burden: What system and culture rewiring would buying require?
Risk of leakage or hold‑up: How exposed are we if a partner defects?
Mapping answers on these dimensions often reveals the dominant path and the sequencing (e.g., ally now, build in parallel, buy later to consolidate).
V. Orchestrating Complementary Assets
Even strong capabilities can be stranded without complementary assets—distribution, after‑sales service, manufacturing, regulatory clearance, or platform access—that enable commercialization. Strategists ensure access and alignment to these complements, whether by ownership, contracting, or ecosystem design. In many modern settings, the bottleneck sits outside the firm; dynamic capability then includes stakeholder strategy—coalitions, standards, and regulatory engagement—to unlock complements.
VI. Avoiding Capability Traps
The internal lens has characteristic failure modes. Recognizing them reduces risk.
Capability laundry lists. Enumerations of strengths without causal links to outcomes invite diffusion. Remedy: name mechanisms and indicators; cut the list to those that move economics.
Core rigidities. Routines optimized for yesterday become barriers today. Remedy: periodic “zero‑based” capability reviews; rotate leaders; retain optionality in architecture.
Myth of best practice. Importing generic practices without the surrounding system rarely differentiates. Remedy: adapt to context; design for fit with the firm’s activity system.
Outsourcing crown jewels. Near‑term savings tempt firms to externalize differentiators. Remedy: keep control of bottlenecks; externalize non‑core.
Acquisition as a substitute for learning. Buying to skip development can freeze capability maturity at the acquired level. Remedy: pair M&A with internal absorption goals and knowledge transfer plans.
Metrics theater. Scorecards without decisions and reallocation waste attention. Remedy: connect measures to the investment calendar and to explicit scale/stop thresholds.
VII. Linking RBV and Dynamic Capabilities to Other Lenses
These internal theories complement, not displace, other schools.
With positioning: Use Five Forces to choose where advantage is earnable; use RBV to ensure the firm possesses (or can build) the distinctive system to win there.
With game theory: Commitments (capacity, contracts, platform rules) are more credible when backed by real capabilities; rivals respond to what you can actually do, not what you say.
With ecosystems: Capability focus shifts outward: orchestration, developer experience, trust and safety, and data governance become differentiating routines.
With real options: Dynamic capabilities prosper when investments are staged; options thinking provides financial discipline for sensing and seizing.
With stakeholder strategy: Licenses, permits, and social legitimacy behave like capabilities; they are cultivated and renewed through routines of engagement and transparency.
VIII. A Practical Agenda: From Diagnosis to Build Plan
Turning the theory into action typically follows a repeatable sequence.
Articulate the theory of advantage (from Chapters 3–4). Specify which capabilities it presumes.
Conduct a capability audit. For each presumed differentiator, assess maturity, tacitness, isolating mechanisms, and dependence on complements. Use external benchmarks sparingly; focus on economics and evidence.
Choose the 4–6 differentiating capabilities to elevate and the few enabling ones that must be reliably “good enough.” Declare what will not be built internally.
Design each target capability as a system. Define processes, data flows, technology enablers, decision rights, and talent profiles; specify the interfaces with adjacent routines.
Decide build/buy/ally paths with explicit criteria and sequencing. Where buying is likely, prepare integration playbooks in advance; where building, define milestones and learning metrics.
Reallocate resources. Shift budget and senior talent; create visible commitments (e.g., platform investment, labs, partnerships) that are hard to reverse casually.
Wire learning. Establish leading indicators tied to mechanisms; run post‑decision reviews to refine microfoundations.
Refresh. Every 12–24 months, revisit assumptions: which capabilities truly moved economics; which hardened into rigidities; which complements or bottlenecks shifted.
IX. Illustrative Capability Microfoundations (Brief)
To make the microfoundations concrete, consider three common differentiators.
Demand insight at scale. Sensing: instrumentation of user journeys; ethnography; conjoint and causal inference. Seizing: rapid experimentation pipelines; cross‑functional launch councils; pricing and packaging tests. Transforming: unified data models; privacy‑by‑design; product and marketing incentives tied to retention, not top‑of‑funnel.
Operational excellence in time‑critical fulfillment. Sensing: real‑time telemetry of bottlenecks; weather and event feeds. Seizing: dynamic slotting and routing; surge staffing models; fast supplier pre‑qualification. Transforming: facility layout redesign; cross‑training; automation cells; procurement rewrites to favor lead‑time variance, not piece price alone.
Acquisition‑integration engine. Sensing: target maps; technology scouting; cultural due diligence. Seizing: standardized term sheets; integration “day‑0/30/100” playbooks; brand architecture rules. Transforming: org design that absorbs teams; knowledge base of integration lessons; earn‑outs aligned with capability transfer.
Each example shows capabilities as repeatable patterns, not heroic acts—a hallmark of durability.
