How to Roll Out ClickUp Across a Team of 10–50 (Step-by-step guide)

There is one particular way of rolling out a work management platform like ClickUp for teams under 50 that by far results in the best adoption outcome. I call it the coaching method, and it's quite different from what you'll hear from most conventional tool implementation experts.

In this post, I'm breaking down the coaching method step by step so you'll know how to roll it out across your own company. I've also recorded a full video walkthrough if you want to see each phase in action.

A quick scope check before we dive in. This is for a full-org rollout — not a single project, not one sub-team. If you just want to manage one campaign in ClickUp, this isn't the post for you.

What Is the Coaching Method?

The coaching method, in short, is coaching your team to configure and set up ClickUp themselves — rather than the typical approach of having someone set it up and then hand it over.

It is by far the most effective way of building internal capability in process management and tool knowledge. It also saves you from having to document SOPs and processes in advance, since these get built directly into the tool by the people who know them best.

The coaching method divides your team into two groups.

Changemakers. Usually the lead, or the person most knowledgeable about how work actually flows in their function. They are the ones you coach to set up ClickUp for their area and onboard their own team.

Typical users. Everyone else. They learn from the Changemakers.

A rollout using the coaching method typically spans five phases.

Phase 1 — Design

This phase is about laying the groundwork. Even though the whole point is to get your people to set up ClickUp themselves, you still have to plan how you're going to coach them — just like a teacher prepares a curriculum before the class. In this phase, you want to understand the scope of the rollout and identify who your Changemakers could be.

Step 1: Produce an organisational structure map.

This is not an org chart. You're not mapping reporting lines — you're mapping work packages. Recurring tasks, projects, and areas of responsibility, clustered into functions. You'll also want to map cross-functional work (workflows that involve multiple functions but are typically owned by one department) and company-level work (the rhythms that involve everyone — all-hands, OKRs, company-wide strategic projects).

Step 2: Draft a structure proposal for the tool.

Now that you have the map, it's much easier to see what needs to be covered within ClickUp. The first decision is the number of Spaces, because this directly determines the number of Changemakers you'll need to involve.

A useful default is one Space per major functional area. But Spaces should follow operational ownership, not organisational labels. What this means in practice: if a function has a distinct owner, runs meaningfully different workflows, and has a need for autonomy in organising its own work, it needs its own Space — even if it formally sits inside another department on the org chart.

Once you've settled on Spaces, provide some thought starters for each one. These don't need to be polished. They're a starting point for colleagues who may not be familiar with ClickUp at all. The owners you identify here become your Changemakers.

Step 3: Have 1:1 conversations with your potential Changemakers.

Do this before anything is official. Let them know what's coming and what you're going to ask of them. These conversations build early buy-in and let you assess technical comfort and willingness — information you can use to tailor your coaching later.

If someone isn't willing or able to be a Changemaker, ask them to nominate someone from their function who can be.

And — this is important — just as you're asking for their commitment, you have to commit back. Specifically, you need to give them the time and the permission to prioritise this. If you don't, the rollout will fail.

Step 4: Make a first draft of the workspace setup.

Build a rough version of the structure in ClickUp. Not a fully fleshed-out one — just enough to give Changemakers something to react to. One folder instead of four, for example, so they can see that there are different ways of using ClickUp and get exposure to the different views available.

Deactivate features the team doesn't need yet. Fewer options means faster adoption. And flag this clearly as a draft — you don't want anyone walking into the kickoff thinking it's set in stone.

Step 5: Create a project timeline.

Draft the rollout schedule across all five phases and share it at the kickoff. Your Changemakers will need to commit to it, so they should have input.

Phase 2 — Changemaker Kickoff

The kickoff is where the rollout becomes real for your Changemakers. This is a working session — not a presentation. You walk them through what you've built, explain the coaching relationship, and get their commitment to their role and the timeline.

Every Changemaker should leave this meeting knowing what they're building, with access to the workspace, and with a timeline they've agreed to.

