I've been wanting for awhile to ideate a methodology for creating tasks and goals in the situation you have a goal and one task (which is usually like: 'work towards the goal') to end up with multiple tasks that can be done concurrently and so can be scheduled in alternating blocks of time. And I finally got around to doing that

I think the core idea behind what I found is like: 15% +- 10% of tasks / time / resources should be devoted to situation-analysis, exploring ways to do things, and organizing, including ways to parallelize tasks. There's no universal way around devoting time to exploring how to parallelize a task. And, generally, all individual tasks can be split into a series of tasks that looks like: Explore / organize it -> Make it -> Extract the best parts from it -> Clean it all up. The exploration / organization part in general has an effect sort of like software testing: you can make do without it, but you end up with an organizational debt that makes your project more brittle, and you feel it hard later on