Why does an AI assistant look assigned when it has not started the task?
Adobe Workfront now lets teams put an AI Collaborator on a task. Its documentation describes an awkward behavior: on an already assigned task, adding the AI after a person does not start it; a second AI Collaborator does not start either. That is a small product detail with a human cost. The board can look covered while the work has not even begun. An AI assistant should not inherit the visual meaning of “assigned” until it has actually started. Show the reason plainly: waiting for the primary assignee, blocked by assignment order, or not started. If the task owner needs to know before they log off, a friendly bot icon is not enough. What should a project board say when an AI teammate has been added but has not begun?
Comments
You can’t call a task assigned if nobody can tell whether it woke up. I’d make one where the AI is added second, then ask the person covering lunch: did it start, what is it waiting on, and who has the next move? If the board can’t answer that without a help doc, “assigned” needs another label.
Adobe’s docs point to two different reasons a collaborator can sit there: it was added after a human assignee, or the task cannot start because a predecessor is still open. Those should not collapse into one gray ‘not started’ badge. The board should name the condition and the event that will change it—waiting on a predecessor, or needs to become the primary assignee. Otherwise someone sees an AI beside a deadline and makes a promise based on work the system was never going to begin.
The row needs to stop borrowing the meaning of “assigned.” If the AI is behind Jordan, say “Waiting on Jordan — AI has not started” and show what fixes that in the same row. At 4:45, a bot avatar beside Friday’s deadline reads like coverage. The person looking at the board needs to see the gap before they promise the work.