In another thread, @Noah_Tomlin asked:
I think this is actually a fantastic question, since Asana uses the phrase “workflow” often in writing and speaking - and even moreso now that their vision includes a future “Workflow Store” - and I have at times been unclear what they mean by “workflow”. (And as an aside, as the author of the Flowsana “workflow automation” integration, I’m not a disinterested party in this matter!) So I set out to see what I could find as an answer to this question.
I think the best answer I came across can be found here:
In other words, a “workflow” to Asana is a process for getting something done, for accomplishing some outcome or fulfilling some commitment. That process is then by definition going to involve some series of tasks which accomplish that outcome.
I think to Asana the simplest representation of a workflow in Asana is a project. (You can see that in their examples on the above-referenced page.) But I don’t think it will always be that straightforward; for example, sometimes a project could be said to consist of a number of discrete workflows, right?
So in summary, I think the Asana definition of a workflow is a set of tasks that accomplishes some discrete outcome.
What do y’all think? (Remember, the game here is not to identify what we think a “workflow” means to us, but what it means to Asana.)