Designing businesses is not a trivial activity. Having a simple structure that one can use to design and / or understand a capability makes designing business architecture so much easier.
The Capability Canvas
When you should use this
- When setting up Agile as described in “Kanban: When is it appropriate? (part 1) | DJAA” you can use a capability map and the capability canvas to figure out a great “product structure”
- When figuring out what capabilities to grow as described in this McKinsey report: Building capabilities for performance
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
I’ve cleaned up the descriptions of the elements to make it easier to work with.
- PROCESS – Renamed “using” to “associated with ”.
- SERVICE – Renamed “enabled” to “associated with ”.
- INFORMATION – Renamed “produced, consumed and manipulated by” to “associated with ”.
- TECHNOLOGY – Renamed “supporting” to “associated with ”
- ORGANISATION – Changed spelling to US format.
- VALUE – Renamed “attributed to” to “associated with ”
- INVESTMENT – Renamed “we have done, do or plan to do on” to “associated with ”