Diagnose & Map method guide
Capability Analysis
Capability Analysis compares strategic value, current strength, imitability and action need.
Beginner-friendly guide · 4 min read
What Capability Analysis does
Capability Analysis compares strategic value, current strength, imitability and action need.
Capability analysis provides a concise portfolio view of what the organisation can repeatedly do and how those abilities support strategy. It is broader and faster than a detailed competence map.
The method helps leaders identify capabilities to strengthen, protect, source, partner or monitor. Compare capabilities at a similar level and distinguish them from assets, projects and aspirations.
This is a lighter executive scan grounded in resource-based strategy. It is useful for triage before deeper competence, defensibility or make-or-buy analysis.[1][2]
The position suggests where to build, protect, source or monitor, subject to evidence and dependencies.
Strategic importance: low to high
Current strength: low to high
InnovationFlow explanatory schematic, synthesised from the method sources[1][2].
Understand the method
The parts in plain language
When to use it
- When leaders need a concise internal capability view.
- When a roadmap contains ambitions without credible enabling capabilities.
A practical workflow
- 1
List capabilities at a comparable level.
- 2
Assess strategic importance, current strength, defensibility and confidence.
- 3
Identify gaps and dependencies against strategic aims.
- 4
Route important capabilities into deeper analysis or roadmap action.
Fictional worked example
Example: capabilities for a connected service
This example is illustrative rather than a reported case. A manufacturer reviews the capabilities needed for a new digital service.
Observation:High importance and strong internal evidence.
Implication:Protect and scale the competence.
Observation:Important but weak and readily available externally.
Implication:Partner while retaining architecture ownership.
Observation:Low relevance to the chosen industrial model.
Implication:Do not invest because it is fashionable.
From analysis to decision
How to interpret the result
- 1Compare capabilities at a consistent level.
- 2Make confidence visible where evidence is weak.
- 3Connect selected action postures to sourcing decisions and the roadmap.
The interpretation guidance is an InnovationFlow synthesis of[1][2].
What a useful output looks like
Common pitfalls
- Do not mix resources, projects and capabilities without definition.
- Use deeper evidence before making irreversible sourcing choices.
References and method basis
- [1]Barney, J. (1991). Firm Resources and Sustained Competitive Advantage. Journal of Management, 17(1), 99-120. Source ↗Peer-reviewed research
- [2]Phaal, R., Kerr, C., Oughton, D. and Probert, D.R. (2012). Towards a modular toolkit for strategic technology management. International Journal of Technology Intelligence and Planning, 8(2), 161-181. Source ↗Peer-reviewed research
This guide synthesises the named sources into practical questions for strategy and innovation work. It does not claim that using a tool by itself produces a successful decision.