A Goal that reflects revenue, not just task completion
A sales-linked Goal's progress updates off actual closed revenue synced from your CRM or accounting system, not just whether the related tasks got checked off.
Asana's reporting layer has three real pieces: project-level dashboards for basic charts, Portfolios for rolling several projects' status into one view, and Goals for tracking company or team objectives, with progress that can auto-update as linked tasks and projects complete. All three only ever know what's already an Asana field. A number that lives in your finance or support system has to get there first.
Project dashboards show basic charts, task completion, workload by assignee, status over time, built directly from that project's own data. Advanced cross-project reporting, building a chart off several projects' combined data at once, is a paid-tier feature rather than something every plan includes.
Portfolios group several related projects into one rolled-up status view, useful for a program manager tracking five client projects at once without opening each individually. Each project in a portfolio carries its own status indicator, which rolls up to a single at-a-glance health check.
Goals (Asana's OKR feature) is the one genuinely clever piece: link a goal to specific projects or tasks, and its progress percentage updates automatically as the linked work actually completes, rather than someone manually updating a progress bar every week.
A dashboard, a Portfolio status, and a Goal's progress bar all draw from the same pool: whatever's already a field on an Asana task or project. True revenue, support ticket backlog, fulfillment rate, anything that only lives in a different system, simply isn't visible to any of them until it's synced onto an Asana object first. The rollup looks complete. It's just missing the half of the picture Asana was never shown.
A sales-linked Goal's progress updates off actual closed revenue synced from your CRM or accounting system, not just whether the related tasks got checked off.
A project's health indicator flips to at-risk the moment an external signal, a vendor delay, a budget overrun tracked elsewhere, crosses a threshold, instead of staying green until a person notices.
If it lives outside Asana, that's a sync worth building, not a limitation to live with.
Tell us which figure, revenue, backlog, a fulfillment number, never makes it into Asana. We'll scope what it would take to get it onto a Goal or dashboard your team already checks. Reporting is one example; n-frames builds this same connection wherever a number is stuck in a system your rollup can't reach.
Let's talk →A way to group several related projects and see their rolled-up status in one place, each project carrying its own health indicator (on track, at risk, off track) that a program manager can scan without opening every project individually.
You create a Goal and link it to specific projects or tasks. As that linked work completes, the Goal's progress percentage updates automatically, rather than someone manually moving a progress bar on a schedule.
Yes, cross-project reporting exists on paid tiers, letting you build a chart off combined data from several projects at once rather than one project's data alone.
Reports and underlying task data can be exported, usually as CSV, for use elsewhere. There's no single native export that captures a dashboard exactly as it's visually arranged.
Yes, Goals is built around the objectives-and-key-results format directly, letting you set a measurable target and track progress toward it as linked work completes.