Blocked-work answers need current tasks, while retrieval still rewards broad project history.
Project managers need an immediate handoff to act on, while the retrieval path must protect latency and context cost.
Who you’d be doing this for
“My director asked what was holding the launch, and I got three old status updates instead of the task waiting on legal.”
Tuyet Kittisak · Program Manager
Runs cross-functional enterprise initiatives and depends on AI Teammates to identify stalled dependencies across active projects.
What is at stake
Blocked-work queries are surfacing old project updates instead of actionable tasks. You have to weigh ranking precision against retrieval latency and context cost.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- actionable handoffs vs broad project context
- ranking quality vs retrieval latency
- AI usefulness vs data ownership boundaries
- fast rollout vs validated evaluation
Why Asana
AI Teammates depend on the Work Graph and OpenSearch to turn enterprise project activity into useful next actions.
Written with these in mind
Not your kind of problem? 28 more at Asana, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.