Asana

What Asana is and the problem it organizes

Asana is a work management platform delivered as a service by Asana, Inc., a US company headquartered in San Francisco. It connects tasks, owners, projects and goals so different teams can coordinate deliverables. It is accessed through browsers and desktop and mobile applications. Its license is proprietary: integrations and an API do not make the product open source.

The difference between a personal list and a coordination platform becomes clear when several people depend on one result. A task may contain discussion, dates and files; a project defines shared work; a portfolio groups projects; a goal expresses the intended outcome. These are different concepts. “Prepare three sessions” describes execution; “participants understand the change” requires an additional check.

Asana supports campaigns, operations, launches, internal initiatives and service coordination. In occupational safety and health it can make project preparation and follow-up visible while linking preventive decisions to their sources and owners. Its usefulness depends on participants agreeing what completion means and keeping information current.

Reference documentation: Asana — Company and origins · Asana — Pricing · Asana — Multi-home tasks.

Founding, expansion and key milestones

Dustin Moskovitz and Justin Rosenstein founded Asana in 2008 after working at Facebook, where they had addressed coordination through an internal task tool. The name comes from the Sanskrit term associated with a yoga posture. Public availability began in November 2011, followed by a paid offering in 2012. Its REST API was announced on 19 April 2012 to read and add data programmatically.

The iPhone and iPad application was rebuilt using native technology in July 2014; Android followed in January 2015. International expansion included French and German in November 2017, alongside connections such as Gmail. These developments mark the transition from the original web application to coordination across devices and languages.

Funding included a $50 million Series C led by Sam Altman in 2016, a $75 million Series D in January 2018 and another $50 million that November. The company began trading through a direct listing on the NYSE on 30 September 2020 and added the LTSE on 26 August 2021. These are historical corporate milestones, not an estimate of current valuation.

Reference documentation: Asana — Company and origins · Asana — Series C, 2016 · Asana — Series D, 2018 · Asana — Series E, 2018 · Asana — SEC filing: listings · Asana — Native iOS release · Asana — Android release retrospective · Asana — French and German · Asana — Announcing the REST API · Forbes history, August 2020.

Tasks connected by responsibilities and dependencies

Asana organises work through tasks and projects. A task needs a defined result, accountable owner and completion criterion; the project supplies the context connecting tasks. Dependencies can indicate that one task blocks another or must wait for a preceding condition to be completed.

Dependencies represent sequence, but do not verify a deliverable’s technical validity. Marking a task complete can release subsequent work without sufficient review. Separate production, review and acceptance where different people hold those responsibilities. Confirm which dependency types and scheduling options are available in the subscribed plan. A useful dependency should describe a real requirement, rather than merely reproducing the order in which tasks were entered.

Reference documentation: Asana Help — How to use task dependencies.

Current leadership and the move towards human–AI teams

Dan Rogers became CEO on 21 July 2025. Since 25 September 2026 he has also chaired the board; Moskovitz remains a director. Descriptions still presenting the cofounder as CEO or board chair therefore need a historical date or an update.

Asana progressed from generative features in 2023 to announcing AI Studio in October 2024 and subsequently expanding collaborative AI Teammates. In May 2026 it confirmed the acquisition of StackAI to connect execution across systems. June brought its human-agent teams approach and Asana Dash. Each product has a distinct role and access conditions: an acquisition does not place all acquired capabilities in every Asana subscription.

The current range also distinguishes applications for services, client work and development. When assessing a demonstration, identify the application shown and its required license. Project-based work may be sufficient for straightforward preventive coordination; adding another application or agent is useful when it addresses an identified need.

Reference documentation: Asana — Dan Rogers biography · Asana — Dustin Moskovitz biography · Asana — CEO appointment 2025 · Asana — Board appointments 2026 · Asana — StackAI acquisition · Asana — Asana AI overview · Asana — Human-agent teams announcement, June 2026.

Work Graph: one shared task in several contexts

Work Graph is Asana’s model for relating units of work, people and context. A characteristic feature is multi-homing: one task can belong to several projects, with changes reflected in each. This does not mean creating manually synchronized copies. “Review site A materials” might appear in both the training project and the review team’s meeting agenda.

This advantage requires interpretation rules. A task appearing in two projects can be counted twice when lists are added together. Use its identity rather than its title for combined reporting. Adding it to another project can also widen its audience. Check where it appears and who can access it before including restricted information.

