Higher Altitudes

N

neil007

0
I am starting to look at higher altitude goal setting now that my 10k and below is working well. How do other people deal with goals?

In 'Ready for anything' DA says that a long term goal such as 'land on mars' is still a project with an NA. So, how about putting goals on the project list and . Or do you keep seperate lists of goals/projects?

Some say that a project is anything that gets done in less than a year. I suppose I think of a project as relatively small and that goals are more important.

Is the difference the TIME the project/goal will take or its IMPORTANCE? I have sort of assumed that the goals list is for the more important stuff. Or is everything 'just a project'?
 
I personally don't think it's about how long the project will last. In my mind to make sure your projects are completed you should actually break them into smaller group and step-by-step you will eventually finish the big project.
 
There are certain things that aren't exactly goals.

For example, I love to write. That's neither a goal nor a project, but I can create goals and projects that support that love. That's part of my higher-altitude planning.
 
neil007 said:
I suppose I think of a project as relatively small and that goals are more important.

Is the difference the TIME the project/goal will take or its IMPORTANCE? I have sort of assumed that the goals list is for the more important stuff. Or is everything 'just a project'?
Click to expand...

You can think of DA's 30K, 40K and 50K perspective as equivalent to 1-2 year goals, 3-5 year goals, and life goals. However, projects are the key link between day-to-day actions and these higher levels. Different levels are not more important- you have to deal appropriately with all of them. You may be about to receive some wonderful award when the police pull you over on the way to the award ceremony for expired plates.
 
Goals vs. Projects

neil007 said:
In 'Ready for anything' DA says that a long term goal such as 'land on mars' is still a project with an NA. So, how about putting goals on the project list and . Or do you keep seperate lists of goals/projects?
Click to expand...
I think it's clearer to say that a long term goal like "land on Mars" causes projects -- if you want to go to Mars, you will have to work your way through a lot of projects before you ever get to launch day.

One of my 30,000-foot items has been the construction of a new house. This house has caused a lot of projects to fall into my lists -- choosing a floorplan, choosing all the stuff in the house (cabinets, countertops, light fixtures, plumbing fixtures, etc.), packing to move out of the house we're replacing, actually moving... and so on.
 
These are the levels that work for me:

Next Actions = Runway
Projects = 10,000 ft
Objectives = 20,000 ft
Goals = 30,000 ft
Roles/Responsibilities = 40,000 ft
Values = 50,000 ft

Goals are general, can correspond to a vision and are geared to a 2-5 year timeframe. They are high level and set the context for Objectives. I define goals for specific roles and/or responsibilities.

Objectives are measurable and have a due date. They are typically the output of yearly planning exercises. They define how I will achieve a given goal.

Projects are again measurable, have a due date and may contain one or more deliverables and/or milestones.

Richard
 
You must log in or register to reply here.
Top