This seems so obvious now I've read it. When I think of how many small tasks I've never got around to doing it's embarrassing.
A small, but important part of GTD: there is a concept of a "capture system". As soon as there's something that's a TODO or task to be done and you are working on something, put it into your capture system, be it a text file, a TODO app, etc. Process the capture system regularly, filing the items into projects (can be as simple as separate TODO lists). So here's the key difference to what you mentioned: only now while you are filing, do you do those tasks that take 5 (or 2) minutes or less.
As a developer who works on my laptop most of the time, I have a global keyboard shortcut that brings up a prompt with textbox that lets me quickly something (appended to a text file) and go back to work without disrupting my flow.
- the idea that, if you can do something in 5 minutes or so, just do it rather than keep putting it on to do lists.
- breaking down complex projects into discrete small concrete tasks.
Both are good ideas which do help me.
One thing about procrastination that often seems to be overlooked though is procrastinating about things that really do need to get done sooner or later (If I don't do the expense report, no one else is going to do it for me.) versus procrastinating about doing some project or making some plans because there's a voice questioning whether you really need to or want to do this project at all.
Now, I suppose in the latter case, a hyper-organized person would create an action item to "get more information" or something along those lines. But sometimes letting ideas just sit and percolate in a future projects queue works OK too.