๐Ÿ“

Asana

Asana is a general-purpose work-management platform made by Asana Inc., organizing work into tasks, projects, timelines (Gantt-style views), and portfolios with built-in automation rules. It ranks #15 among dev collaboration tools, reported in roughly 4.4% of developer surveys, but it's widely used cross-functionally โ€” by marketing, design, ops, and product teams, not just engineers. Teams pick it when they need one tool that non-technical stakeholders and developers can both plan work in together.

Quick facts
Type: General work/project management (tasks, timelines, portfolios, automation)
Made by: Asana, Inc.
Cost: Freemium โ€” free tier for small teams (up to 15 members); paid Starter/Advanced/Enterprise tiers add timelines, portfolios, and admin controls
Best for: Cross-functional teams spanning engineering, marketing, design, and operations
Primary use case: Coordinating work across multiple departments with tasks, project timelines, and automated workflows
Jump to: ExampleGetting startedBest for

Example

The Asana API lets you create tasks programmatically โ€” handy for wiring up forms, bots, or other tools to automatically generate work items.

# create a task via the Asana API
curl --request POST \
  --url 'https://app.asana.com/api/1.0/tasks' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "data": {
      "name": "Write Q3 launch announcement",
      "notes": "Draft due before the marketing sync",
      "projects": ["1201234567890"],
      "due_on": "2026-08-01"
    }
  }'

Getting started

Sign up free at asana.com, create a project, choose List, Board, or Timeline view, and start adding tasks with assignees and due dates.

1. Go to asana.com and sign up with a work email
2. Click "Create project" and pick a template (or start blank)
3. Choose a view: List, Board (Kanban), or Timeline (Gantt)
4. Add tasks with assignees, due dates, and subtasks
5. Set up an automation Rule (e.g. "when task moves to Done, notify assignee")
Best for: Cross-functional organizations where engineering, marketing, design, and ops all need to plan and track work in one shared, non-technical-friendly tool rather than an engineering-only issue tracker.