Your client insists on designing their grid based on the company’s org chart and creating workspaces for each department. Through discovery, you…

The most appropriate best practice is to design the Grid structure based on how people actually work, not a rigid organizational chart. Since discovery revealed that departments are highly collaborative, creating workspaces for broad, cross-functional business units or value streams is the recommended approach. This design facilitates seamless collaboration across departmental lines, reduces the friction of working in separate, siloed workspaces, and aligns the Slack architecture with the company's collaborative culture. It provides structure without creating unnecessary barriers.

A. Following the client's org chart design: This would create digital silos that directly contradict the company's collaborative nature, hindering the very cross-functional work that needs to be supported.

B. Creating a single workspace for the entire organization: For a large company, a single workspace can become chaotic, difficult to navigate, and hard to administer, leading to information overload.

D. Creating workspaces for each department: This is the same as following the org chart and would create the silos that the best practice aims to avoid in this collaborative environment.

1. Slack Help Center. (n.d.). A guide to Slack Enterprise Grid administration. Retrieved from https://slack.com/help/articles/360001809983-A-guide-to-Slack-Enterprise-Grid-administration. (See section: "Design your org structure," which explicitly states, "Think about how people work together, not just your org chart.").

2. Slack. (n.d.). Slack Enterprise Grid: A guide for admins and owners. (This foundational guide for Enterprise Grid emphasizes designing the structure to support collaboration and business objectives, often recommending grouping by large functions or divisions rather than strict departmental lines).