r/projectmanagement • u/gangleskhan • 1h ago
ISO best practices for managing reviews in Asana (or whatever tool)
Looking for feedback on best practices when it comes to reviewing assets in Asana. Specifically how people are structuring the tasks and subtasks involved. I have more of a platform background than a project management background, so hoping to learn from people who know more.
Our typical setup looks something like this:
Parent task (e.g. landing page)
* Write Copy
* Build Page
* Approval (reviewers put their feedback in the comments of this task)
* Review (person A)
* Review (person B)
* Implement changes
* Handoff
In this structure, we expect that person A and person B will put their feedback in the comments of the subtask called "Approval." This has worked fine for years, but now with a larger team I'm getting complaints that it's too messy and confusing to have all the feedback in that Approval task. Instead, people are asking to have it within each person's review task. So like this:
Parent task (e.g. landing page)
* Task
* Task
* Approval
* Review (person A) (Person A's feedback here along with any clarifying conversations)
* Review (person B) (Person B's feedback here along with any clarifying conversations)
* Implement changes
* Handoff
To me, this seems more confusing, because now the person making the changes needs to sift through multiple tasks assigned to others and find all the feedback and dedupe overlapping feedback, and potentially have the same or slightly different conversations with different people.
Do you convert every point of feedback into a new subtask for the person making changes? If so, who is aggregating and assigning those? A project manager, I assume? And where are you housing that?
I'm open to changing our system, but I'm interested in aligning with best practice more than "what So-and-so likes." So, how do you handle reviews effectively?