Basic patterns for capability map level 0
Download as PPTX, PDF11 likes4,533 views
The document discusses various business capability map patterns and their advantages and disadvantages, highlighting traditional hierarchical structures, service-oriented perspectives, and systems thinking. It emphasizes that these patterns reflect different organizational philosophies and can influence how businesses gather intelligence on their capabilities. The choice of structure often depends on the organization's vision and approach to service delivery or agility.
Basic patterns for capability map level 0
- 1. http://enklare.wordpress.com SOME BASIC BUSINESS CAPABILITY MAP PATTERNS (LEVEL 0) These Patterns are examples of structuring Business Capability Maps devised and designed by Jörgen Dahlberg ENVISION ENGAGE ENABLE ENSURE ENVISION ENABLE ENGAGE ENSUREEMPOWER ENVISION ENABLE EMPOWER ENCOURAGEENSURE ENGAGE Pros and cons What is good with the usual way of structuring is that it reflects the thinking on business organization the last +200 years. What is bad is that it solidify the rather old way of thinking about organizing a business. So why would one choose this pattern then? If it is more important to gather intelligence on capabilities than to try to impose organizational thinking via capabilities then it is highly effective. Does it always look like this? Basically, yes. However on occasions you will find the order of the boxes thrown around. THE HIERARCHY PERSPECTIVE THE SERVICE PERSPECTIVE THE SYSTEM PERSPECTIVE Pros and cons What is good with the service way of structuring is that it reflects the thinking on business as a service delivery organization. What is bad is that it can be a challenge to sell if people are stuck in the hierarchy way of organizing. So why would one choose this pattern then? If people think of their organization as a service delivery business or if they are on a path to become such. Does it always look like this? Basically, yes. However on occasions you will find that envision has switched place with enable. Pros and cons What is good with the systems way of structuring is that it reflects the thinking on business organization as a fractal structure. What is bad is that it comes very close to how one need to build the organization to run it. So why would one choose this pattern then? If one want’s to create a self organizing business that is highly agile on all accounts then this is the pattern to choose. Does it always look like this? Basically, yes.