Explaining the Succession Nomination Methods

Succession Management has three main nomination methods to support various processes and strategies for our customers. Only one method can be chosen, and each method has unique benefits.

• Role-Person
• Position (Legacy)
• Metadata Framework (MDF) Position

The three succession nomination methods will be briefly discussed in this PTO. However, the screenshots in this guide display the MDF Position Nomination method because it is the preferred method to be implemented for new customers.

Customers upgrading from one method to another should use caution due to the possibility of data loss during the transition process. This is another reason customers are strongly encouraged to start new implementations using the MDF Position method.

The Role-Person Nomination method (Incumbent-based) is typically used for replacement planning. Successors are nominated to role/unique person combination (e.g., job code + user ID). Job codes and roles must be defined, and this method of succession planning is focused on the person or incumbent rather than the position itself.

For example, a company may select the Role-Person Nomination method if they have grown quickly and do not have strong position alignment in place or need a more simplified method of administration or maintenance. Yet, it is important to note that successors follow the incumbent if an incumbent changes jobs and does not stay in the position. All successors are dropped from the succession plan if an incumbent changes jobs.

Role-Person is no longer a recommended nomination method to use, and new customers are strongly encouraged to implement the MDF Nomination method instead.

There are two nomination methods utilizing the Position Model. The Position Model means these methods focus on the position rather than the person or incumbent. All nominations and successors remain with the position regardless of the movement of the incumbent.

The Position Nomination method (also known as Legacy Position) was historically selected for its compatibility with older permission models. However, with all customers having moved to Role-Based Permissions (RBP) and the use of MDF Talent Pools, new customers are being advised to implement MDF Position Nominations.

The MDF Position Nomination method builds on our most sophisticated platform feature, the Metadata Framework (MDF), which uses generic objects (GO). MDF puts control back into the hands of your company's administrator by broadening the position object capabilities within the Admin Center.

Some powerful benefits in configuration, tracking, and permissions include creating custom fields unique to your organization within the position details, utilizing effective dating of positions to capture historical changes to a record, and providing more granular permissions and targets to restrict sensitive information.