Working with Salesforce Go combines feature discovery, guided implementation, and ongoing adoption measurement. The workflow below covers the standard sequence for using Go to roll out a new capability and measure its uptake.
- Open Salesforce Go and identify a goal
From Setup, search for Salesforce Go and open the page. Browse the available goals organized by business outcome. Pick one that aligns with the org's current priorities (Improve Sales Productivity, Reduce Case Backlog, Increase Newsletter Engagement). Review the features Go suggests for that goal, including recommended starting points based on the org's current configuration and license footprint.
- Run the guided implementation for a chosen feature
Click into the feature and start the guided implementation flow. Go walks through the prerequisites, the configuration steps, and the rollout suggestions. Complete each step with the recommended values or customize as needed. Save the configuration. At the end of the flow, Go offers next steps: train users, monitor adoption, schedule a review. Follow through on the next steps rather than treating the implementation as complete just because the configuration is saved.
- Roll out to users and track adoption
Communicate the new feature to the user community: brief internal email, training session, documentation in the team wiki. Encourage users to try the feature and provide feedback. Return to Salesforce Go after two weeks and review the adoption metrics: who is using the feature, how often, what specific actions they take. The data tells you whether the rollout is succeeding or needs intervention.
- Iterate and demonstrate value
Based on the adoption metrics, iterate on the rollout: provide additional training where adoption is low, simplify the feature configuration if users find it confusing, target specific user groups for re-engagement. Report the adoption story to leadership using the Salesforce Go reports: features enabled, users active on them, business outcomes connected. The reporting closes the loop between admin effort and business value.
- Enabling features in Go without user-facing rollout produces zero adoption. The guided flow includes rollout steps for a reason.
- Salesforce Go does not replace deep Setup knowledge. For complex configuration, you still need to understand the underlying Setup pages.
- Adoption metrics in Go are based on platform telemetry. Some features without rich telemetry produce limited adoption visibility.
- Goal taxonomies in Go are generic. Customize them for the org's specific priorities or the recommendations may not match what you actually care about.
- Enabling too many features through Go at once overwhelms the user community. Pace the rollout based on absorption capacity, not Go's recommendations alone.