ClickUp is one of the most powerful operations tools available - and one of the easiest to get wrong.
The product is unusually feature-dense. Spaces, folders, lists, tasks, subtasks, sprints, goals, docs, whiteboards, automations, time tracking, dashboards, custom statuses, custom fields, custom views. Every feature has a use case. None of them are mandatory.
Most growing businesses that adopt ClickUp end up using somewhere between 30% and 60% of the available features - and configure those features badly. The result is a tool that the team avoids because it feels heavier than it needs to be.
This guide is the setup we use with 20-person operations-led businesses. It is opinionated. It leaves features out deliberately. It is designed to be used by the team within two weeks of going live - not 'rolled out' over six months while people quietly keep using spreadsheets.
Before You Open ClickUp
Three decisions to make before you create the first Space.
Decide what ClickUp is for in your business. ClickUp can be a project management tool, a CRM, a knowledge base, a goal tracker, a sprint tool, or all of them at once. Pick one or two primary jobs and resist using it for more until those are working. For a 20-person operations-led business, the right answer is usually: project management + lightweight knowledge base. Sales tracking is better in a dedicated CRM. Goal tracking can come later.
Decide who owns the configuration. ClickUp gets messy when multiple people add features ad hoc. Appoint one person - often the operations lead or COO - who has the final say on structure changes. Anyone can suggest changes, but one person approves them.
Decide what you are migrating from. If you are migrating from Asana, Notion, or Trello, list every workflow currently happening in the old tool. ClickUp setup should replicate the workflows, not the structure. The structure is what you redesign.
The Top-Level Structure
ClickUp uses a hierarchy: Workspace → Spaces → Folders → Lists → Tasks. Most teams over-use the Spaces level and under-use Folders, which makes navigation painful.
The structure that works for 20-person businesses:
One Workspace - the company.
4-6 Spaces, organised by department or major function - not by client or project. Spaces are top-level navigation. People should know which Space their work lives in without thinking.
Typical Spaces for a 20-person business:
- ·Operations
- ·Client Delivery (for services businesses) or Product (for product businesses)
- ·Sales / Revenue
- ·Marketing
- ·Finance & Admin
- ·Internal (for internal projects, hiring, IT)
Folders inside Spaces - one folder per ongoing programme or project type. For Client Delivery, this might be one folder per client. For Internal, one folder per initiative (Hiring, Q3 OKRs, Office move).
Lists inside Folders - the actual project boards. Each List is one set of tasks with one set of statuses. Tasks live in Lists.
The mistake to avoid: creating a Space per client. At 20 people you might have 10-30 clients - 30 Spaces makes the navigation unusable. Clients live as Folders inside the Client Delivery Space.
Task Status Setup
ClickUp lets you customise statuses per List, per Folder, or per Space. Customisation is the second-biggest source of mess.
Start with these two status sets and use them across 90% of your work.
Standard project status set (for most operational work):
- ·To Do
- ·In Progress
- ·Blocked
- ·Review
- ·Done
That is five statuses. Resist adding a sixth until you have a documented reason.
Client delivery status set (for services businesses):
- ·New Brief
- ·In Scoping
- ·Active
- ·Awaiting Client
- ·Review
- ·Complete
These are the only two status sets most 20-person teams need. Specialty status sets (engineering sprints, content pipeline) can be added later for specific Lists.
The rule: a status should represent a meaningful change in who needs to act. "To Do" → "In Progress" is meaningful (assignee starts work). "In Progress" → "75% Done" is not - it is just a percentage update.
Custom Fields - Use 4, Not 14
Custom fields are powerful. Most teams add too many and lose the ability to filter usefully.
The four custom fields that earn their place for most 20-person operations:
Owner (single user) - separate from assignee. The assignee does the work; the owner is accountable for the outcome. Often the same person, sometimes different.
Priority (dropdown: Urgent / High / Normal / Low) - ClickUp has a built-in Priority field. Use it. Do not create a duplicate.
Due Date - ClickUp built-in field. Make it visible in default views.
Effort Estimate (number or dropdown of S/M/L/XL) - lets you plan capacity. Without this, you cannot forecast workload.
That is it. Tags, departments, client names, and similar should be communicated through Folder/List location, not custom fields. If you find yourself filtering by a custom field that should have been a folder, restructure the folder hierarchy instead.
The 5 Automations That Save Real Time
ClickUp Automations is one of the most underused features. Most teams either ignore them or set up 30 of them and forget what they do.
The five automations every 20-person team should have:
1. When status changes to Blocked, assign to the team lead. Prevents tasks from being silently stuck. Forces escalation through the structure.
2. When status changes to Review, notify the owner. The person accountable for the outcome reviews before the task closes.
3. When status changes to Done with no time tracked, post in #ops to log time. For services businesses where time tracking matters. Forces accountability.
4. When a task is overdue and still in 'To Do', notify the assignee and post in the team's daily standup channel. Prevents tasks from quietly slipping past due dates.
5. When a new task is created in the Client Delivery Folder, auto-add the standard onboarding subtasks. Eliminates manual checklist creation for repeating workflows.
Five automations is enough to materially reduce manual work. Adding more without measurable benefit creates the same problem as too many custom fields.
The Three Views Everyone Needs
ClickUp supports a dozen view types. Most teams need three.
My Work (built-in) - every team member's primary view. Shows what is assigned to them, due this week, sorted by priority. Set this as the default home view for everyone.
Team Workload (Workload view) - for managers. Shows what each person is working on, capacity, and overdue items. Reviewed in the weekly 1:1.
This Week Across the Business (saved Filtered List view) - for the operations lead. Shows everything due in the next 7 days across all Spaces. Used in the Monday morning leadership stand-up.
That is enough for a 20-person team to operate. Gantt charts, calendar views, and timeline views can be added per-Space for teams that need them, but should not be defaults.
What to Skip in Phase One
ClickUp has many features. Most are good. None are mandatory for a 20-person setup.
Skip these in your first three months:
Goals. ClickUp's Goal feature is sophisticated but adds overhead. Track OKRs in a dedicated tool or a simple doc until ClickUp itself is being used daily.
Sprints. Unless your team is already running formal sprint cycles, the Sprints feature adds structure without benefit. Plain Lists with status workflows are simpler.
Time tracking. ClickUp's time tracking works, but adoption is hard. Use only if the business needs time data (consulting hours, client billing). Otherwise skip.
Whiteboards. Use a dedicated whiteboard tool (Miro, FigJam) for visual collaboration. ClickUp Whiteboards are functional but rarely the best option.
Forms. Useful for intake processes (new client requests, internal tickets) but should be added only when you have a specific form to replace - not pre-emptively.
Dashboards. Powerful but easy to mis-configure. Build dashboards after the team has been using ClickUp for 2-3 months and you know what data actually drives decisions.
The Two-Week Rollout
Setting up ClickUp is not the same as adopting ClickUp. Most 20-person teams fail at adoption, not at setup.
The rollout that works:
Week 1: Configure the Spaces, Folders, and Lists structure. Migrate active work from the old tool. Get one team (usually Operations) using it for real.
Week 2: Add the second team. Use the first team as the reference. Run a 30-minute live training session per team. Document the basics in ClickUp itself - a Doc in the Internal Space called "How We Use ClickUp."
Day 14 onwards: Hold the line. People will ask for new features. Resist for the first 60 days. Let the basic structure prove itself before adding complexity. New features can be added monthly during a review cadence - not whenever someone has a new idea.
After 60 days, evaluate what is missing and add deliberately. The teams that stick with ClickUp long-term are the ones who under-configured at the start and added features only when the use case was proven.
The Honest Trade-Off
ClickUp is not the only good answer for a 20-person team. Asana, monday.com, Linear (for engineering-heavy teams), and Notion (for very small teams that mostly need docs) all work.
What ClickUp does better than alternatives: the breadth of features in one tool. What it does worse: the cognitive load of having so many features available.
If your team is operationally mature and wants flexibility, ClickUp is a strong choice. If your team is early and wants simplicity, monday.com or Asana is often easier to adopt. If your team is engineering-heavy, Linear is purpose-built.
The decision is not which tool is best in absolute terms. It is which tool fits how your team actually works - configured by someone who knows what to leave out.
The Most Important Configuration Decision
Whichever tool you pick, the single highest-leverage decision is what NOT to use.
Tool sprawl is rarely about choosing the wrong tool. It is about configuring tools without restraint. Five well-used features will produce better outcomes than thirty features that nobody fully uses.
Start with the structure above. Skip the optional features for 60 days. Add complexity only when the team is asking for it - not when you imagine they might need it.