I don’t agree with you, “>” is the typical indicator of a breadcrumb, and anything on the left is higher in the hierarchy, isn’t it?
You did mention breadcrumb, but you don’t seem to consider what’s currently on the screen to be one?
@Bastien_Siebman is right; the accepted standard UX for breadcrumbs is:
Top level > upper level > next lower level > etc.
This is how Asana has implemented it, so that’s correct.
However, the thing that is somewhat non-standard is that they put each entry on its own line. I imagine they did that because the width of the task detail pane is not that wide. Still, I think it adds some cognitive friction and IMO causes one to have to stop and think about that element, if even for a second or two, which is not great.
From the gold standard of UX design (they’re talking about mobile but it still applies generally):
@Bastien_Siebman I think what @Phil_Seeman mentioned about the breadcrumb format here wrapping onto a second line is what is throwing me off. Also, I usually only go one level deeper than the top-level task, so to me, the “[parent task name] >” felt more like a back arrow than a breadcrumb. I just did a quick test of a 4-level deep set of subtasks and that looks more intuitive and makes total sense.