Why using subtasks for document review might be better than you think ?

:fire: My position on subtasks is pretty well-known: they are really powerful but they come with limitations you should be well aware of.

:mag_right: The other day a client shared with me an interesting benefit of using subtasks for document review. They had a document attached to a task, and each subtask assigned to a reviewer. The reviewer was giving feedback in the subtask.

:+1:t3: They realized the benefit was that a reviewer would not be influenced by what other people said. They were able to work and review in isolation, and share feedback on their own subtask.

:hugs: I usually advocate for the same task to be passed around, but in this case there is a hidden benefit of using subtasks!

What do you think?


Going through the reviews afterwards may be more tedious as you have to open all subtasks.

1 Like

I like Subtasks for assigning tasks like this, but i prefer people commenting on the main task.

It would be a pretty nice AI feature: “Summarize all Subtasks” to get information back to the maintask


@Jan_Blankenhorn This is a great Idea!

I do like this idea, but if the purpose is to not be influenced by others’ comments, can’t the assignee just look at the other subtask comments? Not sure I understand that piece.

1 Like

That’s indeed a drawback.

Sure but it defeat the purpose described here: make sure people are not influenced by each other.

They can’t because they don’t see the parent task so the subtasks will be hidden

I advocate for subtasks. They give you a clear overview of what has been done by whom within the main task. The subtasks can then be shown in workload and my tasks days ahead instead of receiving the main task at some point. Commenting on the main task!

I like the client idea to not be influenced by others! Maybe make the main tasks or subtaks private, so the others can see the content?

1 Like

I use this feature before, assigning literature to be reviewed, and then I create a shared doc, for input and sharing ideas that is attached to the larger task, sometimes we use the main task as a major agenda item when we are looking at big ideas or brainstorming

I route Marketing content and prefer reviewers see each other’s comments to avoid conflicting changes. This way, I won’t need to reach out individually to explain why I can’t incorporate certain edits. So, I am an advocate of summarizing all edits on to the parent task. There should be an option to summarize comments, or turn it off.

This indeed sounds like a great suggestion that would leverage AI functionality.

We use subtasks for reviews but encourage comments at the main task level so people can not duplicate the same feedback. But in this use case, it still doesn’t make sense to me since the attachment is at the main task level anyway.

1 Like