{"id":139,"date":"2009-02-02T16:53:00","date_gmt":"2009-02-02T16:53:00","guid":{"rendered":"http:\/\/joapen.com\/blog\/2009\/02\/02\/developing-a-strategic-project-position\/"},"modified":"2009-02-02T16:53:00","modified_gmt":"2009-02-02T16:53:00","slug":"developing-a-strategic-project-position","status":"publish","type":"post","link":"https:\/\/joapen.com\/blog\/2009\/02\/02\/developing-a-strategic-project-position\/","title":{"rendered":"Developing a strategic project position"},"content":{"rendered":"

\"\"<\/a> One of the exercise I learnt about this is issue is the use of echelons of Project Goals.<\/p>\n

Placing goals into echelons also helps determine the person in the client organization that can help you achieve multiple goals. Placing these echelons allow the people to see in which step of the project they are working.<\/div>\n
The echelons could be something like that:<\/div>\n
    \n
  1. Organizational<\/em> , focused on project goals,<\/li>\n
  2. External\/Customer<\/em> , focused on customer behavior,<\/li>\n
  3. Inter-departmental<\/em> , focused on inter-departmental performance,<\/li>\n
  4. Operational<\/em> , focused on functioning of a department,<\/li>\n
  5. Feature<\/em> , focused on system or process performance.<\/li>\n<\/ol>\n

    Developing a strategic project position<\/em><\/p>\n

    Look for links to higher echelons. Work with the client or your team to find the tasks that will place the goal into a higher echelon. You will then have a project that meets higher critical areas of performance and has greater value for the client.<\/p>\n

    The right alignment of these echelons is essential and it’s one of the things that will increase your odds of success. <\/p>\n

    It’s never too late to try to enchance the strategic position of your project.<\/p>\n

    If you find your project scope or goal does not correspond to those of your client, there are some alternatives you can try:<\/p>\n