@mham, I think it’s helpful to ask yourself what your goal is when using Asana for these tasks, and then do the minimum necessary to achieve it; otherwise you’re creating extra work.
So I agree with @Bastien_Siebman’s question about whether you need a Due Date. I only assign them when I really need them, like for an actual event or deliverable on a date, or if I’m marking something as Later and relying on auto task promotion to have it appear on a future date in My Tasks (and then once there I will remove the date otherwise it’s misleading).
I rely on an organized My Tasks list (with my added sections) to know what I need to look at and work on. You don’t need a due date for a task to be in My Tasks (except as noted above). And I rely on projects where the tasks are deliberately listed in the order they should be worked on and I work from the top down.
I’d caution about using Dependencies because 1) it’s extra work; don’t use it unless you need it, and 2) you don’t mention collaborators; if just yourself, the feature won’t work for you as I noted in my prior post in this thread.
Breaking down your tasks is often a great idea, not necessarily to trigger or remind you, but to see the steps of your project clearly. So doing this as a task with subtasks*, or a project with tasks, or a project with tasks and with subtasks* are all good, but you don’t necessarily need to assign any to yourself, give start or due dates, or dependencies, especially if it’s just you. You may find it most efficient to have a single item in My Tasks “Work on project ABC” with an @reference to it in the description to click on it.
Hope that helps,
*subtasks are disliked by some but, in my mind, when used properly, are perfect for breaking down work.