How do you assign a task to your whole team? (surveys, SOP reviews, acknowledgements)

We’re a team of ~10. When I need everyone to do something — complete a staff survey, review an updated SOP, acknowledge a policy — email to the distribution group was the default. I’ve been trying to move this into Asana.

The challenge / question

How do you communicate the request to each member of the team?

Options I see:

  • Individual subtasks, but how do you create them efficiently? The “assign to multiple people” isn’t repeatable and is more work than an email to a distribution list.
  • Collaborators on a single task, but how do communicate it’s actionable and ensure follow-through?

What I ended up building

A rule with a manual trigger button that uses AI Studio to generate individual subtasks, one per team member, each assigned to the right person. The AI instruction is roughly:

Create a subtask assigned to each member of the Everyone team to check out what’s in the parent task and mark their subtask complete when done. The subtask name must not include any links or names. The subtask description must include a short explanation of what to do.

It worked in my first test, after several rounds of testing and refining. But we know that AI Studio is non-deterministic, so will it sometimes create the wrong number of subtasks, miss someone, or write a subtask name that doesn’t make sense? For a compliance use case (everyone must acknowledge), that’s not acceptable.

What worked: The concept is solid. One trigger, individual accountability, completions visible in one place.

What I’d do differently: I’d want a rule that’s fully deterministic — no LLM in the loop for something this mechanical. Why use credits and inference here?

The challenge: Setting up each individual subtask in the rule is possible, but loads of work and maintenance.


Over to you

How are you handling this? Specifically:

  • Do you use subtasks per person, or something else entirely?

  • Have you found a deterministic way to do this without AI Studio (task templates, rules, something else)?

3 Likes

Hi @Liohn_Sherer,

I always do this; simple, quick, easy, no rules, no AI.

Create one task to single-source the content, instruction, attachments, etc.

Create one “model” subtask, something like “Complete survey described in parent task” with a due date.

Open that model subtask in the task detail pane (you have to do this step to use the next feature). Click Assignee, then select Assign to multiple people and enter the team name. It creates a sibling subtask for each team member. You can delete the (unassigned) model subtask.

I’m guessing you didn’t see this, or is there a reason you didn’t want to use this?

Thanks,

Larry

1 Like

Hey Larry.
I am familiar with that function and use it frequently. But it’s a lot of manual steps. It’s good for customizing distributed tasks. In cases where there’s no unique requirements (all team members, “refer to parent task” instructions…) I’m aiming for something more efficient and repeatable. I’m thinking of a makeshift company LMS, for example.
Clicking all those buttons given the automation at our disposal feels like friction.

1 Like

If everyone needs a task, I would assign duplicates and use an Asana team name, so I don’t have to type everybody’s name one by one.

If someone from the team needs to pick up a task, I would multi-home it into a team bucket for them to choose.

1 Like

Using the team name in Assign Multiple is helpful. Thanks for that.

My AI-assisted rule worked nicely today, also. One click, task name and descriptino drafted, 11 subtasks assigned.