I recently made a career switch after 30 years working in a University setting. I am now working as a consultant and executive recruiter (headhunter).
I find that many of my work projects follow a predictable cycle. In an executive search there would be several phases; for example 1) Launch search, 2) Source and shortlist candidates, 3) Conduct interviews, 4) Negotiate contract for client 5) Close file.
In my past work, I would typically list the project as "Hire for X role" or something to that effect. The problem now is that my project list is now filled with 10 similarly uninspired titled projects. When I look at the projects, it is hard to feel a "forward tug" because there are so many moving pieces and ebbs and flows to each project.
I'm thinking of converting each project to a standard template in my project support tool and then listing each project by it's phase or milestone. So "Hire for X role" becomes "Source and shortlist 6 candidates for X role" and "Complete Interviews for Y role". These seem more attractive and concise project descriptions.
As each are completed they are then replaced by the next phase. Does anyone else approach projects this way?
I know David says even sending a man to the moon starts with "Call Fred". But I assume in practice the Project would not be "Send man to the moon" but rather a series of projects such as "Recruit Astronauts" "Lunar Module is completed and tested" (as you can tell, I am not a NASA engineer).
I find that many of my work projects follow a predictable cycle. In an executive search there would be several phases; for example 1) Launch search, 2) Source and shortlist candidates, 3) Conduct interviews, 4) Negotiate contract for client 5) Close file.
In my past work, I would typically list the project as "Hire for X role" or something to that effect. The problem now is that my project list is now filled with 10 similarly uninspired titled projects. When I look at the projects, it is hard to feel a "forward tug" because there are so many moving pieces and ebbs and flows to each project.
I'm thinking of converting each project to a standard template in my project support tool and then listing each project by it's phase or milestone. So "Hire for X role" becomes "Source and shortlist 6 candidates for X role" and "Complete Interviews for Y role". These seem more attractive and concise project descriptions.
As each are completed they are then replaced by the next phase. Does anyone else approach projects this way?
I know David says even sending a man to the moon starts with "Call Fred". But I assume in practice the Project would not be "Send man to the moon" but rather a series of projects such as "Recruit Astronauts" "Lunar Module is completed and tested" (as you can tell, I am not a NASA engineer).