Sometimes, due to time and budget constraints, there isn’t an overarching project to place a task, a situation that — for us here at Octane — often arises in the aftermath of completing a major project, where we find ourselves in that weird hinterland between the doing and the planning.
When we begin a new task, we first need to do a few things first (such as open at least one application, either running native on a computer or something on the web, and then reappraise ourselves with the instructions and the requirements), before reminding ourselves what we did before — the list goes on.
Sometimes, this time spent preparing needn’t be replicated if we think more about what needs to be done and line the tasks up such that the initial preparation for one is applicable to those other tasks in the sequence.
What remains should be a production line of tasks with a slither of preparation in between (switching to a different set of instructions or files in the same project folder, as an example), where you then get on with the — uh — task at hand.
So, with this in mind, I conjured up an graphic to illustrate this approach, which — I hope — makes sense!