Skip to main content
Adaptive Planning
Last Updated: 2023-06-23
Reference: Best Practices for Adaptive Planning Hubs

Reference: Best Practices for Adaptive Planning Hubs

Consider these best practices to help ensure a smooth user experience, enable participants to understand the current functionality, ensure data security, and provide feedback.

Start small

  • Begin with a single hub for one department or workflow such as Financial Planning Hub.
  • Limit early pilots to a few groups to validate access, performance, and adoption.

Focus on relevance

  • Include only the most essential pages, links, and widgets to reduce cognitive load.
  • Use Groups to structure related content logically.
  • Ensure the Workflow widget surfaces insights that are truly actionable.

Keep layout consistent

  • Use a consistent structure across hubs to make navigation intuitive.
  • Maintain uniform naming conventions for Pages and Groups.
  • Place the Workflow widget in the same general location across hubs.

Manage updates carefully

  • Test configuration changes in draft hubs before republishing.
  • When cloning hubs, always revalidate page links, widgets, and permissions.
  • Archive old hubs instead of deleting them to preserve configuration references.

Monitor feedback

  • Encourage users to report usability or performance issues through designated feedback channels.
  • Track recurring themes for improvement.

Manage updates carefully

  • Test configuration changes in draft hubs before republishing.
  • When cloning hubs, always revalidate page links, widgets, and permissions.
  • Archive old hubs instead of deleting them to preserve configuration references.

Collaborate across teams

  • Partner with UX, Adaptive Planning admins, and security to ensure hubs follow consistent design and access standards.
  • If integrating with other Workday products, validate that connected workflows and permissions align correctly.

Manage hub security

  • Grant the Hub Administrator (with
    Edit Hubs
    permission) user type sparingly by limiting it to a few trusted users. This ensures that admins retain control over configuration, while business users can interact confidently with the content they need.
  • Use group-based permissions for scalability. This also ensures that hubs remain secure, organized, and tailored to the right audience.
  • Align the Hub Contributor (with
    Access Hubs
    permission) user type with teams responsible for content upkeep such as finance or HR analysts.
  • Regularly review and audit hub permissions, especially after reorganizations or role changes. Consistent governance enables smooth scaling from pilot environments to production rollouts.