Scaling six departments without a standards war
A 400-person company has grown from one operations team to six departments, each with its own monday.com workspace. There are 120 boards, 18 board templates, and at least five variants of status labels: Done, Complete, Finished, Closed, and Shipped. Every department has its own intake board, and two departments built near-duplicate vendor management boards. The executive team wants a single portfolio dashboard and cross-department handoffs from Sales to Delivery to Support. Department leads resist central control; the admin team has 1.5 FTE and cannot review every board. A previous standardization attempt renamed status labels in 40 boards and broke several automations, so trust is low. The company is on Work Management Advanced with 400 seats and wants to scale to 700 next year.
1. Propose a scaling operating model that gives departments autonomy while enabling cross-department reporting, including workspace and board structure.
Read the worked answer
Use a federated model: central standards, departmental ownership. Create a small governance group with one lead per department and the admin team; it owns the template catalog, naming convention, and status dictionary. Keep departmental workspaces for local execution and permissions, but create a shared Portfolio workspace for cross-department reporting and handoffs. Common processes-vendor management, intake, project delivery-get one approved template; departments can extend it with local columns but cannot fork the core statuses. A center of excellence, even at 1.5 FTE, can review new board requests against a checklist rather than every board. Name boards with department-process-year, and require a board owner and backup. This gives leads autonomy over their workspaces while the portfolio workspace provides the single executive view. Because the company is doubling seats, the model must be self-service; the center of excellence should publish templates and office hours, not manually build every board.
2. How would you standardize status labels and process handoffs without repeating the automation breakage?
Read the worked answer
Do not repeat the bulk rename. Inventory every status column, every automation, every filter, and every dashboard that references the five labels; map each legacy label to a standard label and a migration owner. Pilot on two low-risk boards: duplicate the board, rename in the copy, run the automations, and compare results. Then migrate board by board with a checklist: update automations and filters first, rename the label, test the trigger and action, and confirm dashboards. Keep a rollback copy until the board has run cleanly for a week. For cross-department handoffs, standardize only the handoff statuses-Ready for Delivery, In Delivery, Delivered-and allow local sub-statuses inside each department. Communicate the mapping and the reason: reporting and handoffs, not central control. This avoids breaking automations because the change is tested per board and the automation owner is part of the migration.
3. When should a team get a new workspace, a new board, or a connected portfolio board? Give decision rules.
Read the worked answer
Decision rules: a new workspace when the primary need is a permission or security boundary-external agencies, HR, Finance-or a distinct department that needs its own admin. A new board when the work has a different lifecycle, different columns, or different board permissions; do not create a board just for a new stage or a new group. A connected portfolio board when the need is cross-board rollup, executive reporting, or a handoff between departments; it should read from source boards, not become the daily work surface. Before any new board, check the template catalog and search for an existing board with the same process. Use groups for stages and subitems for checklists. Because two departments already built duplicate vendor boards, the governance group should merge them into one template with departmental views. This keeps 120 boards from becoming 200 and preserves a single portfolio view.