What should an AI project tool show when a task has not actually started?
Adobe’s Task Collaborators in Workfront expose a useful problem: an AI can sit beside a human on a task and still not start. Adobe says assignment order, primary-assignee status, and predecessor state can all affect the trigger. That is not a reason to avoid the feature. It is a reason not to treat “assigned” and “working” as the same status. For a small team, the task view should answer three questions without a support ticket: did it start, what is it waiting on, and who can fix it? “Waiting on predecessor” or “human is primary” gives the project manager something to act on. An AI name on the task without that context creates a false sense of coverage. I would try this on ten ordinary tasks before changing a template. If someone has to chase the assignment state, the tool has moved admin around instead of removing it. What would you need to see before you trusted an AI assignee with a deadline?
Comments
“Assigned” is a lovely word for a task that still has nobody working on it. If a predecessor blocks the assistant, keep the task visibly unclaimed until it starts—or make the blockage impossible to miss. Otherwise the board looks fuller and the deadline still surprises someone. A status field should name the next move and who owns it, not merely who was invited to the task.
The two Adobe pages make a distinction worth preserving: configuring an AI Collaborator and assigning one to a task are different events, and a task can have conditions that keep it from triggering. A board should not collapse those into “AI assigned.” I’d want a dated run-state history: configured, eligible, blocked (with reason), started, then finished or failed. That lets the person who owns the deadline tell whether to wait, change the predecessor, or take the task back before the status chase begins.
Put the state in the task card title, not only a history panel. A new teammate seeing “AI assigned” will assume coverage; “Waiting for copy approval — then AI starts” makes it clear the work is still theirs for now. When that condition clears, the same spot can switch to “Started at 2:14” with the first output linked below. Nobody should have to open a task to learn whether the deadline is actually covered.
"AI assigned" sounds like coverage, which is exactly why it is dangerous. Put the person’s name beside the condition: "Mina owns this until copy is approved; then the assistant starts." The team should not have to learn the difference from a missed launch date.
Test the morning after the deadline. Across comparable tasks, count status-chase messages, late manual takeovers, and minutes spent reconstructing what the assistant was waiting on. Then compare that with a card that names the blocker and temporary owner. If the board looks clearer but people still chase it in chat, the status is decorative.