How to Set Up Asana's Goals Feature So It Actually Connects to Daily Work

Asana's Goals feature can automatically calculate progress from the projects and tasks linked to it - see our full Asana profile for pricing and plan tiers, and our Asana vs ClickUp comparison if you're still deciding between platforms. Goals sit behind Asana's Advanced tier and above, and the setup itself is quick. What determines whether the resulting progress bar means anything is the decisions made before and during linking, which this guide walks through alongside the setup steps.

Step 1: Write the Goal as Something Specific Enough to Disprove

Before creating anything in Asana, write the goal in concrete enough terms that it's possible to say definitively whether it's being met - a specific number, a specific outcome, a specific deadline - rather than a vague directional statement. "Improve customer onboarding" isn't specific enough to judge; "reduce time-to-first-value from signup to seven days" is. A vague goal can't be meaningfully linked to specific work, because nothing is specific enough to check the link against, which is the root cause of a lot of loosely connected goals downstream.

Step 2: List the Work That Actually Drives the Goal Before Opening Asana

With the goal defined, identify which existing or planned projects, and which specific tasks within them, genuinely move that goal forward - not which ones are thematically related or happen to be running in the same department. This is deliberately a planning exercise done outside the tool, because the goal of this step is separating what actually drives the outcome from what merely sits nearby, and that judgment call is easy to skip once you're inside the interface clicking through a linking flow.

Step 3: Create the Goal and Set a Measurable Target

In Asana, create the goal and set its measurement type - a number, a percentage, or a simple binary status - matching the specific, disprovable language from Step 1. Assign a goal owner who's actually accountable for the outcome, not just whoever happened to create the entry in the system, since ownership tends to determine whether anyone follows up when the goal stalls.

Step 4: Link Only the Projects That Passed Your Step 2 Filter

Link the goal to its supporting projects, but limit this to the projects and tasks actually identified in Step 2 as genuine drivers, not every project that seems adjacent to the topic. If a project only partially serves the goal - most of its tasks matter, but a handful don't - consider whether Asana's task-level progress linking can scope the connection down to just the relevant tasks, rather than linking the entire project and accepting that the progress bar will include unrelated work. This step tends to feel slower than simply linking an entire project wholesale, since it requires going through a project's task list and making an individual judgment call on each one, but that extra time is exactly what separates a progress number that means something from one that's technically functioning but not actually trustworthy.

Step 5: Choose the Progress Source Deliberately

Asana lets you set whether a goal's progress comes from project completion percentage or specific task completion. Choose based on what you actually verified in Step 2 - if only certain tasks within a project drive the goal, task-level tracking will produce a more accurate signal than project-level tracking, even though it takes slightly more setup to configure which specific tasks count.

Step 6: Sanity-Check the Progress Bar Immediately After Linking

Once linked, look at the goal's current progress number and ask whether it actually matches your own sense of how close the organization is to the real-world outcome. If the goal shows significant progress despite the underlying initiative clearly being in an early, uncertain stage, that's a signal the linked projects or tasks include completed work that isn't genuinely connected to the goal, and it's worth revisiting the link before treating the number as trustworthy. This gut check takes a couple of minutes and is cheap insurance against presenting a misleading number in a review before anyone's had a chance to question it.

Step 7: Set a Recurring Check on Whether the Link Still Makes Sense

Projects evolve after a goal is first linked to them - new tasks get added that may not serve the original objective, scope shifts, priorities change. Put a recurring review on the calendar, tied to whoever owns the goal, specifically to ask whether the linked work still reflects what the goal is actually measuring. A link that was accurate at setup can drift out of alignment within a single quarter if nobody revisits it, and the progress bar will keep updating confidently the entire time without flagging that drift on its own. Thirty minutes on a recurring calendar invite is a small cost against the alternative of discovering, months later, that a goal everyone assumed was tracking real progress had actually been coasting on unrelated task completions the whole time.

Step 8: Use Portfolios to Catch Misalignment Across Multiple Goals at Once

If your team is tracking several goals simultaneously, set up an Asana Portfolio to view them side by side alongside their linked projects. Reviewing goals individually makes it easy to miss a pattern that only becomes obvious at a glance across several at once - the same project linked to three different goals, for instance, which either means that project is genuinely a major driver across multiple objectives, or more likely, that it was linked loosely to whichever goal seemed plausible rather than checked carefully against each one. A portfolio view surfaces this kind of overlap faster than scrolling through goals one at a time.

Step 9: Train Whoever Creates Future Goals on the Linking Discipline, Not Just the Clicks

As more teams start using Goals, the setup steps themselves - creating a goal, linking a project, choosing a progress source - are easy to document and easy to learn. The harder discipline, actually separating genuinely goal-driving work from loosely related work before linking anything, doesn't get picked up automatically just because someone learned which buttons to click. Make the Step 2 filtering exercise part of how goal creation is taught across the organization, not an implicit expectation that new goal owners are supposed to infer on their own, since without that explicit framing, new goals tend to regress toward whatever linking shortcut feels fastest.

Step 10: Report the Honest Number, Even When It's Stalled

When a goal review shows little or no real progress, resist the urge to link additional, loosely related work just to make the dashboard look healthier before a leadership check-in. A stalled goal that accurately reflects a stalled initiative is more useful information than one padded with tangential activity to avoid an uncomfortable conversation, since the stalled, honest number is what actually prompts the organization to address whatever is blocking real progress.

A Note on Rolling This Out Gradually

None of this needs to happen across every team and every objective simultaneously. Starting with one or two well-scoped goals, done carefully through the full process above, teaches far more about how reliable the resulting progress signal actually is than rolling Goals out org-wide on day one. Once that first goal has run through at least one full review cycle and proven the link between its progress number and real-world outcomes holds up, expanding to additional teams and objectives becomes a much better-informed decision - built on evidence that the discipline actually works, rather than an assumption that the feature alone will produce it everywhere it's turned on.

If you're still deciding whether Asana's structure-and-goals-first approach fits your team better than a more visually driven alternative, our Asana vs ClickUp comparison and Asana tool profile cover where that choice tends to land.