Running EOS in ClickUp: What to Actually Build (and What to Skip)

What the standard templates get right

Rocks as tasks with milestones underneath them is the correct shape — a Rock without sub-tasks is just a title, and nobody can tell on Tuesday whether it's actually moving. A Scorecard as a live dashboard beats a spreadsheet someone updates by hand every Monday, purely because it can't silently go stale without someone noticing the numbers stopped moving.

Where template installs quietly fail

• Custom fields get added because the template suggested them, not because anyone's dashboard actually needs to filter or sort by that field — six months in, half the fields are empty because nobody was ever going to fill them in during the actual work
• The Space and folder structure mirrors ClickUp's own defaults (or the template author's org) instead of your accountability chart, so the person accountable for a function can't find their own work without three clicks through folders built for someone else's company

The three things worth actually building

One: a single Scorecard view the leadership team opens Monday morning by habit, with each metric's owner tagged to a real person on the accountability chart, not a department label.

Two: Rocks linked directly to the tasks and sub-tasks that deliver them, in the same tool people already work in — a Rocks list that lives separately from the actual work is exactly the kind of thing that gets checked once a quarter and ignored the other twelve weeks.

Three: an IDS/Issues list that persists and carries context forward, instead of a fresh list every Monday that loses the history of why an issue keeps reappearing.

What to skip

Don't rebuild the Vision/Traction Organizer as a database — it's a document people read a few times a year, not something that benefits from custom fields and filtered views. And don't build automations on top of the structure until the team has used the base setup consistently, unautomated, for at least 60 days — automating a workflow nobody's actually settled into yet just automates the wrong version of it.

Who owns the ClickUp instance once it's live

Someone specific, by name, not "whoever set it up." Fields drift, dashboards get cluttered with one-off views, and Spaces sprawl the moment there's no owner checking that the structure still matches how the team actually works six months later. That's usually the same person who owns the Process Component discipline, if there is one — the mechanisms are similar even though the artifacts are different.

A simple structure that maps to your accountability chart

A practical layout is one Space for the leadership team and one Space per major function on the accountability chart, named the way the team actually talks about those functions. In the leadership Space, keep three lists: Rocks for the current quarter, the Issues List, and the weekly meeting's to-dos. Each function's Space holds its own day-to-day work, with Rock milestones linked to the tasks that deliver them.

Assign every Rock and to-do to one person, use due dates for milestones, and keep custom fields to the few that someone actually filters on. The test for any part of the structure is whether the person accountable for a seat can find their own work in one or two clicks.

Setting up the weekly meeting view

Build one view the leadership team opens during the weekly meeting: the scorecard numbers at the top, then Rocks with their status, then to-dos from last week grouped by owner, then the Issues List sorted by priority. The facilitator works down the view in order. When to-dos and issues are captured directly into ClickUp during the meeting, nobody has to re-type notes afterwards, and the next meeting starts from an accurate list.

A 30-day rollout plan

• Week one: build the leadership Space with Rocks, Issues and to-dos only, and run the weekly meeting from it
• Week two: add the scorecard view and assign an owner to every number
• Week three: link each Rock to its milestones and the tasks in the functional Spaces
• Week four: review what is being used and remove anything that is not, before adding anything new

Related reading