Capability Mapping


A capability map is a visual outline of the capabilities an organisation currently possesses and the capabilities that should be prioritised to reach a desired future state.
The idea is to map your business capabilities against your strategic outcomes.
A capability map differs from a capability framework (which looks at illustrating skills, knowledge and behaviours) in that it focuses on visualising core business drivers (aka capabilities) by their level of priority in value chains or business functions.
A capability map provides a more helpful bird’s eye view of how your business works than other visual aids. It keeps the focus on your big picture and aligns internal business processes with people and technology.
It’s like a companion for all your other planning, strategy and business documents and allows you to undertake gap analysis more accurately.
Business capability maps are usually arranged in a hierarchy to display their granularity.
At the highest level, there are a few capabilities that are core to business success, each being followed by a set of complementary capabilities that support them.
At this level you are creating a logical way to flesh out and organise your lower levels. It’s common to define business capabilities based on value streams/chains or key functions that take you from conception to market. There’s no ‘ideal’ number of core capabilities at this level.
This level gives you the necessary detail to make more informed strategic and resourcing decisions. A key point is that you don’t need the same number of sub-capabilities for every core capability. It’s about the drivers defined as critical to your business.
In most cases, 2-3 levels of sub-capabilities are enough. However, some organisations go deeper. This granularity further ensures the right capabilities are represented at that second level.
smaller companies or those undertaking capability mapping for the first time, this level of granularity is usually not needed. It’s more common in mature organisations who may use a capability map from an operational viewpoint.
There should be more than one champion in your organisation for a capability map, at multiple levels of your organisation.
Buy-in needs to be based upon capability mapping being a pain killer, not just a nice-to-have supplement.