Asana does projects well but misses repeatable work

Asana is a cloud-based project management tool used by millions of teams to organize tasks, track deadlines, and coordinate work across departments. It does this genuinely well. But there’s a specific category of work - repeatable processes like employee onboarding, approval chains, and compliance procedures - where Asana’s project-centric design starts to buckle. That gap matters more than most reviews will tell you.

What Asana gets right

Asana is a project management tool. That sounds simple, but it’s worth being precise about what that means because the term gets stretched to cover everything from sticky notes to enterprise resource planning.

At its core, Asana lets you create projects, break them into tasks, assign those tasks to people, set deadlines, and track progress. You can view work as lists, boards (Kanban-style), timelines (Gantt-style), or calendars. Tasks can have subtasks, custom fields, attachments, and comments. Projects can be grouped into portfolios for executive-level visibility.

That foundation is solid. Here’s where Asana genuinely shines:

Cross-team visibility. If your marketing team, engineering team, and design team all work in Asana, you can see dependencies between their projects. The portfolio view gives leadership a single dashboard across all active work. One thing that keeps coming up with operations teams evaluating project tools, this cross-team visibility is consistently the feature that sells Asana over simpler alternatives like Trello or Todoist.

Flexible views. The same set of tasks renders as a list, board, timeline, or calendar depending on who’s looking. A project manager might prefer the timeline. A team member might prefer the board. Nobody has to change how they work.

Rules and automation. Asana’s rules engine handles things like auto-assigning tasks when a project reaches a certain stage, moving tasks between sections, or notifying someone when a due date changes. For project-level automation, this works fine. Feedback we’ve received from teams comparing tools suggests Asana’s rules cover about 80% of common project automation needs.

Integrations. Asana connects to Slack, Microsoft Teams, Google Workspace, Salesforce, Jira, Adobe Creative Cloud, and hundreds more. The API is well-documented and actively maintained.

Forms. You can create intake forms that feed directly into Asana projects. A design request form, a bug report form, a project brief - each submission becomes a task automatically.

Where repeatable work breaks down

Projects end. You plan them, execute them, close them. A product launch has a finish line. A marketing campaign wraps up. An office move gets completed.

But some work never ends. It repeats. Employee onboarding happens every time someone joins. Monthly close happens twelve times a year. Purchase approvals happen dozens of times per week.

This is where Asana struggles, and it’s not a minor thing.

When you try to run a repeatable process in Asana, here’s what happens. You create a project template. Each time you need to run the process, you duplicate the template. That creates a new project instance. So far, so good. But now you’ve got 30 copies of your onboarding project running at the same time. Each one is a separate project in your sidebar. Tracking which ones are stuck, which ones are overdue, and which ones finished on time requires clicking into each project individually.

There’s no unified view across all running instances of the same process. No dashboard that shows “17 onboardings are in progress, 3 are stuck at the IT setup step, and 2 are overdue.” You can build approximations with portfolios and custom fields, but it’s a workaround, not a designed experience.

People who use both Asana and Tallyfy tell us the distinction becomes obvious fast. Asana treats every instance of a repeated workflow as a standalone project. A dedicated process tool treats it as a running instance of a template, with cross-instance tracking built in. That difference sounds subtle on paper. In practice, it’s the difference between managing processes and drowning in duplicate projects.

A real example. A 200-person company onboards roughly 4 people per month. That’s 4 new Asana projects per month just for onboarding - each with 25-40 tasks spread across HR, IT, facilities, and the hiring manager. After a year, you’ve got 48 completed onboarding projects cluttering your workspace, and no easy way to answer: “What’s our average time from offer acceptance to fully onboarded?”

This isn’t an Asana bug. It’s a category limitation. Project management tools are built for unique work. Workflow automation tools are built for recurring work. They solve different problems.

AI features and what they don’t fix

Asana has been moving fast on AI. Here’s what’s new as of early 2026:

