Loading tutorials…
Loading tutorials…
Projects without templates burn 30 minutes of setup every time. Templates well-built save 20+ hours per month and force consistency. This is the library specialists build first.
Who this is forMarketing teams who have just set up Asana and want to scale work, not recreate it. Agencies producing repeatable client deliverables. Founders standardizing how their team runs campaigns.
What you'll need
Step 1
List every marketing workflow you do more than twice per quarter. These become templates.
Common marketing templates: Blog Post, Email Campaign, Paid Ad Campaign Launch, Webinar, Event, Product Launch, Quarterly Planning, Monthly Reporting.
Less obvious: New Hire Onboarding (for marketing), Vendor Evaluation, Brand Guideline Update.
Score each by frequency (monthly, quarterly, annually) and complexity (5 tasks, 15 tasks, 50+ tasks).
Prioritize building templates for high-frequency or high-complexity workflows. Skip low-frequency low-complexity (they don't need templating).
Step 2
Reverse-engineer a recently completed project into a template. Less abstract, more accurate.
Open a recently completed project. Copy it (Project menu → Duplicate).
Strip dates, assignees, and project-specific details. Leave task names, descriptions, and ordering.
Standardize task names. "Write blog draft" not "Write draft for Q3 launch post."
Save as Project Template (Asana → Templates → Save as template).
Test by creating one new project from the template with a real upcoming workflow.
Step 3
Too few tasks = template is useless. Too many tasks = template is noise. Sweet spot is 12-25 tasks per template.
Blog Post template: 12-15 tasks (research, outline, draft, edit, SEO check, design, schedule, publish, promote, measure).
Email Campaign template: 15-20 tasks.
Product Launch template: 30-50 tasks across multiple sections.
For each task, include: clear name, description (1-2 sentences of context), default assignee role (not person), default duration (3 days, 1 week).
Group tasks into Sections for navigation: Research → Production → Review → Launch → Measure.
Step 4
Templates should bake in the right Custom Fields. Done once at template level, every project inherits.
Standard marketing fields: Priority (low/med/high/urgent), Status (not started/in progress/blocked/done), Content Type (blog/email/ad/social), Channel (Google/Meta/LinkedIn).
Bake fields into the template at the project level. Every new project from the template has them.
Avoid template bloat — past 8 custom fields, the project becomes hard to scan.
Document each field in the project description so new users understand the semantic.
Step 5
Sequential tasks need dependencies. Major checkpoints need milestones. Both surface in Portfolios and Timeline view.
For each pair of sequential tasks, set the second as "Depends on" the first.
Asana then prevents starting Task 2 before Task 1 is done.
Mark major checkpoints as Milestones (right-click task → Mark as milestone).
Milestones surface in Portfolios as date markers. Use for things like "Campaign launches," "Content goes live," "Event date."
Step 6
Templates rot if not maintained. Quarterly review keeps them tight.
Calendar: quarterly review of every active template.
For each: how many projects used it last quarter? If less than 2, archive it.
Talk to 1-2 users who ran the template. What did they delete? What did they add? What confused them?
Update the template based on observations. Re-save.
Document changes in a "Template Changelog" page so teammates know what changed.
Common mistakes
Building templates from imagined workflows
What goes wrong: Template looks neat but does not match real work. Team deletes 40% of tasks every time they use it. Friction compounds and people stop using templates.
How to avoid: Reverse-engineer from real recent projects. Test on real upcoming projects before declaring done.
Templates with 50+ tasks
What goes wrong: Every new project starts with 50 tasks. Most get deleted because they do not apply. Net friction is higher than no template.
How to avoid: 12-25 tasks per template. Sections for navigation. Add tasks at the project level when needed, not template level.
No custom fields baked into templates
What goes wrong: Each project starts with no Priority, Status, or Channel fields. People add them inconsistently. Reporting becomes impossible.
How to avoid: Bake 4-6 standard custom fields into every template. Consistent fields = consistent reporting.
Templates with named assignees
What goes wrong: Template assigns tasks to Sarah and John. Sarah leaves. Every new project from template has tasks assigned to a former employee.
How to avoid: Templates assign by role, not person. Use "Content Manager," "Designer," etc. as assignees. Reassign at project creation.
Never reviewing templates
What goes wrong: Template built in month 1, still used in month 18 despite workflow having evolved. Tasks no longer reflect reality. Users delete-and-replace 60% of tasks.
How to avoid: Quarterly template review. 30 minutes. Major updates. Document changes.
Recap
Done — what's next
How to set up an Asana workspace for marketing the right way
Read the next tutorial
Hand it off
Template libraries are exactly the kind of high-leverage, low-glamour work specialists earn their fee on. EverestX growth-marketing strategists build template libraries in 1-2 weeks, then own ongoing ops for $400-1,200/mo.
See specialist rates
Most high-functioning marketing teams converge on 8-15 active templates. Past 15, the library is hard to navigate and templates start overlapping. If you have 30 templates, half are duplicates.
Asana has CSV import that preserves task structure. Templates do not import directly between tools, but you can export task list from Trello/ClickUp as CSV, import to Asana, then save as template.
Date-relative. Asana lets you set tasks as "3 days after project start" or "5 days before milestone." When you create a project from template, all dates auto-calculate from the project start.
Templates can be Team-scoped or Org-scoped. For company-wide processes (onboarding, vendor evaluation), make Org-scoped. For team-specific (content, paid media), make Team-scoped.
Asana
Asana for marketing is powerful but unforgiving on the first setup — the wrong org structure costs you months of cleanup. This is the setup specialists run.
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
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
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.