New answers tagged

0

I build software, and often have to switch contexts. A few things that have help me: Keep a clear task/todo list for each project. Make sure that the items lists the goal and any constraints in terms you will understand when you switch back. When you leave off for the the day, or to switch contexts, make a good note about what you were trying to ...


0

It's all about context. If the next action is closely related to what you're already doing, then it can makes sense to do it if you're not over a barrel on other things you need to do. But, if you have other must-do tasks, then it may make more sense to get those done before continuing with the next step of the task you're on. Basically, try not to switch ...


6

Let's take an extreme example: Imagine that I'm about to go on holiday, and I have a plane to catch this afternoon. I've got a taxt booked to take me to the airport, and it is due any minute. So, I'll just wash up these cups before I go... Oh look, I'm out of washing up liquid! And the cupboard under the sink needs a good clean-out, too. Should I go to the ...


3

If your projects are computer related you might consider keeping a detailed log of your activity using a tool like EverNote or OneNote. I've gotten in the habit of doing this and it's a great aid to recall where I left off when I go back to a task I stopped working on weeks earlier, or I encounter an issue similar to what I resolved weeks or months earlier ...



Top 50 recent answers are included