Quote:
Originally Posted by SpiralOcean
I like your 'halo effect' term.
|
Thanks. I felt clever when I thought of it. It’s nice to feel clever for a moment.
Quote:
|
Another workflow I've tried to help me stay on task is: develop a widget that doesn't let me work for too long without bringing the task that I've said I'm working on, back in front of me.
|
I think I would find myself ignoring that just as readily as I ignore the voice in my head that is trying to tell me the same thing. :-) I totally understand the impulse, but I can also predict how I will fail with that approach.
I have a sneaking suspicion that there’s actually a fairly deep problem here, and that Guru Allen would tell us that a bad case of the halo effect is a symptom of generally inadequate capturing. Really, if we’re getting significantly distracted by many new, novel actions that were absent from the trusted system just that morning ... how complete can our system really be?! How good a job can we possibly have done of anticipating what we want to do?
Could the cure for the halo effect be a good dose of brainstorming and harvesting?