I personally love those recipe websites where there's a nice long story at the start before you even get to the recipe, and I think this is probably one such recipe that could benefit from a little more backstory.
The most interesting thing about the recipe is the creation of the custom status. It puts one more thing into the Project Owner's list of to-do's [which is now they have to come back and change that status whenever the task is ready to start]. There's no way to automatically set a task to this custom status without the use of fusion, so this is something a Project Owner has to do manually. It's the equivalent of a recipe that starts with an instruction to "make your own phyllo dough" -- time-consuming and best left for rainy Saturdays. And some customers just like rainy Saturdays!
We have thousands of projects -- so tens of thousands of tasks, and this wouldn't be a workable solution in our company. However, Workfront is very customizable and different customers have different uses. For a more high volume shop I would suggest using a more automated solution like using store-bought phyllo, or combining use of the Task "Can Start" field, and task predecessors.
