Asana
Also known as: Asana project, work management
Asana is a project and work management tool that lets teams create projects, assign tasks, set deadlines, track dependencies, and report on progress.
It supports list, board, timeline (Gantt-style), and calendar views. Asana is positioned between simple tools like Trello and complex engineering tools like Jira: it's designed for cross-functional business teams managing ongoing work.
Asana, explained at three levels
At home
Asana is a task management app where you can create a to-do list, organize tasks into projects, assign them to people, and set due dates. It's more structured than a simple checklist app: tasks belong to projects, projects belong to teams, and you can see everything on a list, board, or calendar view.
At work
Teams use Asana to manage projects collaboratively. A project manager creates a project, adds tasks, assigns each task to the right person with a due date, and tracks progress. When you're assigned a task in Asana, you get a notification, and you can mark it complete when done. The project manager can see overall progress without sending status emails.
At home
Asana's Timeline view shows tasks as a Gantt-style chart: horizontal bars across a calendar. You can set dependencies so that task B can't start until task A is done. If task A slips, Asana shows which dependent tasks are now at risk. For personal project planning, this visual schedule is much clearer than a simple list.
At work
Asana's portfolios let a manager see the status of all active projects on one screen (on track, at risk, or off track) without drilling into each project. Workload view shows task count by person so you can rebalance if someone is overloaded. Asana integrates with Slack, Jira, Salesforce, and hundreds of other tools, and rules automate repetitive task creation and assignment.
At home
Advanced Asana users use multi-homing: assigning a single task to multiple projects without duplicating it. This means a task appears in both a team project and a personal My Tasks view, staying in sync. Custom fields add structured metadata to tasks (client name, budget, priority), and forms let external stakeholders submit requests that automatically create Asana tasks.
At work
Asana's REST API and webhooks allow deep integration with enterprise systems, for example, a Salesforce opportunity moving to Closed Won automatically triggers Asana to create a new client onboarding project from a template. Asana's AI features (first branded Asana Intelligence) can generate project plans, flag tasks at risk based on historical data, and summarize project status in natural language. Admin controls include custom roles, division-level reporting, and data export for compliance.
Real-world examples
At home
Carlos was renovating his home and used Asana to manage the project. He created tasks for each contractor, set due dates, added dependencies (electrical must be done before drywall), and used the Timeline to see the full schedule. When the electrician ran late, Asana showed him which dependent tasks would shift.
At work
Lena managed a cross-functional product launch across Marketing, Engineering, and Sales. She built a shared Asana project with tasks assigned to each team, milestone markers for key dates, and a portfolio view that let her executive team see overall launch readiness in a single dashboard each week.
Common confusions
- Some people think subtasks in Asana are as visible as regular tasks — Subtasks in Asana do not appear in the parent project's task list by default: they only show when you open the parent task. This means a project view can look mostly complete when significant work is still in hidden subtasks. To make subtasks visible in project views, you must manually add them to the project, which many teams forget to do.
- Many assume Asana's Timeline view works exactly like a Gantt chart — Asana Timeline looks like a Gantt chart but has key differences: it doesn't calculate resource capacity, and on most plans it doesn't automatically adjust downstream dependencies when you drag a task. For complex multi-resource project scheduling, dedicated tools like MS Project or Smartsheet are more capable.
- Teams often assume marking a task complete makes it accurate — Asana completion is purely manual: it reflects what someone clicked, not what's actually done. A task marked complete without review appears green in portfolio views and hides real project risk. Completion accuracy depends entirely on the team's discipline in updating tasks promptly and honestly.
For analysts
Asana implementations often fail not because the tool is wrong but because task ownership and update discipline aren't established. Without a clear norm that all work is tracked in Asana and status is updated in real time, managers revert to status-update meetings to find out where things stand. Change management is as important as configuration.
History & origin
Asana was founded in 2008 by Dustin Moskovitz (Facebook co-founder) and Justin Rosenstein, who had built an internal task management tool at Facebook. Asana launched publicly in 2011 with the mission to help teams coordinate work without email. It went public on the NYSE in September 2020 via a direct listing. Asana has continued to expand into portfolio management, AI-powered workload analysis, and goals tracking aligned to OKRs. It competes directly with Monday.com and Jira for cross-functional team project management.