Salesforce Slack Consultant

A project that cannot be measured cannot be defended. You plan phases and roles, agree what success looks like with the sponsor, and choose measures that will show whether the rollout worked.

• Phases, milestones and owners
• Choosing success metrics with the sponsor
• Baselines before the change
• Risks and dependencies
• Reporting progress to stakeholders

You build A project plan with success metrics and a baseline for each.

Many customers arrive with workspaces that grew on their own. You assess what exists, decide what to merge, and plan the migration to Enterprise Grid so that people and history move without confusion.

• Auditing existing workspaces
• Deciding what to merge and what to keep apart
• Migration paths into Enterprise Grid
• Moving members, channels and history
• Communicating changes to users
• Sequencing a migration to limit disruption

You build A consolidation and migration plan for a company with several workspaces.

Identity and apps decide whether the move feels safe. You set up SAML single sign-on for the new org, plan how existing apps are reviewed and reconnected, and avoid breaking the tools people depend on.

• SAML single sign-on setup
• Mapping identity attributes
• Reviewing the apps already in use
• Reconnecting and approving apps in the new org
• Testing sign-in before cutover
• Handling users who cannot sign in

You build A sign-in and app transition plan, with a test plan for cutover.

Grid structure sets how people work for years. You design the org and its workspaces, decide which channels are shared across them, and validate the design with the client before anything is built.

• Org and workspace structure
• Choosing workspaces by function, region or both
• Shared channels across workspaces
• Naming and structure standards
• Validating the design with the client
• Recording design decisions

You build A Grid design document, including workspaces and shared channels, ready for client review.

Policy turns design into daily behavior. You set org and workspace settings, assign roles and permissions to the right people, and advise on which settings should be centralized and which delegated.

• Choosing which settings sit at org level
• Roles and what each can do
• Permissions for creating channels and inviting people
• What to centralize and what to delegate
• Aligning settings with company policy

You build A policy and roles matrix for a customer’s Grid.

Accounts must follow the people. You plan provisioning from the identity provider, set up automated user lifecycle through SCIM, and use analytics to see whether the rollout is reaching the right teams.

• Provisioning from an identity provider
• SCIM and group-based provisioning
• Lifecycle events and automated access changes
• Reading analytics for adoption
• Using analytics to guide next steps

You build A provisioning design and an analytics review for one rollout.

Security teams ask hard questions before they approve a rollout. You advise on session length, data protection, audit logs and Slack Connect, and answer concerns with settings the customer can see.

• Advising on session and device policy
• Data protection and retention
• Audit logs and how they are used
• Controlling Slack Connect with outside partners
• Answering a security team’s questions
• Documenting controls for auditors

You build A security and compliance briefing for a customer’s risk team.

Apps multiply fast when no one is watching. You advise on app governance, set up approval workflows that review each request, and help the customer decide which integrations to allow, restrict or retire.

• Why app governance matters at scale
• Reviewing an app’s permissions
• Designing an approval workflow
• Allowing, restricting and retiring apps
• Measuring app sprawl

You build An app governance policy and an approval workflow for one customer.

Channels shape how information moves. You plan a channel strategy and naming approach, create templates that start channels well, and decide who may create and archive channels.

• A channel strategy for a large organization
• Naming conventions
• Channel templates for common work
• Creating, archiving and ownership
• Preventing channel sprawl

You build A channel strategy and a set of channel templates for a company.

A rollout lasts when people own it. You set up a governance team, define how the organization supports Slack day to day, and build training that fits the roles it serves.

• Forming a governance team
• Support models for a Slack org
• Role-based training plans
• Champions programs
• Gathering feedback from the first weeks

You build A governance and support model with a training plan by role.

Automation shows value early. You identify workflows that remove routine work, plan how they are governed, and sequence a launch that builds momentum rather than flooding people on day one.

• Finding workflows worth automating
• Designing a first set of workflows
• Governing who builds and publishes them
• Launch sequencing and communication
• Measuring early adoption

You build A launch plan with three starter workflows and the measures to track them.

Work a full engagement for one customer. You discover needs, plan the migration, design the Grid, set policy and governance, and present a launch plan that the customer’s leaders and security team can accept.

• Framing the customer’s needs
• Designing the Grid and migration
• Setting policy, security and governance
• Planning adoption and launch
• Presenting to sponsors and security

You build A complete Slack engagement plan for one customer, from discovery through launch.