Subtasks break work down; milestones identify significant points. Separate “draft delivered” from “version accepted” when different people own those responsibilities. A milestone can summarize acceptance without replacing preceding checks. The structure works if someone outside the project can identify the next deliverable, who prepares it and what blocks it.

Reference documentation: Asana — Company and origins · Asana — Multi-home tasks · Asana Help — Task permissions.

Views, capacity and goals measure different things

List, board and calendar views provide different perspectives on work. Timeline and Gantt add scheduling; portfolios and goals connect broader levels. Workload management helps compare assignments with capacity. These features depend on the edition and on populated dates, effort and ownership.

A plan may show four parallel tasks even though they require the same specialist. Record expected effort and review actual commitments to reveal the conflict. A dependency expresses sequence, not availability. If review is delayed, decide whether to move a date, reduce scope or reassign work, retaining a visible record of the decision.

Reports should separate volume, timeliness and outcome. “Eight of ten deliverables accepted” describes execution; “six of eight accepted on time” adds timeliness; neither proves that people understood an instruction. Define the population, period and appropriate measure for the goal. An attractive chart does not correct a poorly defined denominator.

Reference documentation: Asana Help — How to use task dependencies · Asana — Pricing.

Rules, AI Studio, AI Teammates and Dash

Rules automate defined changes in a workflow. AI Studio inserts AI steps without coding, such as classifying a request before assignment. AI Teammates are configurable agents collaborating on tasks and shared context. Dash provides a conversational experience for querying and organizing work. Selection depends on whether the problem calls for a stable rule, interpretation of text or iterative collaboration.

Documentation distinguishes the AI Requests used by Teammates and certain Dash operations from AI Studio credits. Requests are pooled at organization level; credits depend on factors including information volume and model choice. “AI included” does not mean unlimited consumption. Check the balance and exhaustion behavior before making a capability an essential workflow step.

An editorial pilot could classify twenty fictional requests by audience and site, leaving ambiguous cases for review. Compare output with an agreed classification and count errors by type rather than merely counting generated responses. Do not ask the classifier to invent a site when that information is absent. For actions affecting external systems, check whose account performs them and where review is required.

Reference documentation: Asana — Chat with Dash · Asana — AI Teammates · Asana — AI access controls · Asana — AI Requests · Asana — AI Studio credits · Asana — Asana AI overview.

Integrations, APIs and data leaving a project

The REST API lets authorized applications read and modify Asana resources. Integrations connect work with email, documents, meetings and analytics; the 2021 partner expansion and Zoom application are milestones in that ecosystem. Before connecting tools, distinguish creating a task from a message, attaching a link and synchronizing two systems: these produce different outcomes.

Asana supports CSV task imports and CSV or JSON project exports. Search views and My Tasks can also be exported. Tabular output can support date analysis, but check what structure and context it retains before treating it as the project archive.

A reliable integration needs a stable identifier and a retry rule. Reprocessing the same request should find existing work or flag repetition rather than create an indistinguishable task. Test exports using a task containing subtasks, comments, fields and files, documenting differences. A successful technical request does not demonstrate that the complete project was transferred correctly.

Reference documentation: Asana — Announcing the REST API · Asana — Project export/import.

Editions and access: check the actual environment

The reviewed offering limits Personal to two users. Starter adds scheduling and structured features; Advanced adds portfolios, goals and further coordination capabilities; Enterprise expands administration and resource management. Enterprise+ provides specialized controls. Check contractual conditions rather than applying limits from older Premium or Business plans to the current range.

Asana states that it does not use customer data for model training and imposes equivalent restrictions on its AI providers. This does not mean content is never processed. Agent permissions, the triggering user’s permissions and connected tools determine what information is usable. Memories are also linked to task context; reviewing them is part of agent maintenance.

A permissions test should include a preparer, reviewer and read-only participant. Check behavior after access removal and after adding the task to another project. Linking to an authorized source can reduce copies of personal information, but the destination repository’s permissions must also be respected.

Reference documentation: Asana — Pricing · Asana — AI access controls · Asana — AI FAQ.

Adoption, studies and recognition: what they establish

