I see lists getting due dates and descriptions and attachments and comments... Since the difference between a list with tasks and a task with subtasks seems to blur more and more, you might as well go total inception by storing lists and subtasks as tasks! :) So you end up with a hierarchy system that can be as deep or shallow as the user wants. For example I have that 1 team with 1 project with 1 list (and I even struggle with naming them) - so I wouldn't even need those 3 hierarchy steps in that case. But then there might come up that one task where I have some subtasks, and I actually want to split those subtasks into subtasks, but I'm not allowed to. So I imagine the whole hierarchy as a tree of tasks with board view, list view, box view, etc. And in the sidebar I'd like to chose how deep a tree should be shown/expanded. Maybe you already thought about this and there might be reasons for avoiding this. Then I'd be curious to hear them. In my imagination it sounds good :)