successor capabilities
The term "successor business capability" isn't as common in business capability management as other concepts like dependencies or hierarchies. However, there are two main ways to understand it:
1. Capability Evolution (Less Common):
This interpretation suggests a scenario where a business capability has been replaced by a newer, improved version. The original capability is then considered the predecessor, and the new one, the successor.
Example:
Predecessor Capability: Manual Order Processing
Successor Capability: Automated Order Processing System
In this instance, the organization might have transitioned from a manual system for processing orders (predecessor) to a more efficient automated system (successor).
It's important to note that this approach is less frequent. Business capabilities are often viewed as ongoing functionalities, and advancements are typically reflected in updates or improvements to the existing capability description, rather than entirely replacing it.
2. Focus on Improvement (More Common):
A more common way to view successor capabilities is through the lens of continuous improvement. This perspective acknowledges that capabilities can evolve over time, incorporating new technologies, processes, or best practices. In this sense, the improved version can be considered a successor to the original capability.
Here's an example:
Original Capability: Marketing and Sales
Focused on traditional channels like print advertising and telemarketing.
Successor Capability (Improved Version): Digital Marketing and Sales
Leverages online channels, social media marketing, and marketing automation tools.
Here, the core functionality of marketing and sales remains the same (generating leads and converting them to customers). However, the successor capability reflects an improved approach that utilizes advancements in technology and marketing strategies.
Key Points:
"Successor business capability" is not a standard term in business capability management.
It might refer to a completely new version that replaces an older capability (less common).
It can also signify an improved version of an existing capability that reflects advancements and best practices (more common).
The most fitting interpretation depends on the specific context and how your organization manages its business capabilities. If focusing on ongoing improvement is the preferred approach, then documenting successor capabilities (improved versions) can be a valuable way to track progress and ensure your capabilities remain aligned with strategic goals.