ClickUp Goals and OKRs for Gulf Teams: Two Ways to Track Objectives, and How to Choose

Quick answer

ClickUp tracks objectives two ways. Goals is a native feature: a Goal holds measurable Targets (Number, True/False, Currency, or Task) and its progress updates as Targets move. The second, which ClickUp documents for OKRs, runs each objective as a task with key results as subtasks, plus statuses, Dashboards, and Brain. Most Gulf teams use both.

Every organisation in the Gulf has a strategy document. Very few have a strategy scoreboard that is still alive in week nine of the quarter. Between the two sits the same gap in Dubai, Doha, and Kuwait City: objectives are written once, in a slide deck or a board paper, and then the year happens somewhere else, in tasks, WhatsApp threads, and month-end spreadsheets that nobody reconciles against the original intent.

We have written three guides on how the national planning frameworks of Qatar, Kuwait, and the UAE cascade into company-level targets. Each ended at the same ClickUp layer, Goals and Targets, without going deep. This guide does. It uses ClickUp's own help documentation as the source, explains the two routes the product offers for tracking objectives and key results, and gives a decision rule and a setup plan tuned to the Gulf calendar. Feature details reflect the help centre at the time of writing; treat it as the final authority when behaviour changes.

OKRs, KPIs, and Goals: three words that get mixed up

Before the tooling, a short vocabulary check, because most OKR rollouts fail on definitions rather than software. An objective is a qualitative statement of what you want to be true by a date. A key result is a number that proves you got there, with a baseline and a target. A KPI is a health metric you watch continuously, whether or not it belongs to a current objective. In ClickUp's vocabulary, a Goal is a container of measurable Targets, which maps neatly onto an objective with key results, though the feature also serves Sprints and weekly scorecards.

Keep the distinction explicit. Objectives change each quarter or year; KPIs persist. Put both into one List with the same statuses and the quarterly review will spend its first twenty minutes arguing about which rows are supposed to move.

Two routes, one product

ClickUp offers two structurally different ways to track objectives, and understanding that they are different is the whole game. Route one is the Goals feature: a dedicated area in the Global Navigation where a Goal is broken into Targets, each with its own measurement type, and progress rolls up automatically. It is a scoreboard. Route two is the approach ClickUp's own help series on goals and OKRs recommends: run objectives as tasks inside a dedicated Space, with key results as subtasks and custom task types, statuses, views, Dashboards, Docs, and Brain layered on top. It is a workflow. The first tells you where the number is; the second tells you what is being done about it and by whom. Most organisations we work with in the Gulf use both, but they need to decide deliberately which one is the source of truth for each kind of question.

Route one: Goals and Targets

Goals lives in the Global Navigation; if it is hidden, it sits under More and can be pinned. A Goal is a high-level objective made up of smaller, measurable Targets, and completing all Targets completes the Goal. Guests can use Goals too, which matters when an external consultant, a holding-company reviewer, or a government liaison needs to see progress without joining the team.

There are four Target types, and choosing the right one for each key result is most of the design work:

• Number: a range from a starting value to a target value, tracking increases or decreases. Use it for share-of-revenue, headcount, NPS, on-time delivery rate, and any percentage.
• Currency: a monetary Target that tracks increases or decreases. Use it for revenue, cost-out, collections, and pipeline, with the currency label your finance team reports in.
• True/False: a Done or Not Done checkbox. Use it for binary milestones such as an ISO certificate obtained, a free-zone licence renewed, or a policy approved.
• Task: tracks the completion of a single task, a subtask, or an entire List. Use it when the key result is 'ship the thing' and the thing already lives in ClickUp; when a task is attached to a Target, the task shows a badge with the Goal's name, so the person doing the work can see the number it serves.

Progress is updated by clicking a Target and entering the new value; the Goal's percentage recalculates on its own. Goals are public to the whole Workspace by default and can be made private, then shared with named people or Teams with their own permissions, and Goals cards place any Goal's progress on a Dashboard next to workload and status data. One practical limit to plan around: Goals is not available in the mobile app at the time of writing, so updating a Target is a laptop task, which shapes who owns the update ritual (our mobile app guide covers the full split).

What Goals does not do is hold the conversation. There is no status like 'Off track, needs a decision', no owner review step, no place where the initiative behind the number is discussed. That is what the second route is for.

Route two: objectives as tasks

