Distinctive capabilities: test what can sustain an advantage

Define the outcome

Start with the customer or economic outcome, then identify the activity system that produces it.

• Outcome
• Comparison
• Evidence

Test distinctiveness

Compare performance and required inputs with credible alternatives; record what is inferred rather than measured.

• Benchmark
• Proof gap
• Rival response

Decide what to build

Make dependencies, time to develop and the review trigger explicit before allocating resources.

• Dependencies
• Investment
• Review trigger

CAPABILITY EVIDENCE PROTOCOL

Define the outcome and comparison

Name the customer or economic outcome, the population concerned, the time horizon and the credible alternative. A capability is not distinctive because it is important or difficult internally. It must produce a repeatable difference measured against another way of delivering the same outcome. Preserve the unit, source, date and uncertainty for every comparison.

• Outcome
• Population
• Alternative
• Period

Prove the capability before treating it as a source of advantage.

Describe the operating mechanism

Map the routines, decisions, data, technology, skills, assets and partners that jointly create the result. Avoid attributing performance to a single visible resource when coordination or accumulated learning is the actual mechanism. State which component is necessary, which is substitutable and where the causal explanation is still only an assumption.

• Routine
• Resource combination
• Coordination
• Assumption

Prove the capability before treating it as a source of advantage.

Test transferability and maintenance

A capability that works in one team, segment or geography may not transfer. Examine the conditions needed to reproduce it, the lead time, the quality controls and the dependencies that can break it. Distinguish current capacity from capacity that still needs investment, acquisition or partnership before it can support a strategic option.

• Transfer conditions
• Lead time
• Quality control
• Dependency

Prove the capability before treating it as a source of advantage.

Compare build, protect, partner and stop

Turn the evidence into explicit options. Building may preserve learning but take time; protection may require governance and access rights; partnership may accelerate deployment while creating dependency; stopping avoids continued investment in an unproven claim. Compare total cost, control, reversibility and the evidence threshold for the next commitment.

• Build
• Protect
• Partner
• Stop

Prove the capability before treating it as a source of advantage.

Set erosion and review signals

The capability record remains dated. Define the observed signal that would indicate imitation, substitution, loss of quality, staff concentration, data decay or reduced customer value. Add the decision threshold, review owner and planned date. This prevents yesterday’s superior performance from becoming an unsupported permanent label in the strategy.

• Erosion signal
• Threshold
• Owner
• Review date