AI Teammates. These are context-aware collaborative agents that handle project tasks - triaging incoming requests, drafting status updates, answering questions about project context. They operate within Asana’s project framework and are designed to reduce the coordination overhead that project managers deal with daily. AI Studio surpassed $1 million in annualized recurring revenue in its first quarter, so there’s real adoption here.

AI Studio. This gives teams the ability to build custom AI workflows within Asana. You can create AI-powered rules that go beyond simple if-then logic. “Smart Projects” can spin up a project scaffold by generating a description, organizing sections, and creating relevant custom fields based on just a project name.

Claude integration via MCP. In January 2026, Asana partnered with Anthropic to integrate Claude directly into the platform using the Model Context Protocol. Teams can brainstorm in Claude, then turn that thinking into structured Asana projects without leaving the chat. When you click back into Asana, everything you’ve created through Claude is reflected in real time.

Here’s where I think the bigger picture gets missed, though.

AI capabilities keep leaping forward while the processes they depend on stay frozen in place. Asana’s AI features make project management smarter - that’s genuinely useful. But AI agents need more than project boards. They need structured workflow patterns - sequential steps, parallel execution paths, evaluation loops where the agent checks its own work before proceeding. That’s the infrastructure layer that most project tools, Asana included, weren’t designed to provide.

We’ve been thinking about this differently. The same workflow patterns that help humans run repeatable processes - step-by-step sequences with branching logic and accountability - are exactly what AI agents need to operate reliably. It’s not a coincidence. Process definition is the prerequisite for both human consistency and AI reliability.

Plan restructuring. Asana now offers Personal (free), Starter, Advanced, Enterprise, and Enterprise+. The free tier remains generous for small teams but caps at 10 members. For current pricing, check Asana’s pricing page directly - we deliberately avoid quoting specific numbers since they change.

Who should pick Asana

I’ll be honest about this. Asana is a genuinely good tool for the right use case. Running Tallyfy taught us evaluating workflow tools at Tallyfy, here’s how we think about it:

Asana is great if:

• Your work is primarily project-based - campaigns, launches, events, sprints
• You need cross-team visibility into multiple concurrent projects
• Your team is already in the Asana ecosystem and productive there
• You want strong integrations with Google Workspace, Slack, and Salesforce
• You’ve got a small team (under 10) and want a capable free plan

Asana is less ideal if:

• You run the same process repeatedly (onboarding, approvals, audits, compliance)
• You need to track dozens of running instances of the same workflow simultaneously
• You want process-level analytics - average completion time, bottleneck identification across all instances
• You need to assign steps to people outside your organization who don’t have Asana accounts
• Your primary pain is process consistency, not project coordination

The honest comparison. Asana is like an excellent kitchen for a restaurant that serves a different menu every night. It handles variety beautifully. But if you’re a pizza shop making the same ten pizzas 200 times a day, you need a production line, not a gourmet kitchen. Tallyfy is built for the production line - where the same standard operating procedures run repeatedly with tracking across every instance.

If you want to see how the two approaches compare side by side, the Asana alternative page breaks down the specific differences.

Repeatable process templates that work better than project boards

Example Procedure

Employee Onboarding

1HR - Set up payroll and send welcome email

2IT - Order equipment and set up workstation

3Office Manager - Prepare physical workspace

4IT - Create accounts and system access

5HR - Welcome meeting and company orientation

+3 more steps

View template

Example Procedure

Client Onboarding

1Gather Basic Information

2Send Welcome E-Mail

3Conduct a Kick-Off Call

4Conduct a 1 month check-in Call

5Request Feedback

+1 more steps

View template

Example Procedure

Team Status Report Workflow (Weekly/Monthly)

1Weekly B2B Sales report

2Review and sign-off weekly sales report

3Weekly Finance report

4Review and sign-off weekly finance report

5Monthly B2B Sales report

+8 more steps

View template

Process gap keeps growing

Here’s something I probably think about too much. The gap between project management and process management isn’t shrinking. It’s getting wider. And AI is accelerating it.