ClickUp's help centre publishes a full pattern for running OKRs inside the Hierarchy, and a Company OKRs and Goals template that builds it in one step. The shape is worth understanding even if you use the template, because you will adapt it:

• One Space for all goals and OKRs, so accountability lives in one place rather than scattered across departmental Spaces.
• Folders by company-wide, departmental, quarterly, or region-based objectives; Lists follow the Folder logic, for example one List per country in a region-based Folder, which is exactly how a UAE, Qatar, and Kuwait operation would slice it.
• One task per objective, key results as subtasks, and custom task types so an Objective and a Key Result are visibly different kinds of item in every view.
• Relationships linking a team's OKR tasks to the department or company objective they serve, so updates roll up regardless of where the task sits in the Hierarchy; plus an owner, a due date, and Custom Fields for baseline, target value, data source, and country.
• Recommended statuses: To Do, Needs attention, Off track, On track, Department review, Owner review, Completed. Region-based Lists get a simpler set: Not started, In review, On hold, Awaiting approval, Done, Complete.
• Purpose-built views: department goals grouped by department, region projects grouped by region, a filtered view of your own team's goals, a single view of all key targets, and a Gantt view of the whole Space for dependencies, Milestones, and dates.
• Dashboards for the review meeting: a Text card for the weekly narrative and blockers, Calculation cards counting objectives and key results in progress, a Portfolio card for progress across OKR Folders or Lists, Pie or Bar charts by assignee or department, a Task List card for detail, and card data export for stakeholders outside the Workspace.
• A Doc view in the OKR Space for the weekly update and meeting agenda, with notes turned into tasks in place, and AI Notetaker capturing the meeting itself.
• Brain on top: ask questions of the OKR List from its Brain icon or from anywhere in the Workspace, and AI Fields (Summary, Progress Updates, Action Items) that can be automated so the objective describes its own state.

The strength of this route is that the objective is a task, so everything ClickUp does to tasks applies: comments, Automations, time in status, Custom Field roll-ups, Forms that file a proposed initiative straight into the right List. The weakness is the mirror image: a key result as a subtask has a status, not a value curve. 'On track' is a judgement; '62 of 80' is a measurement. If your board wants the measurement, you still need Route one.

How to choose: a decision rule that holds

Ask one question of each key result: is the hard part measuring it, or doing it? If the hard part is measuring, use a Goal Target. Revenue by segment, customer retention, average days-to-approve: these need a number that moves and a history of how it moved, and a Target gives you that with almost no ceremony. If the hard part is doing it, use a task with subtasks: launching a service in Doha, migrating a department off spreadsheets, passing an audit. These need owners, discussion, dependencies, and a review cadence, and a Target would reduce all of that to a checkbox.

Then connect the two. The Task Target type is the bridge: a Goal's Target can point at the objective task or the whole List of initiatives, so the scoreboard turns green only when the work is done. This gives a Gulf organisation a clean split: Goals is the executive scoreboard, three to seven Goals for the year, updated on a fixed day by a named person; the OKR Space is the operating layer where department heads run their quarter; and the Dashboard sits between them with Goals cards on the top row and Route two cards beneath.

The Gulf calendar: two working weeks, a moving month, and two clocks

Quarter design in the Gulf has three quirks that OKR templates written elsewhere ignore. First, the working week differs across the three countries BuyClickUp serves: the UAE moved to a Monday-to-Friday week in 2022, while Qatar and Kuwait work Sunday to Thursday. A regional review 'every Thursday afternoon' is the end of the week in Doha and Kuwait City and a normal working day in Dubai. Set the review cadence per country List, and put the group-level review on a day that is a working day everywhere, Monday to Thursday.

Second, Ramadan moves about eleven days earlier each year and for the next several years falls in the first quarter, bringing shortened working hours across the region and a quieter decision calendar. Build it into the plan rather than discovering it in the numbers: a Q1 key result with the same weekly target as Q3 is a design error, not an execution failure. Third, the UAE runs on UTC+4 and Qatar and Kuwait on UTC+3, and fiscal years do not fully align either: UAE and Qatar entities generally plan on the calendar year, while Kuwait's state budget runs from April to March, which matters for any Kuwaiti government-linked customer in your plan. A Custom Field for the fiscal year an objective belongs to saves a quarterly argument.

Bilingual objectives without double entry

