Most IT leaders spend their first week as CIO in meet-and-greets. Mark Settle spent his time sitting in quarterly sales reviews in Minneapolis—where executives looked at him confused, asking why he'd want to be there. That confusion was the point. He was building field credibility that would matter when things got hard.
The VP-to-CIO transition isn't what people expect. As a VP, your CIO shields you from unhappy business partners—even if people complain about your data warehouse, the CIO knows nobody could run it better. As CIO, that protection disappears. You can't succeed unless all your peers are happy because the CEO and CFO constantly poll them for feedback on your performance. Company politics shifts from occasional management to your daily job.
Mark's credibility playbook centers on three moves: physically embedding in business operations (warehouse tours, field QSRs), identifying the one or two perception-shaping lieutenants in each department who influence their executive's view of IT, and recognizing that executives judge your seriousness by whether you show up—even when you learn nothing new. The tactic sounds soft until you realize these lieutenants shape whether your projects get funded.
What we cover:
- Losing hierarchical protection at C-level where the CIO no longer shields you from business partner complaints
- Building executive credibility by attending operational reviews where business leaders initially question why you're there
- Identifying perception-shaping lieutenants in each department who influence C-level executives' views of IT
- Avoiding the super user trap where IT builds edge-case customizations that average employees never use
- Meeting all executives during the interview process to create subliminal buy-in before day one
- Preventing your own IT team from poisoning your perspective on business partners through constant complaints
- Distinguishing AI's potential from automation ROI through bandwidth and information timing constraints that have always limited business processes
- Redesigning service desks from reactive ticket systems to proactive productivity loss prevention
- Justifying productivity investments using security's playbook for risk-based tool decisions
- Serving as gotcha consultant rather than policeman when business partners evaluate AI tools
- Rejecting the entry-level job death narrative by recognizing continuous role evolution with each technology wave
- Managing agent networks using API management principles around clumping versus splitting functionality
