How to Use Asana to Run Projects Without Chaos
Asana is a work management tool organised as projects, tasks and subtasks, with several views of the same data — list, board, timeline, calendar. It is flexible enough that teams routinely build three overlapping systems and then blame the tool.
Short answer: one project per body of work, list view as the default, timeline only for work with real dependencies, and sections instead of extra projects. Free plan supports up to 10 people; Starter is around $10.99/user/month billed annually.
What Is Asana Actually Good At?
Marketing and operations work with many small interlocking pieces: campaign launches, content calendars, event logistics, onboarding checklists. The timeline view with dependencies is genuinely nicer than a spreadsheet for anything with a launch date.
It is not a great issue tracker for engineering — tasks have no meaningful resolution states unless you build them — and it is not a real alternative to a database tool for inventory-style work.
How Should You Structure a First Project?
- Create one project per deliverable stream: Q4 Launch, not Marketing.
- Use sections as stages: Brief, In Production, Review, Live. Nothing more granular than that.
- Set the default view to List. Boards are for things with a continuous flow, not a launch.
- Add a follower to every task by default via project settings — silent tasks are how things get missed.
- Create custom fields only for things you will filter by: Owner, Channel, Launch date.
That is the entire structure. Most Asana mess comes from adding fields “just in case”.
Which View Should You Use When?
| View | Best for | Prone to |
|---|---|---|
| List | Daily task work | Nobody reads descriptions |
| Board | Ongoing pipelines | Rot without owners |
| Timeline | Dated launches, dependencies | Wrong dates propagated everywhere |
| Calendar | Scheduling, content | Misses undated tasks entirely |
Pick one as the canonical view and tell people that if a task is not there, it does not count as planned.
How Do You Stop Task Duplication?
Two habits solve most of it. First, search before creating — Asana’s search is fast and typed, and thumb-typing a new task without searching is the root cause of duplicates.
Second, use multi-homing sparingly. A task in multiple projects feels convenient and creates the illusion of activity: the same task shows up three times in three different statuses.
What Do the Plans Actually Cost?
Free: up to 10 people, unlimited projects and tasks, no timeline view, no automations. Starter: roughly $10.99/user/month annually, adds timeline, dependencies and 250 automations. Advanced roughly doubles it with portfolios and workload.
The free plan’s missing timeline is the real barrier — if your work has dependencies, you are paying. A 10-person team on Starter is about $1,300 a year.
What Are the Honest Complaints?
Notifications are noisy by default and require pruning per project. Subtask overload is common: teams create three levels where one would do, and then nothing rolls up.
Performance on very large projects (1,000+ tasks) is noticeably slower than the empty-project experience.
Who Should Use Something Else?
Engineering teams wanting sprint boards — Linear or Jira fit better. Solo freelancers — the pricing per seat is hard to justify when a simple task list would do. Teams needing databases with linked records — that is Airtable’s territory.
Key Takeaways
- One Asana project per deliverable stream, with sections as stages.
- Free plan caps at 10 people and excludes the timeline and dependency features.
- Starter costs about $10.99/user/month annually with 250 automations.
- Avoid multi-homing the same task across projects — it produces fake progress.
- Better fit for marketing ops than for engineering sprints.