Objectives are read by two audiences in most Gulf organisations: the delivery team, often working in English, and the board, shareholders, or ministry, often reading in Arabic. Do not maintain two Workspaces or two Lists. Give each objective task a short bilingual name, keep the formal Arabic wording in a Custom Field or the task description, and let Dashboard card titles carry Arabic for the audience that reads them. Docs handle right-to-left Arabic well, so the objective charter (the indicator it serves, the baseline, the source of truth for the figure, the owner) can be one bilingual page linked from the task. Our guide on Arabic support in ClickUp covers the interface-language question; the point here is that the objective is written once and understood by both readers.

Five mistakes we see in Gulf OKR rollouts

The pattern is consistent enough across the three countries that it is worth listing.

• Too many objectives. Twelve company Goals is a to-do list, not a strategy. Three to seven, with key results a board member can recite.
• Key results without baselines. A Target from 0 to 100 percent says nothing about difficulty; a Target from 61 to 75 does. Record the starting value the day the quarter opens.
• One person updating everything. If the PMO enters every number, the numbers are the PMO's, not the owners'. Assign each Target and objective task to the person accountable for the outcome.
• Statuses used as opinions. Define 'On track' once, in writing, as a percentage of plan or a Target value, and pin the definition in the OKR Space Doc.
• No review ritual. The Dashboard exists so that a fixed meeting, on a day that is a working day in every country involved, can look at it. Without the meeting, it decays in about three weeks.

A 30-day setup plan

The order matters more than the speed. Thirty days is enough for a mid-sized organisation to start a quarter with a live scoreboard.

• Days 1 to 5: agree the vocabulary and the objectives. Three to seven company objectives, each with two to four key results carrying a baseline and a target. Decide, per key result, Target or task.
• Days 6 to 10: build the OKR Space from the ClickUp template or by hand: Folders by department and country, custom task types for Objective and Key Result, the recommended statuses adjusted to your review flow, Custom Fields for baseline, target, source, country, and fiscal year.
• Days 11 to 15: create the Goals. One Goal per company objective, Targets typed correctly, Task Targets pointing at the objective tasks or initiative Lists. Set sharing so guests and reviewers see what they should and nothing else.
• Days 16 to 20: build two Dashboards, an executive one with Goals cards on top and Portfolio and Calculation cards beneath, and a departmental one with Task List and Bar cards. Add the weekly Text card and agree who writes it.
• Days 21 to 25: wire the routine. An Automation that sets Needs attention when a key result has not changed in a set period, a recurring update task on the fixed review day per country, AI Fields for Summary and Progress Updates on objective tasks.
• Days 26 to 30: run one dry review with real data, in both languages if the audience needs it. Fix the definitions that caused argument, then open the quarter.

How this compares

In fairness, every serious platform in this category has an answer for objectives. Asana has a Goals feature with sub-goals and progress roll-up from projects and portfolios; monday.com handles objectives through boards and its portfolio and dashboard tooling; Atlassian tracks goals across its cloud products and offers Focus for strategy-level portfolio tracking; Notion relies on databases and relations to build OKR pages; and dedicated OKR platforms such as Perdoo, Quantive, and Profit.co go deeper on OKR methodology than any work management tool, at the cost of living beside the work rather than inside it.

ClickUp's distinctive position is that both routes live in the same Workspace as the work: a Target can point at the exact List of tasks that moves it, the review Dashboard can mix Goal progress with workload and time-in-status, and Brain can answer a question about an objective using the comments on the tasks beneath it. Whether that is decisive depends on how much of your operating work is already in ClickUp. If your team is still weighing platforms, our guide to the best project management tools for GCC teams covers the broader trade-offs.

How BuyClickUp fits

BuyClickUp is an independent ClickUp partner operated by Inspark, working with organisations in the UAE, Qatar, and Kuwait. Objective design is where we start most implementations, before Spaces and statuses, because the OKR structure decides what the Hierarchy has to hold. We run the vocabulary workshop in Arabic or English, build the OKR Space and the Goals layer with the people who will own them, and design the review Dashboards for each audience, including the board pack in Arabic where that is what the board reads.

ClickUp is a trademark of Mango Technologies, Inc.; BuyClickUp is an independent partner, and this article reflects our reading of ClickUp's published documentation and our own implementation experience. If your strategy lives in a deck and your work lives somewhere else, take our short readiness assessment or contact us, and we will help you decide which of the two routes each of your objectives belongs on.