Asana reported more than 35,000 paying customers in January 2018. That describes historical expansion; customers, licenses and active people are different measures. Its Anatomy of Work Index 2022 examined responses from over 10,000 knowledge workers. It informs perceptions of coordination but does not prove that installing Asana independently improves health or productivity.

PCMag has recognized the product in editorial selections; Inc. included the company in Best Workplaces and Fast Company in Brands That Matter 2022. These concern different dimensions: software, workplace and brand. A pilot using your own work and measurable criteria is more useful for selection than combining unrelated awards.

Measure time to locate the latest version, requests without owners, duplicate tasks and dependencies discovered late. Compare equivalent periods and scope. Fewer messages may indicate better coordination or simply less communication; accompany that measure with evidence of clarity and resolved outstanding work.

Reference documentation: Asana — Series D, 2018 · Asana — Anatomy of Work 2022 · PCMag task-management selection 2025 · Inc. company profile · Fast Company Brands That Matter 2022.

Coordinating preventive projects with several contributors

• Training preparation: connect audience definition, material adaptation, review and session organisation, avoiding scheduling before the required content is available.
• Implementing improvements: coordinate tasks across functions and expose decisions or resources blocking progress.
• Document review: assign preparation, checking and approval while linking to the source holding the authorised version.

Sabentis proposes these as coordination examples. Distinguish management milestones from preventive outcomes: completing implementation tasks does not by itself demonstrate that a measure works at the workplace. The project should make clear which further observation or review will evaluate that outcome.

Worked example: sessions dependent on reviewed materials

Hypothetical example. An organisation is preparing sessions on an updated internal procedure, involving a content owner, a reviewer and coordinators at several sites.

1. Define the final deliverable: identifiable material, documented review and sessions organised for the intended audience. Separate this from later assessment of learning.
2. Create tasks for drafting content, checking it against the approved procedure, resolving comments and organising sessions. Assign specific owners and realistic dates.
3. Make final session organisation dependent on material acceptance. Document the evidence required to consider the review complete.
4. Test a reviewer delay and check which tasks become blocked. Agree who decides a revised date and how it is communicated, without accepting a draft automatically because of calendar pressure.
5. Before closing the project, check materials, recipients and delivery evidence. Record cancelled, postponed and completed work separately.

Accept the result when each task has an explainable state and dependencies reflect the actual process. The schedule should expose uncertainty and blockers, rather than hide them through artificial completion. Retain the reason for changed dates so the team can learn from recurring bottlenecks.

Assume four sites with three planned sessions each: twelve sessions. If nine occur, two are postponed and one is cancelled, execution against the original plan is 9/12, or 75%. If cancellation formally changes scope to eleven, retain both figures and explain the change rather than deleting it to improve the percentage. One shared review task added to four projects remains one review and must not be counted four times.

Reference documentation: Asana Help — How to use task dependencies.

Task access and a misleading sense of progress

Asana documentation explains that access can depend on projects, collaborators and assignment. Adding a task to a project or adding collaborators can change who sees it. Before including personal information or restricted documents, review access in the full context rather than only the settings of an isolated task.

An overdue date does not explain a delay, and a completed task does not establish result quality. Avoid using the percentage of closed tasks as an automatic safety measure. Tasks need comparable scope if aggregated into a progress figure; otherwise, closing many small actions can hide a major unresolved dependency. Keep material blockers visible even where most administrative work is already finished.

Reference documentation: Asana Help — Task permissions.

When to choose Asana

Asana may fit several contributors, deliverables and dependencies requiring explicit coordination. Before deployment, agree who maintains the project, how scope changes are handled and what happens when an owner is unavailable. A detailed plan without maintenance quickly loses usefulness.

For a simpler visual workflow, compare Trello. Where documenting context and decisions is central, Notion can complement tasks. Keep evidence at a stable reference and link to it from the project instead of attaching several unidentified versions.

Frequently asked questions about Asana in OSH

Does a dependency prevent unsafe work from starting?

It represents a planning relationship. Do not treat it as a physical safeguard or technical authorisation to perform real work.

How can completion be distinguished from acceptance?

Define separate steps and owners where necessary, and record the evidence supporting acceptance.

Can project progress be a preventive indicator?

It can describe plan execution where rules are clear. Assessing preventive effects requires additional measures related to the objective and context.

Reference documentation: Asana Help — How to use task dependencies.