It's for the position of IT Director.
When I was younger (oh so much younger than today) I had the technically bloated, list every skill under the sun, I am desperate resume. But after having my time wasted (and wasting others time) going in for interviews that I wasn't particularly skilled or interested in, I cut my resume back to what I wanted to do.
But then I was taught the next extension to that, you write your resume for the role that you want. So I have my manager resume, consultant resume, and engineer resume.
But if you do want to pass the key word search, then drop them into page 3 on the resume. No-one will read it, but it will be found.
As for not being able to "connect everything an IT professional has done to business value", that just highlights why IT professionals aren't sales professionals. If providing the infrastructure that allows a business to reliably and efficiently operate isn't of business value, then not much is.
Google even acknowledges that allowing their employees spare time to do whatever is potentially beneficial to the company.
Many companies acknowledge that a gym or basketball court improves the business.
So business value could be a little vague, but it really is just a matter of making the things we do matter to the people making the decisions.
Having said that, I can't work out why some companies implement certain systems (oh, the temptation to name names). So Jennifer may be right - there are some monumental stuff ups that just shouldn't go on a resume.
Keep Up with TechRepublic