As you will undoubtedly see, I continue to fuss with the format of the blog. I've added a couple of blogs that I follow on the right side of the page, and links that I think can be especially useful. The links will probably change from time to time to stay fresh.
The group on Wednesday has been working elevator pitches for a couple of weeks now and we actually read examples to each other yesterday. My last post had our definition, I think there's more to it. A clear tight elevator pitch becomes the organizing subject for a resume. Everyone over the age of about 20 has more experience than can possibly be captured in writing, some of it relates to work, and some of it has nothing to do with it. The older we get, the more work experience we have making it even more difficult to choose and edit what we include on a resume.
For example, I've been in IT for more than 25 years. In that time, I've been a developer, analyst, resource manager, director, etc, etc. Just describing each role would take at least a couple pages, before I got to experience that is specific to me. All that will do is bore everyone who sees it and threaten an additional forest every time it's printed. Not a useful exercise.
My elevator pitch for jobs in IT is, "Every organization struggles with getting what they need from their IT department at a price they can afford. I've been building teams that deliver on this for more than eight years and would love to have the opportunity to continue." This tells me what events and roles and accomplishments to include. Time as a dev? it's a footnote. Time as an architect? it's abreviated, but bigger than the dev stuff. What I focus on is experience where I have built teams and the team has delivered.
The point here is not that mine is the only kind of pitch, but that by being clear with my pitch, I can write a cooherent resume that supports my goals and my pitch. If I have other parallel goals, then I can write other pitches and focus the experience in my resume around those goals and that pitch.