Thank you for your great input on project management. Super valuable tips! I have a question: In your document, you mention the statuses "todo", "in progress", "internal review", "in revision", "in client review", "blocked", "deliver & close" und "completed" but in the video, you don't use “in revision” and “deliver and close” and mention handling feedback loops as subtasks instead. (But wouldn't the status “internal revision” be unnecessary?) The Q: When I use a status like "Internal Review," the task doesn’t automatically show up for the team member who needs to review it. The due date would end up being incorrect, and it’s hard to automate because different tasks require different reviewers. I could create an additional view where team members see tasks in review where they’re assigned as the reviewer, but then all to-dos wouldn’t be in one place anymore. How do you handle this? I really like the idea of the status "Deliver & Close" status you described in the document. It seems super useful because it ensures tasks don’t need to go back to "In Revision" after changes but can move directly to "Completed." But I see the problems I mentioned above.
The statuses are more used for the parent task to give high-level oversight to an account or project manager. You should build all review cycles in to your subtasks so that people have actionable tasks to complete something and don't just rely on a status and automations to pass work amongst the team. For example, your workflow for a deliverable could look like this: Scope Publish Create draft Internal review of draft Revisions of internal review Send draft to client Receive & share client revisions / follow up with client Round 1: Apply revisions from client Round 1: Internal review of revisions from client Round 1: Apply revisions from internal review Round 1: Send to client Round 1: Receive & share client revisions / follow up with client Round 2: Apply revisions from client Round 2: Internal review of revisions from client Round 2: Apply revisions from internal review Round 2: Send to client Round 2: Receive & share client revisions / follow up with client Final Round: Apply revisions from client Final Round: Internal review of revisions from client Final Round: Apply revisions from internal review Final Round: Send to client for Approval Final Round: Confirm client approval
A couple questions; 1. Is there a reason why you only seem to use parent task > sub task > checklist and never use sub-sub tasks or even sub-sub-sub tasks? 2. I’m in a finance/commercial consulting role currently and thinking of using ClickUp to streamline their finance department and hopefully the whole company over the long term. Just starting with the finance function and was wondering if any of your videos show that Finance department folder you have within Operations? I was originally thinking I’d need Finance to be it’s own space but I’d love to see why yours isn’t set up that way 😊 Thanks in advance. I’m really enjoying your videos!
1. Sub-sub tasks add an extra layer of complexity and decrease visibility in ClickUp. With out methodology, all subtasks are actionable tasks that are grouped by a non-actionable parent task. If we incorporated sub-sub tasks, that would make some subtasks non-actionable. 2. We don't have any videos that walk through that, but it's also not overly complex. That's really just a folder that stores tasks related to finance. We see finance as a smaller item underneath operations so that's why it's a folder in that operations space. But this is mainly for agencies, and it can vary for different companies.
This video explains our whole reasoning behind subtasks. Subtasks are what help build timelines in your work and ensure nothing slips through the cracks. Your parent task = the name of the deliverable (i.e. Blog Post), and your subtasks represent all of the steps needed to complete that deliverable (i.e. write draft, review draft, create thumbnail, send to client for review, etc.) Each subtask has it's own assignee and due date and helps the team know what they need to work on and when when it's due.
![How to Manage Your Team in ClickUp [Team Performance Dashboard]](http://i.ytimg.com/vi/sHMQjoRc9qw/mqdefault.jpg)
![How to Manage Your Team in ClickUp [Team Performance Dashboard]](/img/tr.png)
![ClickUp for Project Managers [The Ultimate Guide]](http://i.ytimg.com/vi/Alxgyb1JkD8/mqdefault.jpg)
![ClickUp for Account Managers [The Ultimate Guide]](/img/n.gif)
🚀Let us build you a more productive, profitable, and healthy agency in ClickUp: www.zenpilot.com/clickup-for-agencies
These videos are great! Beyond the clickup help, you all do a great job of explaining things in general! Keep it up!
Thank you for the feedback!
Thank you for your great input on project management. Super valuable tips! I have a question: In your document, you mention the statuses "todo", "in progress", "internal review", "in revision", "in client review", "blocked", "deliver & close" und "completed" but in the video, you don't use “in revision” and “deliver and close” and mention handling feedback loops as subtasks instead. (But wouldn't the status “internal revision” be unnecessary?)
The Q: When I use a status like "Internal Review," the task doesn’t automatically show up for the team member who needs to review it. The due date would end up being incorrect, and it’s hard to automate because different tasks require different reviewers. I could create an additional view where team members see tasks in review where they’re assigned as the reviewer, but then all to-dos wouldn’t be in one place anymore. How do you handle this?
I really like the idea of the status "Deliver & Close" status you described in the document. It seems super useful because it ensures tasks don’t need to go back to "In Revision" after changes but can move directly to "Completed." But I see the problems I mentioned above.
The statuses are more used for the parent task to give high-level oversight to an account or project manager.
You should build all review cycles in to your subtasks so that people have actionable tasks to complete something and don't just rely on a status and automations to pass work amongst the team. For example, your workflow for a deliverable could look like this:
Scope
Publish
Create draft
Internal review of draft
Revisions of internal review
Send draft to client
Receive & share client revisions / follow up with client
Round 1: Apply revisions from client
Round 1: Internal review of revisions from client
Round 1: Apply revisions from internal review
Round 1: Send to client
Round 1: Receive & share client revisions / follow up with client
Round 2: Apply revisions from client
Round 2: Internal review of revisions from client
Round 2: Apply revisions from internal review
Round 2: Send to client
Round 2: Receive & share client revisions / follow up with client
Final Round: Apply revisions from client
Final Round: Internal review of revisions from client
Final Round: Apply revisions from internal review
Final Round: Send to client for Approval
Final Round: Confirm client approval
A couple questions;
1. Is there a reason why you only seem to use parent task > sub task > checklist and never use sub-sub tasks or even sub-sub-sub tasks?
2. I’m in a finance/commercial consulting role currently and thinking of using ClickUp to streamline their finance department and hopefully the whole company over the long term. Just starting with the finance function and was wondering if any of your videos show that Finance department folder you have within Operations? I was originally thinking I’d need Finance to be it’s own space but I’d love to see why yours isn’t set up that way 😊
Thanks in advance. I’m really enjoying your videos!
1. Sub-sub tasks add an extra layer of complexity and decrease visibility in ClickUp. With out methodology, all subtasks are actionable tasks that are grouped by a non-actionable parent task. If we incorporated sub-sub tasks, that would make some subtasks non-actionable.
2. We don't have any videos that walk through that, but it's also not overly complex. That's really just a folder that stores tasks related to finance. We see finance as a smaller item underneath operations so that's why it's a folder in that operations space. But this is mainly for agencies, and it can vary for different companies.
@@ZenPilotgreat thank you for getting back to me. That explains a lot. 😊
So I've always been told to NOT use subtasks... you are showing a 100% focus on them. Do you have comments between the two methods?
This video explains our whole reasoning behind subtasks. Subtasks are what help build timelines in your work and ensure nothing slips through the cracks.
Your parent task = the name of the deliverable (i.e. Blog Post), and your subtasks represent all of the steps needed to complete that deliverable (i.e. write draft, review draft, create thumbnail, send to client for review, etc.)
Each subtask has it's own assignee and due date and helps the team know what they need to work on and when when it's due.