Pullein’s video seems to focus on things that can be relegated to a list or that can be templated, which many people do in OmniFocus, NotePlan, et al. And that’s fine. If you have (as his example) a job where stuff comes in, you perform some transformation, then file the stuff away, a checklist or list of steps is desirable. (Noting that the burden of a lot of these “tasks with steps” have been placed on consumers/clients in the 20-odd years since Pullein did this job.) In fact, Atul Gawande wrote The Checklist Manifesto about the power of checklists to help minimize variations and errors, and to help manage increasing complexity.
I would have liked to hear him elaborate more on projects, which he mentions only in passing (watched late last night, so may have missed something). Especially projects that are somewhat ill-defined, and that evolve over time.
Task/project managers with better flexibility surrounding dates would be helpful. E.g.
-
Start
- when do I want to start working on this? -
Seriously
- definitely should be making progress at this point -
Dude!
- can’t do this overnight -
Due
- when do I want to finish it? -
Deadline
- when is the hard deadline?
When I open the app at any time after Start
, I should see that I’ve committed to working on this project, and any others that are past Start
, and not completed. I’d also like to see how much time remains until Due
. And whether I’ve entered the Seriously
or Dude!
phases (only half joking, I would actually use these). These wishes of mine are in “project planners”, but they also assume that you’re sending people to Mars and want to assign resources, have realtime collaboration, etc. Which are way overkill.
Maybe it’s just me.
Finally, our vocabulary is ill-defined. “Task” means different things to different people, as do “project” and other terms. Pullein references GTD when he says a project is anything with 2 or more steps, but then says, no, it’s just a checklist, and shouldn’t be called a project. But, again, this is for lists of steps that have been pre-established – which are essentially “procedures”.
Just thinking out loud. I should probably have just put this into Tana, or Logseq, or Obsidian, or NotePlan, or Notes, or org-mode, …