Objective Paths

Goals/Roadmap path is comprised of three level objectives: High > Mid > Detail. Collectively, this is an Objective Path. They may or may not have Recommendations & the detailed content that goes within it. As a result, they must have a ‘relationship’ to a Content Group. This helps control the user experience to set specific content visible or not. Roadmaps have Objective Paths. After creating a Goal/Roadmap, it is important to set at least one Objective Path Relation, (i.e., Set a relationship to a content group). For example, if a sub-set of advisor users in SuccessPro will be working on Advisor Success Goals and several goals/Roadmaps have been written & configured, then these should have that Objective Path Relation set.

In this example, the Objective Path is Advisor Success Program > Build Your Business Development Process > Build Your Sales Pipeline Tool.



Create an Objective Path


Click on Objective Paths to get started.


Starting at the High Level, click on Add

Repeat steps for Mid & Detail Levels. Each level will require a name. It is recommended to give a description and sequence.

Click Edit Objective Path Content


Click on View/Edit to provide a Name of the Goal. Update settings for the path where applicable. Progress is Calculated should be checked for automated progress complete calculations. Set the number of days for the default e.g., Goal/Roadmap will be due in 60 days in the example below.


Click on Add Recommendation. In this example, a fourth Recommendation (aka: Task) would be created. The sequence in which the Recommendation displays when the Goal/Roadmap is created.


Click the Active checkbox. A name is required. Instructions/Description are known as the ‘detailed content’ for the recommendation/task. Although it is not required, it is a Best Practice to complete this form to provide more context around what the recommendation/task entails. The sequence will control the order in which the recommendation displays on the Goal/Roadmap. Check the Searchable checkbox enable the searching within the quick content module and from the "Add Custom Rec" dropdown of the roadmap editor. Default Selection State will save the user experience from extra clicks if this is checked, otherwise the user must manually select it each time the Goal/Roadmap is created. Default Due Date Offset allows an override from the default where the Recommendation due may be set earlier. For example: Enter `30` to default this recommendation to be due 30 days before the goal if the goal is set for 60 and the default is due in one month.


Example of user experience when viewing content configured in Instructions/Description.

Enable any applicable Tags with the Objective Path.

Goal Tags are helpful in reporting and analysis