This article will cover the pros and cons of using the two different Huddle types in SalesHood, as well as some logic for each type. Use this as a reference when creating paths, so that you know which type is best for your program.
Open Huddles are characterized by their lack of due date and absence of a Host. When added to a Learning Path with a due date, the users assigned to the Huddle will still be required to finish it by the due date, and this will reflect on the Path level.
Open Huddles are great to use for subjects you’d like your teams to be able to return to and look at anytime. In SalesHood, each Open Huddle is a single object meaning if it is added to multiple Learning Paths, you will see participants in the list from each Path, as well as any users that have found it via the Library and participated it.
When to Use
- Open Huddles are great to use in Paths that you would like to clone later on and make adjustments to, without affecting the previous Learning Paths they were cloned from. This is because each Open Huddle is a unique, separate object with a different URL in SalesHood, independent of any previous versions you’ve created.
- When participants submit responses in an Open Huddle, their Manager is notified only (this is also dependent upon the notification settings in your instance). For more on Notifications, see this Knowledge Base article.
Items to Consider
- Each clone that is created (either by cloning an individual Open Huddle or an entire Learning Path) will create a separate Open Huddle object with a unique URL in the system. This may cause confusion later down the line if the clone retains the same name as the previous version. As a rule of thumb, the bottom-most Huddle with the same name is the most recent version when adding to a Path.
- Confidential settings may also become an issue later down the line if you wish to ‘retire’ or ‘archive’ a Learning Path that users have completed. Once an Open Huddle is placed into a confidential category, any users that have completed the Huddle or Path will lose access to Open Huddles, because they are considered unassignable content.
Scheduled Huddles have both a Due Date and Host, as well as a single Template with Event pages within each Template. In Learning Paths, the Huddle will adopt whatever due date is assigned on the Path level. Think of each Huddle Template as the ‘master’ as well as an index where the Huddle can be edited. Think of each Event as a child that is dependent on the parent Template.
When to Use
- Scheduled Huddles are great for staying organized. By using the global search bar, you can easily find your Scheduled Huddle Template, and contained in it will be each Learning Path that the Huddle Events have been added to.
- This allows you to re-use the same content while keeping the participant list and completion separate.
- When adding a Scheduled Huddle to a Learning Path, the search will display any Scheduled Huddle Templates with that name, and selecting that Template will automatically create a new Event attached to that Template.
- When a Scheduled Huddle is participated in, the Host as well as the participant user’s Manager, are notified (this is also dependent upon the notification settings for your instance). For more on notifications, see this Knowledge Base article.
- Finally, as long as the user has been assigned to the Learning Path(s) or to the Huddle itself, all users will not lose access when placed in a confidential category.
- When cloning an individual Scheduled Huddle, this will create a clone of the Template. When cloning a Learning Path that a Scheduled Huddle has been added to, this will create a new Huddle Event within the Template.
Items to Consider
If any edits are made to the Scheduled Huddle Event, all changes will apply to both the template and all other Events. This includes deleting, adding or removing modules, and any edits within the modules themselves. This may have a cascading effect on participation in separate Events if the content is removed from the template that has been completed by your users.
If you have any questions or need further assistance with this feature, please reach out to firstname.lastname@example.org.