The brief says "Design social assets." Due date: Friday. Assignee: you.
There is no brand guidance attached, no link to the campaign deck, no note about which formats are needed. The task exists. It just does not contain the information anyone needs to do it. So before work starts, there is a round of Slack messages, a rescheduled call, and one frustrated designer who is now a day behind.
This is the most common friction in Asana, and it rarely gets talked about: the gap between a task existing and a task being useful.
The tool and how teams actually use it
Asana works well for creative, marketing, and product teams where collaboration flows naturally but deadlines stay fixed. Marketing teams use it for editorial calendars, campaign launches, and creative asset approvals; product teams track feature requests, sprint planning, and roadmap visualization.
That breadth is also why the friction pattern is so consistent. Different functions, same problem: users create tasks without a clear sense of what they aim to achieve. This leads to confusion, miscommunication, and ultimately a lack of progress.
The tool is not at fault. It will accept a task called "thing" with no description, no due date, no assignee. What you put in is what the team gets. And most teams, under deadline pressure, put in the minimum.
Where the friction actually lives
There are three places work stalls in Asana before it even starts.
The empty description field. A task with only a title is a placeholder, not an instruction. The habit of regularly updating tasks and marking them complete matters - but there is nothing worse than looking at overdue tasks, poor descriptions, and no communication. When someone finally opens the task two days later, they spend the first hour reverse-engineering what the requester actually wanted.
The repeatable-process trap. Asana's project-centric design starts to buckle with repeatable processes like employee onboarding, approval chains, and compliance procedures - because Asana treats every instance of a repeated workflow as a standalone project.
A 200-person company onboarding four people per month generates four new Asana projects per month for onboarding alone, each with 25-40 tasks spread across HR, IT, facilities, and the hiring manager. After a year, there are 48 completed onboarding projects cluttering the workspace, and no easy way to answer: "What is our average time from offer acceptance to fully onboarded?"
The context scattered across other tools. After kickoff, the details needed to execute - deliverables, timelines, ownership - are still scattered across decks, transcripts, and conversations. Work effectively stalls until that information is structured into a clear brief.
The system is only as good as the data in it. Everyone knows this. Nobody has time to fix it.
What good AI inside Asana would do
Asana has been building in this direction fast. The Winter 2026 release introduced a Slack with AI Studio integration that captures requests where they happen and automatically converts them into structured work in Asana, giving teams the full context required to move from intake to delivery.
The Spring 2026 release addressed a problem every leadership team is wrestling with: most teams are already using AI, but organizational productivity is not following - because AI tools that make individuals faster do not automatically make workflows faster.
The Campaign Brief Writer is the clearest example of what this looks like in practice. You give the AI teammate context - a brand voice guide, the template you want - then assign it a task with the kickoff transcript, go-to-market deck, and any relevant Asana tasks. As it works, it can pull from past campaigns, templates, and team goals to understand how to structure its output.
As it builds the brief, the AI teammate actively flags what is missing - undefined KPIs, incomplete timelines - and assigns follow-ups to the right stakeholders, tagging them directly in the project.
That last part matters most. The AI is not just drafting; it is auditing the task against a standard and surfacing the gaps before anyone starts work.
A teammate like Beagle, sitting in Slack, can do a version of this at the intake layer: when a request lands in a channel and someone is about to create an Asana task, it can ask the clarifying questions upfront - format, deadline, linked goals, known dependencies - before the task is created half-empty.
The structural thing that does not get fixed automatically
There is a ceiling, though. The problem every leadership team is wrestling with right now is that most teams are already using AI, but organizational productivity is not following - because AI tools that make individuals faster do not automatically make workflows faster, especially the cross-functional work that actually runs the business.
Cross-functional is where Asana tasks go quiet. The marketing brief is complete. It has a due date, an assignee, and a linked campaign goal. But when it depends on legal review, which depends on a vendor contract, which depends on procurement - none of those dependencies exist as explicit task links. Someone is carrying the dependency map in their head.
Asana's AI risk reports help identify potential project risks before they impact timelines, surfacing AI-powered analysis of project activity and delivering weekly automated risk assessments based on the latest project updates. That is useful for visible risks. The invisible ones - the dependency nobody wrote down - still fall through.
The honest read is that Asana gives teams an excellent structure for making work legible. The friction is almost never the tool - it is the blank description field, the unnamed dependency, the context that got shared in Slack and never made it into the task. AI can close that gap, but only if someone decides it should.
Most teams never decide. The task just sits there, empty, waiting for the designer to ask the obvious question.