Workshop 2: Workspace Admin | Lesson 1 of 7 | Workspace Design Flashcards
Explain the 4 key considerations that inform Enterprise Grid design.
Model & Structure
Roles & Responsibilities
Policies & Settings
Architecture & Security
Identify key benefits of a thoughtful Enterprise Grid design for Members.
Frictionless onboarding
Increased collaboration
Reduction in irrelevant noise and increased ability to focus.
Easy access
Increased efficiency
Identify key benefits of a thoughtful Enterprise Grid design for Admins
Decreased overhead
Automated management
Higher return on investment (ROI)
Increased security and compliance
Ability to scale
Enhanced analytics
Summarize the best practices for designing an effective Enterprise Grid org
Create workspaces based on how information is shared.
Create the minimum number of workspaces to meet your users’ needs.
Target 80%+ time in a “home” workspace.
Provide an overarching, easy-to follow structure to your Enterprise Grid.
Use multi-workspace channels (vs. a new workspace).
Consider your approach to external collaboration.
Establish workspace naming guidelines.
Core considerations for Enterprise Grid Design
Organization structure and size
Existing Slack workspaces and usage
Existing knowledge networks
Cultural dynamics & other factors
Technical Consideration of a Workspace:
Do I have someone to provide admin support to a new workspace?
Does this workspace need unique settings that are different from my existing workspace(s)? (e.g channel management settings, workspace-specific user groups, DND hours, etc.)
Do I have an existing SSO group on my IDP to support the provisioning of users to this workspace?
Determine when you should create a workspace or a channel to meet the needs of your organization.
Which of the following considerations should an organization prioritize in their Enterprise Grid design?
Select:
The # of multi-workspace channels they anticipate needing
Existing knowledge networks.
Custom terms of svc
The # of announcement channels needed to communicate to the whole team
Existing knowledge networks
Workspace
a shared hub made up of channels wherein team members can communicate & work together.
Which is FALSE of Enterprise Grid design?
It is a series of design decisions that impact how employees work w/in your Slack environment.
It is meant to be a static & unchanging framework to meet company goals.
It will likely be totally unique to your co.
Incl choices you make about the model & structure; roles & resp; policies & settings; & architecture & Security.
While it often takes place during the launch of a new Enterprise Grid org, it’s best practices are equally useful in guiding the maturation of Slack at your Org.
It is meant to be a static & unchanging framework to meet company goals.
Enhanced Analytics Data
to meas & promote success across org
Decreased Overhead
thru clear roles & resp at org, Workspace & memb levels
Frictionless Onboarding
memb can get work done in the rt place rt away
Reduction in Irrelevant Noise
incr ability to focus
Ability to Scale Over Time
w/ a clear & flexible structure
