ollimatrix
Contributor
User Power
Value/Post Ratio
100%
- Jun 9, 2013
- 22
- 22
If you want to achieve a goal, you'll have to do a list of tasks, that help you get closer to that goal.
We all know action is king when it comes to achieving goals: you'll want to cut out distractions, unnecessary busy work (which just keeps you spinning in circles instead of moving forward), stop procrastinating and work on the most important task first.
Sometimes however, it'll be necessary to do another task in preparation, before you can actually do the task that directly leads to your goal.
So you'll end up with this:
I want to achieve a goal, for which I'll primarily have to do A.
But first I have to do B in order to be able to do A.
But first I have to do C in order to be able to do B.
But first I have to do D in order to be able to do C.
But first I have to do E in order to be able to do D.
... and so on.
Assuming I am working on a project, for which I pretty much have to make up the rules as I go, and there's a lot of trial and error involved (it's not a project where the outcome is perfectly clear, and I can follow an existing project plan that lists the steps; there is no "cookie cutter" recipe for my project, neither is there a predecessor who's guideline I can follow), I am wondering the following:
How do I know if I REALLY need to do task E in order to (in the long run) accomplish my goal?
How can I judge if I am procrastinating, if I am doing busy work, of if I am taking the right action, that'll get me closer to my goal?
Any guidelines I can follow?
We all know action is king when it comes to achieving goals: you'll want to cut out distractions, unnecessary busy work (which just keeps you spinning in circles instead of moving forward), stop procrastinating and work on the most important task first.
Sometimes however, it'll be necessary to do another task in preparation, before you can actually do the task that directly leads to your goal.
So you'll end up with this:
I want to achieve a goal, for which I'll primarily have to do A.
But first I have to do B in order to be able to do A.
But first I have to do C in order to be able to do B.
But first I have to do D in order to be able to do C.
But first I have to do E in order to be able to do D.
... and so on.
Assuming I am working on a project, for which I pretty much have to make up the rules as I go, and there's a lot of trial and error involved (it's not a project where the outcome is perfectly clear, and I can follow an existing project plan that lists the steps; there is no "cookie cutter" recipe for my project, neither is there a predecessor who's guideline I can follow), I am wondering the following:
How do I know if I REALLY need to do task E in order to (in the long run) accomplish my goal?
How can I judge if I am procrastinating, if I am doing busy work, of if I am taking the right action, that'll get me closer to my goal?
Any guidelines I can follow?
Dislike ads? Remove them and support the forum:
Subscribe to Fastlane Insiders.