Thank you for sharing this perspective! Couple thoughts:
I was implicitly using similar approach by front-loading planning and creative work. Once that’s done one can just execute the tasks without switching back into ‘planning’ mode.
For the (repetitive) negative tasks, I would add considering automating them or minimizing your effort. It might also make sense to understand what exactly you don’t like about them—sometimes this is something trivial and easy fixable (like some inefficiency).
‘Replacing guilt’ series (“How we will be measured” post in particular) gave me a new perspective for getting rid of negative tasks (and tasks in general). Basically some of them might have nothing to do with the actual success of the project and instead just be traditions or rudiments. So instead of asking ‘is this actually necessary’, I suggest to ask ‘is this important for the project and why’.
Thank you for sharing this perspective! Couple thoughts:
I was implicitly using similar approach by front-loading planning and creative work. Once that’s done one can just execute the tasks without switching back into ‘planning’ mode.
For the (repetitive) negative tasks, I would add considering automating them or minimizing your effort. It might also make sense to understand what exactly you don’t like about them—sometimes this is something trivial and easy fixable (like some inefficiency).
‘Replacing guilt’ series (“How we will be measured” post in particular) gave me a new perspective for getting rid of negative tasks (and tasks in general). Basically some of them might have nothing to do with the actual success of the project and instead just be traditions or rudiments. So instead of asking ‘is this actually necessary’, I suggest to ask ‘is this important for the project and why’.