This model is part of my toolbox for working with capability architectures.
The Capability Inventory
I know that there is certain ways of naming a capability and also that there are other principles that people and I promote that you should adhere to when designing your capability map. Here I’ve taken some liberties in regards to those principles to make it easier to relate to the possible content in the boxes. This inventory is basically what I refer to as “functions as capabilities“, now there is certainly a way of mapping proper capabilities into this inventory.
Download note: I’m currently in a process of changing my presentation design (the image shows what the new design looks like) for all my work. When I’ve stabilized the design and applied it across all canvases and related material I’ll link up the powerpoint to Slideshare.
When you should use this
- Whenever you set about designing a capability model of your enterprise
- When you need to understand what types of capabilities an enterprise can have
What you should consider when you use this
- This is not “the complete or correct” inventory of capabilities
- There is no known right way of designing or describing a capability of an enterprise
- There is techniques like reversing the names of processes and then consolidating them that could give you a fair hint of what capabilities you have in your enterprise
- Look at other peoples capability inventories and take inspiration from those
- The “best” capability inventory is the one you get enough people to use in their work
- Develop the capabilities and the capability inventory in as wide spread community as possible
- Continuously refine your capability inventory as you go
- In the end it’s all about just doing it
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Post change log
2015-06-15: Published initial post