Resource-based view

Write the mechanism as an activity rather than a trait. Instead of saying that culture creates advantage, specify who notices a problem, who can stop work, how the problem reaches a decision maker and how the correction becomes repeatable. That chain suggests evidence: response times, recurring defects and whether the same routine works under a different team. The measures are a proposed investigation, not reported results.

Then establish a counterfactual. If the resource disappeared, which customer or cost outcome would worsen? If a rival acquired a visible equivalent, which remaining coordination problem would prevent replication? A capability explanation gains credibility when it predicts a difference before outcomes are known. Selecting successful firms and retrospectively calling their routines valuable makes the explanation circular.

Investment and value capture are separate questions. A capability can help customers while suppliers, employees or the seller of a scarce asset receive most of the resulting return. Consider development cost, maintenance, bargaining and the price paid for access. A purchased resource can be productive yet provide an ordinary return because its expected contribution was already reflected in the transaction price.

The healthcare boundary changes the objective. Burton and Rycroft-Malone discuss tightly managed or absent markets, multiple performance goals and collaboration across organizations. A valuable improvement capability may need to spread through a network rather than remain exclusive to one institution. Patient outcomes, reliability and collective learning cannot be reduced to market share. Their argument calls for evaluation; it does not establish an intervention effect. [Burton and Rycroft-Malone, pp. 114–115](https://www.ijhpm.com/article_2877_36a155b24788e06541bc409ebbac4c55.pdf)

This lens therefore complements an external competitive analysis. Customer demand explains why an outcome matters; the resource analysis explains why one organization might deliver it differently. When either side is missing, a resource inventory becomes an investment story without a test. Use the inventory to identify uncertainties and feasible development choices, not to score every strength as a moat.

A rival can bypass rather than imitate. Customers may switch to a different delivery method that makes the incumbent capability less important. Test substitutes against the customer task, including simpler or less expensive approaches. Difficulty copying a routine is not sufficient if an alternative solves the task without it.

The apparent resource effect can reflect demand growth, regulation, distribution or favorable timing. A strong outcome in a buoyant market does not identify an internal cause. Compare how the proposed mechanism behaves across conditions and look for occasions when the resource was present but the expected outcome did not follow.

A capability can become a constraint. Specialization can make change expensive; incentives that support the present business can discourage a new offer. An investment review needs the cost of redeployment and an explicit exit or renewal condition. The fact that a routine was historically useful does not settle its next funding decision.

For an unnumbered hypothetical public-service network, the relevant question may be how to share improvement knowledge while protecting reliable delivery. Exclusivity would be the wrong default objective. Specify the public outcome and collaboration boundary before importing a competitive-advantage vocabulary; this is an analytical example, not an evaluated program.