The director-to-VP jump breaks most technology leaders. Rusty Atkinson saw it coming. After realizing he was an above-average engineer but never the head geek in the room, he made a calculated bet: leadership ability would take him further than technical depth. Twenty years later, as VP of Technology at Clearway Health and author of "The Integrity Edge," he's built a repeatable framework for climbing to the C-suite. His approach centers on what he calls the "integrity edge" - the measurable engagement, loyalty, and innovation you earn when teams know they're protected and trusted. But getting there required learning that boardrooms don't care about technology, that your VP boss might steal your ideas, and that the firmware upgrade that bricked production was ultimately your failure, not the engineer's who forgot to check the backup.

Topics discussed:

• Defining the "integrity edge" as measurable team outcomes from trust-based leadership

• Why the director promotion is the hardest transition where technical skills stop mattering

• Translating C-suite peer objectives into technology actions rather than pitching solutions

• Embedding in operational contexts like sales calls to identify friction points before they're articulated

• Applying extreme ownership where backup verification failures roll up to leadership, not just the engineer

• Starting career planning with your final role and reverse-engineering required capabilities

• Coaching through personal "why" discovery to convert disconnected actions into character-driven decisions

• Treating AI like cloud in 2008: transformative potential undermined by solution-first thinking

Kumud Kokal's career path defied his CPA father's expectations, pivoting from accounting to software engineering during the Internet's early days. Over 25 years, he built technical fluency across wildly different business models, from Intuit's consumer finance to Airbnb's hospitality platform to FBN's agriculture technology, before landing as CIO at Kiteworks. His framework for career decisions remains consistent: evaluate opportunities through the lens of "how hard can this be?" At FBN, that question led him to dairy farms in Minnesota, watching a fifth-generation farmer track 400 head of cattle producing 29,000 gallons of milk daily by sight alone. The experience taught him that agriculture wasn't a business to customers; it was identity. That perspective shift defines his approach to IT leadership.

Topics discussed:

• Structuring a personal board of directors with domain-specific advisors for compensation strategy, technical architecture, and industry navigation

• Running the "inside out and outside in" assessment framework in the first 90 days to surface misalignment between internal team perspective and stakeholder reality

• Defining IT's mission, vision, and strategy as organizational constitution, moving teams from reactive "whack-a-mole" mode to strategic alignment

• Building the "Stevenson family" of AI agents with distinct roles (Caroline for HR/IT, Natalie for product support) using Microsoft Teams integration and connected infrastructure systems

• Navigating the VP-to-CIO transition by learning to speak peer language across finance, legal, and business unit leadership

• Applying Intuit's "follow me home" observation methodology, catching critical UX patterns like extension fields in phone numbers that UAT testing missed

• Establishing shared-responsibility AI development model where business units propose solutions and IT provides funding and technical enablement

• Reframing technology decisions as a three-way evaluation: human execution, traditional automation, or agent deployment

Bob Genchi's seven years at Gap Inc. became his "postgraduate education" in IT. He watched a major IBM outsourcing initiative that initially promised efficiency turn into a morale-destroying productivity sink. The experience taught him to prioritize what traditional metrics miss entirely: user sentiment and organizational trust. Now as CIO/CISO at Scale Venture Partners, he advises early-stage portfolio companies on scaling IT operations while bringing that hard-won perspective on what actually works versus what looks good in a business case.

Topics discussed:

Noni Azhar turned a consulting career into C-suite leadership by mastering what most IT leaders miss: the skill of making stakeholders believe your solution was their idea. As CIO at ProService Hawaii, he shares the frameworks that carried him from technical consulting through each inflection point—IC to manager, director to VP, VP to CIO—and why self-compassion during those transitions separates leaders who scale from those who stall.

Topics discussed:

Trevor Gregg supervises county IT operations and runs Columbia College's Google-funded IT pre-apprenticeship program. When he inherited a service desk with morale in the basement, he did something most IT leaders never consider: he brought a county board supervisor directly to his team—not to announce fixes, but to listen without offering solutions.

That single move solved what performance reviews and skip-levels couldn't touch. His team needed to feel heard before they could move forward. The insight applies directly to IT leadership: when morale craters, your instinct to problem-solve actively prevents recovery. Your team already knows the technical fixes. They need you to facilitate the conversation, not dominate it.

Trevor applies this same principle teaching students ranging from concurrent high school enrollment to career-switchers in their 50s. His pre-apprenticeship lab strips away the illusion that IT careers are built on technical prowess alone. Students construct the entire infrastructure from raw cable and blank machines. When one team's DHCP configuration blocks another's progress, collaboration isn't optional—it's survival. He's deliberately architected this interdependency because the failure mode for technical people isn't debugging, it's asking for help.

The SCARF framework he teaches addresses the stakeholder problem most IT leaders learn through painful failure: your architecture dies if your audience's threat response activates during the pitch. Status, Certainty, Autonomy, Relatedness, Fairness—these aren't soft skills. They're the variables that determine whether your proposal gets funded or archived. Trevor trains students to structure conversations that bypass defensive reactions, a skill most Directors only master after years of rejected proposals.

His non-traditional path—astronomy degree, NASA Kepler telescope research, family pizza business, bipolar diagnosis—built leadership instincts that traditional IT career paths don't develop. Learning Linux through astronomy research created deeper technical foundations than boot camps provide. Managing pizza shop crews taught him servant leadership before he knew the term existed. Completing his degree while managing mental health struggles taught him that accomplishment becomes addictive once you prove you can summit something that looked impossible.

Topics discussed:

"How many IAM tickets do you close a day?" When Tom Quinn asked his team, the answer was "a lot." That non-answer cost them six hours just to compile basic metrics. Two weeks later: four hours. Two more weeks: one hour. Then real-time. That progression unlocked the insight that 80% of tickets came from one call center with high turnover — leading to automated role-based provisioning that saved 20 hours per week.

Quinn's measurement-first approach at T. Rowe Price proves you can't automate what you don't measure, but more importantly, the act of measuring itself becomes the first automation win. His team didn't start with the perfect metric—they started with any metric they could get their hands on, then systematically reduced the friction of collecting it. That cultural shift from "we handle a lot" to "here's the exact number and where it comes from" created the foundation for every operational improvement that followed.

The conversation also covers Quinn's listening tour methodology for new leadership roles, where asking "if there's anything at all that isn't working — doesn't have to involve my team — I want to know" surfaces the budget constraints and cross-functional friction that shape what's actually achievable. His reference points range from Navy close-quarter operations to early NASA's learning culture to Kimberly Clark's decision to sell their Wisconsin mills and pivot from low-margin cardboard to high-margin paper products.

Topics discussed:

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:

Most directors think the CIO job is about making bigger technical decisions. Karl Mosgofian discovered it's about learning an entirely different language: investment language. When your "perfect" solution reaches the CEO, they're choosing between 30 competing priorities and can fund maybe 6. His brutal mentor with the red pen taught him the empathy framework: if you can't see your presentation through the CEO's eyes, you're dead in the water.

Karl's journey from programmer to CIO at Gainsight spanned over three decades in IT leadership, transforming IT from support function into growth catalyst. His networking evolution went from awkward forced lunches to essential peer relationships he can't do the job without. He built deep business fluency without an MBA by applying technical curiosity to business domains.

What we cover: