As the person responsible for our Asana implementation, I’ve been frustrated with the “one assignee per task” limitation for a while now. I’ve tried to get on board with that philosophy, but in practice, it’s caused more problems than it solves—especially when we’re trying to expand the use of Asana.
For example, our operations team often has tasks that require two or more people working together. Not being able to simply assign a single task to multiple team members forces us to create separate tasks, which scatters comments and attachments all over the place. And for people who aren’t super tech-savvy, it’s an extra hassle.
This has come up in various parts of our organization, but it’s been a real roadblock for the operations team—our largest department. We’re already pretty deep into Asana, but sometimes I worry we chose the wrong tool, wishing we’d gone with something that supports multiple assignees under one task.
We really do love Asana, but I wanted to share these honest thoughts—really hoping that this gets addressed in some way.