For too long, the CIO was seen as the 'junior partner' in the C-suite—the nuts and bolts guy who kept everything running, but didn't have a lot of input into business strategy—and who, too often, wasn't taken terribly seriously by the other members of the executive team. Sure, the title was CIO. But too often, the CIO was still asked to get the AV running for a presentation—as though he or she was still a technical resource.
Happily, that's changed to a large degree…
In that article, I focus on the need for today's transformational CIO to be bilingual - to communicate value to ensure enthusiastic stakeholder buyin - and to further ensure that IT is recognized as a value center, and not a cost center.
You don't become a CIO / CTO / CISO / CDO without being able to deal with stress.
At every stage of a technology career - from early days "in the trenches" to a leadership position in the boardroom, you've dealt with high pressure, mission critical initiatives - and major decisions that impact every aspect of the enterprise.
We're all driven by metrics these days. Whether it's cost, revenue, increase in market share, streamlined operations, or KPIs, numbers often seem to tell the story of success or failure.
That's why Executive Resumes Writers - myself included - work to dig out the quantifiable achievements to demonstrate our client's success.
It's a rare week that I don't see a blog post or article with the 3, 5, 7, or 10 things that a job seeker MUST or MUST NOT include on a resume.
There's one big problem with articles like this. They go on the assumption that every career is the same, and that there's an simple template - a cookie cutter approach - that works for every career, every resume, every job seeker.
I've blogged on this topic before - but I think that it's important - do to the amount of misinformation you'll find on the web.
It's a rare week that I don't see a career "expert" suggesting customizing IT Resumes for every job you apply for.
In this series of blogs, I'm going to address the 3 most significant issues that I see in the IT resumes that cross my desk.
And I'll start at the top of the organization - with CIO and CTO resumes - and continue the series with IT Directors, IT Managers, and then address issues that I see in the resumes of "hands-on" IT professionals.
A client of mine - a senior IT leader - asked me for counsel of he was asked during the interview process if he had written his own IT resume.
It was an interesting - and, I think, an important - question.