Okay, now that Asana has a mechanism that doesn’t allow you to complete a task until the dependency is complete. If you take this a step further, you will save all of us a lot of time and headaches with the subtask “add to project” concept.
Here’s an example of video production broken up into multiple phases.
Development
- Concept
- Script
Pre-production - Coordination
- Obtain assets
- Talent scout
Production - Load-out
- Shooting day(s)
- Load-in
Post Production - Log/Ingest
- Edit
- Sound mix
- Color grading
Distribution - Channel
- YouTube
- Social
So, there’s the basic layout… but here’s the thing… I don’t really need to clog up the task list with things people can’t possibly work on until they get to that phase. So for example, there’s no real sense showing any of the tasks from Production through Distribution until the project is in the production phase. So by setting things up as dependencies, and completing the tasks in the pre-production phase, that would auto-promote to the project the production items. Then when that phase is complete, it will auto-promote to the project, the post production phase, etc.
The only other thing that would help make this process (and many other processes easier) is allowing us to mass select tasks and demote them to subtasks, and vice versa. Without having to use the search function, or go into individual tasks/subtasks.