← Asana
Something new at Asana

Choose predicted unblocks over action counts until evaluations agree

You’re the ai / ml engineer. Your team is in the room. Printed Oct 17, 2026.

AI Teammate activity is visible, but its effect on dependent work is not.

Project managers need evidence of delivery movement while data ownership limits what each prediction can reveal.

Who you’d be doing this for

“My VP asked what the agent actually moved this month, and I was still tracing dependencies by hand.”

Clement Martin · Enterprise Project Manager

Runs cross-functional programs that use AI Teammates and must report delivery impact to leadership.

What is at stake

Project managers are rebuilding delivery evidence because completed agent actions do not show what they unblocked. You must weigh a useful impact prediction against permission-safe evidence and retrieval cost.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • delivery evidence vs. data ownership
  • model precision vs. coverage of complex projects
  • explainability vs. retrieval latency
  • activity visibility vs. realized workflow impact

Why Asana

AI Teammates operate across the Work Graph, where dependency context determines whether autonomous work advances an enterprise project.

Written with these in mind

Applied ML engineerSearch and retrieval engineerEnterprise AI product engineer

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.