Almost every team we implement Asana for gets the task management part right within a few weeks. Tasks have owners, due dates, and comments. What almost none of them use properly — at least without help — is Goals and Portfolios. And that's usually the exact feature that decides whether leadership actually opens Asana, or keeps asking for a status update over email.
Individual contributors get value from Asana the moment tasks have clear owners. But executives don't manage tasks — they manage outcomes across departments, and they need to see progress without pinging five people for an update. That's what Goals and Portfolios are built for. Most teams either skip this layer entirely or set it up so loosely it doesn't reflect reality. Neither gets leadership to actually trust the dashboard.
This isn't a feature teams don't know exists. It's a feature that gets deprioritized during setup because it doesn't feel urgent on day one — and by the time leadership asks for visibility, retrofitting it is a much bigger job than building it from the start.
These two features get confused constantly, and the confusion is exactly why they end up misconfigured.
A measurable outcome tied to a time period — a quarterly revenue target, a launch date, a percentage improvement. Goals track progress toward a specific number or milestone, and can roll up from sub-goals owned by different teams.
A collection of projects grouped together for visibility — say, every active client account, or every project under one department. Portfolios show status, workload, and timing across many projects at once, without needing goals attached.
In practice, the two work best together: Portfolios give you the "what's happening across all these projects" view, and Goals give you the "are we actually on track" view. Used separately, each one only tells half the story leadership actually needs.
A reporting layer only works if leadership trusts what it's showing. These are the mistakes that quietly destroy that trust — usually within the first month.
The fix isn't complicated, but it does need to happen in the right order — usually the reverse of how most teams approach it.
Start from the business outcome, then connect projects to it — not the other way around. A goal without a clear owning project is just a wish.
Where task completion can drive goal progress automatically, use it. Manual progress updates are the single biggest reason dashboards go stale.
A handful of tracked goals per quarter, not twenty. Fewer numbers, but numbers leadership can actually trust and act on.
Someone needs to archive finished projects and flag stalled ones weekly, or the portfolio view slowly stops reflecting reality.
"Asana will get rid of your status meetings" is a common pitch, and it's true only partially. What actually happens with a properly built Goals and Portfolios layer is that status meetings shift purpose — from reporting what happened to discussing what to do about it. Leadership already knows the numbers before the meeting starts, because the dashboard told them. The meeting time gets spent on decisions instead of updates.
That shift is usually the biggest single ROI signal teams report after a proper implementation — not less software use, but noticeably less meeting time.
Goals and Portfolios are exactly the kind of setup that gets rushed or skipped when a team implements Asana on their own — and it's exactly where we spend deliberate time when we run an implementation.
We build the goal structure around what your leadership actually tracks, not a generic template.
We connect goal tracking to real task data using Asana's rules, so dashboards stay current without manual upkeep.
We assign responsibility for keeping the portfolio view accurate as part of the rollout, not as an afterthought.
Task management gets your team to use Asana. Goals and Portfolios get your leadership to trust it. Skipping this layer is the most common reason a rollout feels successful at the team level but still leaves executives asking for manual updates months later. Build it early, keep it simple, and give someone ownership of keeping it accurate.
If your team's rollout never got this far, book a free consultation with SassyOS and we'll show you what a proper reporting layer looks like for your business.
Core Asana Services
Rollout & Implementation
Automation & Collaboration
Comparisons & Partner Coverage
We'll build a Goals and Portfolios structure around the numbers your leadership actually cares about — not a generic template.
Book a Free Consultation Get in Touch