I'm still having trouble, I think, on dealing with ambiguous tasks. These are cases where the exact deliverable has a range of acceptable quality and the exact approach for getting there can't be known in advance.
e.g., lets say my task is "Sell old uke on ebay"
One of my next actions is to get the thing boxed up. To do that, I need to know the size. So the task I have is:
"Measure size of uke"
but really the next action is to get a tape measure, but it seems silly to me to put
"Get tape measure"
when it's pretty obvious that since I'm already in that context (Home), I'll need to get the measure. But, is that the way I'm supposed to do it?
The more complicated case is something like "prepare materials for status meeting X." In this case, the range of acceptable outputs is pretty variable. As I'm going through it, I might notice that material item x (the list of issues) could be automated. If I automated it now, I'd still get the task done, with better quality, BUT I could get the task done without doing it now and just spin this task off as a someday/maybe.
Or, let's say I notice when I'm going through that some of the issue statuses are messed up or haven't been kept up to date. I could fix them permanently in their source (might take a while), or just paste and hack into the document. Again, I could spin it off as a separate task, but it's the same trade off.
In these cases, I often end up tackling the separate task because of it's long term value, but I end up eating time that, if I looked at all my tasks in a in the moment or weekly review, I might not have picked that as a "must do now."