When you add AI to a project tool, you get smarter project management. The AI can draft updates, triage requests, and suggest timelines. That’s valuable for unique, one-off work.

But when you add AI to a process tool, something different happens. The AI can follow defined workflows. It can execute steps in sequence. It can evaluate its own output against criteria before moving forward. It can handle the boring, repeatable work that humans hate doing the same way every time.

If your onboarding process is a mess of emails and tribal knowledge, AI will just create that mess faster. But if your onboarding process is a structured workflow with clear steps, accountability, and branching logic - AI can run it consistently at scale.

That’s the fundamental bet we’re making at Tallyfy. Process definition isn’t just about human consistency anymore. It’s about building the infrastructure that AI agents need to be useful. Every structured workflow template becomes a set of instructions that both humans and AI can follow.

Asana isn’t wrong for ignoring this. They made a bet on project management and they’re executing on it well. But if your work is repeatable, the tool you need looks fundamentally different from a project board.

Related questions

Is Asana free to use?

Yes. Asana offers a Personal plan that’s completely free and includes task creation, assignees, due dates, comments, file attachments, and unlimited tasks and projects. The main restrictions on the free plan are a 10-member cap, no timeline view, no portfolios, no custom fields, and no workflow automation rules. For small teams or individuals managing basic projects, the free plan is genuinely functional - not a crippled trial. Paid plans add timeline views, advanced reporting, AI features, and automation rules. Check Asana’s pricing page for current tier details.

What is Asana best used for?

Asana is best for managing one-off projects that involve multiple people and have a clear start and end date. Marketing campaigns, product launches, event planning, website redesigns, office relocations - these are Asana’s sweet spot. It’s also strong for cross-departmental coordination where different teams need visibility into each other’s work. Where Asana is less suited is for recurring, templated work that runs hundreds of times - think employee onboarding, approval chains, or compliance procedures. For those, a dedicated workflow tool is a better fit.

How does Asana compare to Monday.com?

Both are project management tools with similar core features - task management, multiple views, automations, and integrations. Monday.com leans more visual and flexible with its color-coded board system, while Asana tends to feel more structured and project-oriented. Neither tool is purpose-built for repeatable processes - both treat recurring work as duplicated projects. The real question is whether your work is project-based (either tool works) or process-based (neither is ideal). Your choice between the two often comes down to interface preference and which integrations matter more to your team.

Can Asana handle complex workflows?

Asana can handle project workflows with its rules engine, task dependencies, and approval features. You can create multi-step processes with conditional logic using rules - for example, auto-assigning a task when a previous task completes, or moving tasks between sections based on custom field values. But Asana’s workflow capabilities are designed around project orchestration, not process orchestration. If you need the same workflow to run 50 times simultaneously with cross-instance tracking and analytics, you’ll hit limitations. For project-level complexity, Asana is capable. For process-level complexity - running, tracking, and improving the same workflow across many instances - a dedicated process tool is a better fit.

Does Asana have AI features?

Yes, and they’ve expanded significantly. Asana introduced AI Teammates (AI agents that handle project tasks like triaging requests and drafting updates), AI Studio (custom AI-powered rules and Smart Projects), and a Claude integration powered by Anthropic via the Model Context Protocol. These features focus on making project management faster and reducing manual coordination work. They’re useful for summarizing project status, suggesting task assignments, and automating routine project decisions. The AI features operate within Asana’s project-centric framework though - they make projects smarter, not processes repeatable.

Is Asana good for small teams?

Very good. The free Personal plan supports up to 10 members with unlimited tasks and projects, which is more generous than most competitors at that tier. Small teams doing project-based work - a startup coordinating product development, a small agency managing deliverables, a nonprofit organizing events - will find the free plan genuinely useful. You only hit the paywall when you need timeline views, portfolio tracking, custom fields, or automation rules. For small teams whose work is process-heavy (running the same SOPs repeatedly), a tool designed for that purpose will serve you better even at small scale.