I just created a blueprint. But when I go to use it, it's telling me it will be applied to "tasks". I'm sorry, aren't blueprints supposed to be applied to projects....you know bc projects usually have MANY stages, but tasks only a few?????  This is why CRM has blueprints for leads and not calls, tasks and events.

So i created this big blueprint which has been applied to tasks, and I realize that bf I can get to the task status that applies to a particular task that is located lower in the pipeline, I will have to go through all the statuses for the higher up tasks.  

so it got me thinking, what did zoho create the blueprint to do. And yes, it says to organize processes.  TASKS ARE NOT PROCESS. PROJECTS ARE PROCESSES. 

It also go me thinking if there's a way to quickly see what stage the project is in...and I discovered no there isn't. Which tells me that while the application says PROJECTS, Zoho projects team is quite confused as to what project management looks like. They think project management equals task management....bc everything is geared towards managing tasks, and any project management that occurs is simply by happenstance.  

So in order to use the blueprint properly...that is to actually manage projects with it instead of tasks, one will have to create different blueprints for each tasklist and or milestone....which will be a substantial amount of blueprints because different projects types usually require different milestones.

Zoho, sigh.  What a disgraceful let down... i say that bc being that process management is highly complicated, convoluted and time consuming, and ZOHO moves at a snail's pace with updates, this broken system will persist for another 20years probably.