We’re in the middle of implementing Strategic Planning Workspace and are running into a very common challenge: end users are overwhelmed by enterprise-level noise.
By default, many users land in SPW and see goals and plans that have nothing to do with what they own or are accountable for. We’re intentionally trying to avoid hard security controls or org-chart-based restrictions and instead lean on platform-supported patterns.
What we’re currently exploring is an ownership- and contribution-based approach:
-Default views/lenses centered on items a user owns or is explicitly shared on
-Optional filters (portfolio, product, timeframe, etc.)
-Treating Business Unit and org structure as metadata/reporting dimensions, not primary visibility drivers
We are not using lenses as security boundaries and are avoiding custom ACLs on core SPW tables.
I’m curious how others have handled this in practice:
-How are you reducing noise for business users in SPW?
-Are you leading with ownership, org structure, or something else?--
-Have Business Unit or department-based lenses actually worked well at scale?
-Any lessons learned once real users started using SPW day-to-day?
Appreciate any real-world experiences, especially what didn’t work.
