I'm looking for suggestions from other IT folks on how to identify accomplishments of IT work.
I've been listening to the interviewing podcasts and its hitting me more and more that it is very difficult to document accomplishments of IT work. I believe that a good part of this is the nature of IT and the fact that in the past I have rarely been required to link project outcomes directly to results. There is a difference between doing things and accomplishments.
In IT projects I've done, the objective has been completing the project requirements correctly / on time / on budget. But doing that is really a requirement; every person who did the same project would have the same objective. The standard is very high and just meeting the requirement takes an enormous amount of work, none of which (IMHO) can be qualified as an accomplishment. Additionally, the goal is to exactly arrive at the specification, no more, no less.
So, I struggle with my resume and I'm certain that I'm at the top of the majority whose resume stinks. I feel like I'm trying to show how I've been distinctive in a work system that requires conformance.