Loading tutorials…
Loading tutorials…
Asana Dashboards turn task data into decisions. Done right, the marketing leader has a one-screen view of everything. Done wrong, you have pretty charts nobody acts on.
Who this is forMarketing leaders, agency directors, founders who need data-driven visibility. Teams running custom fields disciplined enough to make Dashboards useful.
What you'll need
Step 1
Dashboards exist to answer specific questions. List the 5-7 questions you want answered weekly.
Common marketing questions: "What is in progress this week?" "Which campaigns are blocked?" "Where is content velocity slowest?" "Channel mix this quarter?" "Team workload balance?"
For each question, identify which custom field(s) it depends on.
If a question depends on data you do not track, either add the field or accept that the question is out of scope.
Prioritize questions that drive weekly leadership decisions.
Step 2
One Dashboard for marketing leadership. 6-9 widgets. Single screen. Updated daily.
Dashboard → New Dashboard. Name "Marketing Executive Overview."
Widget 1: tasks by Status across all marketing projects (bar chart).
Widget 2: high-priority tasks list (filtered for Priority = High or Urgent).
Widget 3: tasks by Channel (pie chart) — shows current channel mix.
Widget 4: tasks completed this week vs. last week (line chart).
Widget 5: blocked tasks list (filtered for Status = Blocked).
Widget 6: tasks due this week.
Save and share with leadership team.
Step 3
For content teams: a Dashboard tracking output volume and pipeline.
Widget 1: blog posts published this month (count, filtered by Content Type = Blog AND Stage = Launched).
Widget 2: content in production by Stage (bar chart).
Widget 3: content by Author (workload distribution).
Widget 4: average time from Idea to Published (calculated from task created and completed dates).
Widget 5: blocked content list.
Share with content team for weekly review.
Step 4
For people leaders: who is over-allocated, who is under-allocated, where the bottlenecks are.
Widget 1: tasks per assignee (bar chart, descending).
Widget 2: overdue tasks per assignee.
Widget 3: tasks completed per assignee this week.
Widget 4: incoming tasks (created this week) by assignee.
Workload Dashboard is delicate — use for capacity planning, not performance reviews.
Step 5
One row per active campaign. Status, owner, due date, percent complete. Updated automatically.
Widget 1: campaign list with Status, Owner, Due Date, % complete columns.
Widget 2: campaigns by Channel.
Widget 3: campaigns at risk (filtered for Status = Blocked or due date passed).
Widget 4: campaigns launching this quarter (filtered for Stage = Launched + date range).
Most useful for marketing leadership weekly review.
Step 6
Dashboards rot. Monthly review keeps them tight and decision-driving.
Monthly: open each Dashboard. Are widgets still answering the question they were built for?
Talk to users: which widgets do you act on? Which do you scroll past?
Retire widgets nobody acts on. Add widgets for emerging questions.
Quarterly: full Dashboard audit. Retire dead Dashboards.
Discipline here is what separates a working reporting system from decorative charts.
Common mistakes
Too many widgets per Dashboard
What goes wrong: Dashboard has 18 widgets across 3 screens. Nobody scrolls past widget 6. Most charts are unread.
How to avoid: 6-9 widgets max. Single screen. If you have more questions, build a second Dashboard.
Vanity metrics
What goes wrong: Dashboard shows 'tasks completed' as a big number. Number goes up regardless of what was completed. Drives activity, not impact.
How to avoid: Every widget must answer a decision-driving question. "Tasks completed" by itself is vanity; "Tasks completed by Stage" is decision-driving.
Dashboard built on inconsistent custom field data
What goes wrong: Pie chart of Channel shows 30% "Other" because half the team did not fill Channel. Chart is meaningless.
How to avoid: Custom field discipline is a prerequisite to Dashboards. Audit field usage before building.
No Dashboard cadence
What goes wrong: Built once at setup. Never opened again. Decision-makers fall back to ad-hoc reports or spreadsheets.
How to avoid: Bake Dashboards into weekly reviews. Marketing leader opens executive overview every Monday. Cadence makes the system stick.
Dashboards as performance management
What goes wrong: Workload Dashboard used to compare assignees and rank performance. Team gamifies tasks (lots of small completions). Big-bet work disappears.
How to avoid: Workload Dashboards are for capacity planning, not ranking. Frame the use case to the team explicitly.
Recap
Done — what's next
How to set up Asana custom fields for campaign tracking
Read the next tutorial
Hand it off
Reporting design is leadership-level work. EverestX growth-marketing strategists design Dashboards + train leadership in 2-3 weeks, then own ongoing for $400-1,200/mo on most engagements.
See specialist rates
Direct export is limited. For executive-deck use cases, most teams take a screenshot or use the public share link. For deeper analytics, export task data via CSV and rebuild in Looker Studio or Tableau.
Executive overview: yes, share with cross-functional leadership. Workload: marketing-internal only (sensitivity). Campaign health: shareable with Sales and Product if relevant.
Asana Dashboards are real-time over Asana data. Looker/Tableau is multi-source and more flexible but requires a data pipeline. Use Asana Dashboards for operational reporting; use Looker/Tableau for cross-source strategic reporting.
Asana sends per-user Daily Digest and Inbox notifications, but Dashboard-level email digests are not native. Use Zapier or Asana API to push weekly summaries to Slack or email.
Asana
Custom fields are the spine of Asana reporting. Done right, you get instant campaign health, channel mix, and content velocity. Done wrong, your data is noise.
Asana
Portfolios + Goals are how Asana stops being a task tool and starts being a strategic visibility tool. The setup is what most marketing teams skip — and what specialists prioritize.
Asana
Rules in Asana are not optional past month two. The right 10 Rules save 5-10 hours/week. The wrong Rules create chaos. This is what specialists implement.
Asana
DIY Asana works for a stretch. Then complexity, reporting needs, and adoption hit a ceiling. This is the framework for when a specialist earns their fee.