Naming a capability | The #1 reason no one understands your map.

When you have mapped your capabilities, it can be very challenging to clearly define what each capability is to your team. This is usually because we only want to focus on what the capability is when we name it – not the how, who or why.

Subscribe ►
***************************************
Jibility Resources
See how we do capability planning in Jibility:


What is capability-based planning?


What is a capability map?


***************************************

When trying to construct the best name for a capability, we often focus on who’s involved, how it works, or why we have it. A capability is the combination of all three and it is important to name it accordingly.

We use the method of -ing, -ion, -tion, -ment. So, whatever your capability is, the name for it must end in one of those suffixes in order for it to be clearly defined in a way that can encompass all aspects of the building block. For example: “health management”, “software configuration”, “graduate training”.

The key point of this video is to explain how to name a capability.
You will also learn:
Other ways to name your capabilities
How to avoid confusing terminology
Ways to explain a capability more clearly

Timestamps:
1:42 - The what or how
3:01 - Naming capabilities
4:09 - Capability naming examples

Be sure to subscribe for more agile business strategy tips and tutorials.

Find out more:
Jibility ►
YouTube ►
Facebook ►
Twitter ►
LinkedIn ►

Get your free 30-day trial today:

capability,mapping,capabilities,map,roadmap,software,tool,business,strategy,naming,name,