Use capabilities as stable anchors
Explain why capability maps are better transformation anchors than applications or reporting lines.
The move: anchor volatile change to stable enterprise abilities. Capability, not department A department says who is arranged to do work today. A capability says what the enterprise must be able to do regardless of reporting line. Capability, not process A process shows sequence. A capability shows ability. "Resolve service exception" can be implemented through several processes, teams, tools, and policies. Capability, not application An application is one way a capability is automated or supported. If the application changes, the capability may remain. Use capabilities as the join point for strategy, systems, data, risk, cost, and initiatives. That gives leaders…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in