Phase 3 — Build and Refine

Since the kickoff, your Changemakers have gone back and started building in ClickUp. During this phase, you want to have 1:1 check-ins with each of them.

Keep these as 1:1 meetings, even though it may not feel like the most efficient use of your time. Most people shy away from asking questions in a group setting, and what's relevant in one function often isn't relevant in another.

In each 1:1, get them to walk you through what they've built. Ask clarifying questions. Use the time to evaluate how each Space setup affects the other Spaces in the organisation — specifically, look at how they've designed their statuses and custom fields, and whether they're using different naming conventions for the same things. You want each Space to have enough autonomy while maintaining a consistent baseline that other functions can understand.

If there are disagreements — particularly around cross-functional workflows — use this phase to bring the relevant Space owners together and work it out.

Phase 3 is also when you prepare the documentation for go-live. The three most important documents:

• A running FAQ — start capturing questions as they come in and keep it updated throughout.

• A ClickUp onboarding guide — covering basic features for people new to work management platforms.

• Your Ways of Working document — the company-specific rules of the road for how the entire team uses ClickUp.

I'd recommend housing all of this in a company wiki inside ClickUp itself — one centralised place where anyone can find it.

Finally, stress-test the setups with real or partial real data. When you and the Changemaker agree it holds up, you move to Phase 4.

Phase 4 — Team Activation

This is the point where the rollout expands beyond the Changemakers and reaches the rest of the organisation.

Start with a company-wide onboarding meeting. Use it to explain where the rollout currently stands, what has already been set up, when teams are expected to begin moving their active work into ClickUp, and where to find the resources you've prepared.

Just as importantly, use this moment to establish company-level usage expectations. How will ClickUp show up in the operating rhythm of the business?

• Will weekly priorities be reviewed there during standups?

• Will company-wide projects be tracked there?

• Will leadership updates live in wikis, or continue to be shared in Slack?

• Will there be dashboards for company-level visibility?

This matters because company-wide usage signals commitment from leadership — and it shows people that their individual work is contributing to a larger operational picture.

After the all-hands, three things happen:

• Each Changemaker runs their own team onboarding. You can join if useful, but they should lead it — they understand the workflows in their area better than you do.

• Each function migrates active work into ClickUp. Focus on current projects, recurring workflows, and near-term commitments. Don't waste energy migrating historical tasks.

• Teams begin working in ClickUp for real.

Phase 5 — Behavioural Correction

The tool is live. Now you watch. And adjust.

The rollout does not stop at go-live. It's only done when people have adopted it into their actual working patterns. That takes time, and it's normal.

Spot checks. Are tasks being updated? Is work happening in the tool, or around it? Are people using the agreed fields and statuses? Are meetings and decisions being reflected back into the system?

You don't need to be heavy-handed about this. What you're looking for is friction, confusion, or signs of backsliding. A direct message to the person is usually enough.

"Hey — I noticed this project is still being tracked in spreadsheets. Is something not working here?"

That tends to tell you very quickly whether the issue is unclear process, tool friction, or simple habit. If the same question comes up more than once, update the FAQ or address it in the next team meeting.

Maintenance meetings with your Changemakers — every two weeks or so. How are people responding? Any bottlenecks? Anywhere the system is being ignored? What needs adjustment?

This is also when you make small refinements — deleting unnecessary fields, simplifying a workflow that's proving too complex in practice. Over time, reduce the frequency of these meetings until working in ClickUp feels like second nature.

The Bigger Point

Rolling out ClickUp across a team of 10 to 50 is a behaviour change project that happens to involve software. With the coaching method, focusing on the cultural shift is what allows your organisation's systems to evolve beyond the limits of any individual tool.

If you want to see the full walkthrough — including the org structure map, the workspace design process, and how each phase looks in practice — watch the video here.

📌 I'm also putting together a comprehensive ClickUp implementation guide — including an org structure map template, a 90-day project plan, and all the document templates mentioned above. Register your interest here and I'll notify you when it's ready.