4 ms·

Thanks for posting this video, I found it really helpful. For people who don't have the time to watch this is a strategy I learned from it that I might try out

by reidjs 6y ago

Thanks for posting this video, I found it really helpful. For people who don't have the time to watch this is a strategy I learned from it that I might try out with my TODOS: "In situation X I will do behavior Y to achieve subgoal Z" His example was "When this workshop ends today, I'm going straight to the library to read 4 pages of that paper that I'm struggling to read to achieve the subgoal of finishing this paragraph in my thesis" The idea is you don't have to think about some vague topic. You just go on autopilot like, oh the workshop is over now I have to do this thing, therefore you're more likely to do it.

DelightOne 6y ago
If you don't have the steps to achieve X and you can't come up with the steps on the fly (or the steps you know do not work) then you will not be able to do X when you want to.
- reidjs 6y ago
  In my understanding X is a situation not a goal to achieve. So it can be as simple as 'Today at 5pm' or 'I am at a bar craving a cigarette'
  - DelightOne 6y ago
    My comment was more a general issue. If you know what to do then planning specific slots to do them, makes sense.
- Tyr42 6y ago
  I know I procrastinate when I don't know how to start. But learning how to break things down into chunks and make a checklist makes it a lot easier to avoid that. A well defined task is actually fun to do, and I'm much less likely to avoid it.
- vitabenes 6y ago
  I think this has to with the unknowns of modern work. In knowledge work, we need to: 1. Define the work 2. Do the work Can't do what's not defined. In general, the simple advice I give our clients is to take a piece of paper and a pen, and put all the ideas about the task out there. Take 5-15 minutes and try to define it. Basecamp's Shape Up book is a lot about managing the unknowns.
mickduprez 6y ago
>> "In situation X I will do behavior Y to achieve subgoal Z" I was pondering something very similar to this about 10 minutes before he talked about it only I was thinking about changing perspective for the given task, that is: "what 'mode' do I have to be in to get this done?" in place of 'Y'. His short sentence is much more elegant than what I was trying to think but I think 'mode' also fits just as well. Basically, I think we get too overwhelmed (emotion) with what we have to do and breaking it down into smaller chucks may not be enough. Breaking it down into modes or specialties might make it less daunting. We can all 'plan', 'study', 'code' or whatever hat you need to wear along the way and wearing them all at once, even on a small task can still be overwhelming. For example, say I have a new coding project but I'm having trouble organising it into chunks as I'm new to the platform/API. What I can do is say "ok, I need to put my 'study' hat on and learn just an overview of how this all works" (study mode) then go back into 'plan' mode to reorganize tasks into further modes to complete item one ('hello world' app say), rinse and repeat.
- vitabenes 6y ago
  I always recommend clients to get familiar with the task. A lot of the stress comes from facing the unknown (unknown codebase, report, process). Your "study hat" is just that - you get familiar with the complex underlying mechanism and then much of the resistance disappears. Get familiar, get started.

by reidjs 6y ago

DelightOne 6y ago

If you don't have the steps to achieve X and you can't come up with the steps on the fly (or the steps you know do not work) then you will not be able to do X when you want to.

reidjs 6y ago
In my understanding X is a situation not a goal to achieve. So it can be as simple as 'Today at 5pm' or 'I am at a bar craving a cigarette'
- DelightOne 6y ago
  My comment was more a general issue. If you know what to do then planning specific slots to do them, makes sense.
Tyr42 6y ago
I know I procrastinate when I don't know how to start. But learning how to break things down into chunks and make a checklist makes it a lot easier to avoid that. A well defined task is actually fun to do, and I'm much less likely to avoid it.
vitabenes 6y ago
I think this has to with the unknowns of modern work. In knowledge work, we need to: 1. Define the work 2. Do the work Can't do what's not defined. In general, the simple advice I give our clients is to take a piece of paper and a pen, and put all the ideas about the task out there. Take 5-15 minutes and try to define it. Basecamp's Shape Up book is a lot about managing the unknowns.

mickduprez 6y ago

>> "In situation X I will do behavior Y to achieve subgoal Z" I was pondering something very similar to this about 10 minutes before he talked about it only I was thinking about changing perspective for the given task, that is: "what 'mode' do I have to be in to get this done?" in place of 'Y'. His short sentence is much more elegant than what I was trying to think but I think 'mode' also fits just as well. Basically, I think we get too overwhelmed (emotion) with what we have to do and breaking it down into smaller chucks may not be enough. Breaking it down into modes or specialties might make it less daunting. We can all 'plan', 'study', 'code' or whatever hat you need to wear along the way and wearing them all at once, even on a small task can still be overwhelming. For example, say I have a new coding project but I'm having trouble organising it into chunks as I'm new to the platform/API. What I can do is say "ok, I need to put my 'study' hat on and learn just an overview of how this all works" (study mode) then go back into 'plan' mode to reorganize tasks into further modes to complete item one ('hello world' app say), rinse and repeat.

vitabenes 6y ago
I always recommend clients to get familiar with the task. A lot of the stress comes from facing the unknown (unknown codebase, report, process). Your "study hat" is just that - you get familiar with the complex underlying mechanism and then much of the resistance disappears. Get familiar, get started.