← CTRL-ALT-LEAD with David Hinson
Loading summary
Transcript1 lines
- [00:00]
A
Foreign. I'm David Hinson and I serve as Campus CIO for Bolden Networks for Higher Education. Welcome to Control Alt Lead when we talk about risk in higher ed, if we're even talking about risk at all, we usually start in the same place. Cybersecurity, phishing, ransomware, multi factor authentication. All important, all real. But if I'm honest, that's not the risk most senior IT leaders lose sleep over the most exposed. The most vulnerable risk is reputational. It's the moment when you see something coming. Fragility, exposure, accumulated technical debt. And the room either doesn't see it yet doesn't want to see it, or has something flashier on the agenda. It's the risk that isn't on your radar, and it's also the thing that actually shapes your reputation. Let's start with self advocacy, because most of us aren't wired for it. A lot of us were trained and raised as problem solvers. We were rewarded for fixing things without drama. Solve it, move on, and don't make it about you. Then you step into executive leadership and realize something unexpected and uncomfortable. If you don't explain your impact, it may as well not have happened. Because if modernization isn't connected to enrollment, resilience, student success, or business continuity, it simply becomes it upgraded some stuff. If registration runs clean because your team stabilized the network but no one understands what was avoided, it becomes business as usual. And business as usual rarely earns strategic investment, much less kudos or even thank you. So yes, you absolutely must frame the work. And not just with chest thumping or performative thought leadership, but with discipline. Here's what we did. Here's the institutional risk it reduced, here's what was enabled, and here's why it matters. Because if we don't define IT investment through a strategic lens, someone else will define it simply as overhead or worse. Now let's talk about misalignment. If you've sat in a cabinet meeting for more than a year, you've felt it. You're looking at aging core infrastructure. Cabinet is excited about generative AI because it's trending. You're trying to reduce your school's technical debt, and as always, the pressure is on to trim operating expenses. This fiscal year, you're thinking of five year risks, while others around the table are thinking in headlines, donor optics, or board conversations. That doesn't make them wrong, it just means they're optimizing for vastly different inputs, but hopefully the same outcomes. The real leadership work is translation. Saying that we need to replace core switches isn't persuasive. Instead, frame it. If these devices fail during peak registration, here's the enrollment exposure. Or say if we defer these needed change another 18 months, here's the consequence. If you can't connect your technology priorities to mission, revenue, resiliency, student experience, or institutional trust, it'll lose to whatever feels most urgent in the moment. Human systems under pressure maybe you argue your case effectively, clearly. Still, leadership decides to go in another direction with other priorities. That's when you find yourself in an entirely more personal risk calculation. Do I comply quietly? Do I document my concerns and just move forward? Or do I decide that the gap between my professional judgment and institutional direction is simply too wide for me to bridge? Know this Compliance isn't weak. We serve institutions with presidents, boards and cabinets carrying significant pressures that we don't and can't fully see or even understand. But silence without a record isn't leadership. Leadership can be something as simple as saying I understand the direction. Here are the risks as I see them, and here's how we can address them calmly, specifically and on the record. Not to protect your ego, but to protect the institution. If something fails later, the goal isn't to say, well, I warned you. It's ensuring the risk was knowingly assumed. And if you find yourself consistently suppressing concerns that cut against your core obligation to protect data, people and continuity, you have to ask a harder question. Is this truly a difference in tactics, or is it a fundamental difference in values between myself and my leadership? This matters more than we might care to admit it. Leaders sit in a uniquely exposed position. We see fragility, others don't. We understand systemic risk in ways that aren't intuitive to non technical peers. We also influence decisions that shape access to student success, business continuity, and community trust. So when pressure builds, I don't ask will this make the room comfortable? But I do ask Can I defend this decision a year from now? Can I explain it to my team without hedging? Can I stand behind it if it becomes public? And is it so misaligned with my values that there is a different conversation to be had? Those questions cut through politics. Doing the right thing won't always accelerate your career. Sometimes it makes you inconvenient or worst case scenario, redundant. But credibility compounds it matters. Perhaps it is the only thing that truly matters in the end. Our higher ed technology fishbowl is so much smaller than we realize. Reputations travel faster than resumes. Folks remember who protected their teams during reductions. They remember who refused shortcuts that compromise security and they remember who said we need to slow this down when momentum was outrunning governance. Remember, your title will change, but your reputation will always follow you. Let's be honest, there does exist a shallow version of self promotion. We all recognize it, but that's not the goal here. The goal is, however, to make invisible risk reduction visible. If your team prevented a security or privacy breach, say it. If your infrastructure strategy enabled continuity during disruption, then connect the dots. Not to inflate status, but rather to shape institutional understanding. If it is only seen when something breaks, it'll only be funded reactively. Leaders don't always understand upside, but they certainly all understand consequences. Strategic IT leadership requires narrative discipline. So when risk gets personal, and it absolutely will, I come back to three anchors. First, clarity. Know your principles before you're under pressure. Otherwise you'll default to the loudest voice in the room. Next, courage. Not theatrics, not grandstanding. Just the steady habit of saying the necessary thing. Finally, contribution. Does this serve students? Does this strengthen institutional resilience? Does this protect the people doing the work? If yes, you're probably aligned with your mandate. Risk in our world isn't just outages and breaches. It's the accumulation of small decisions that shape who you become as a leader. Let me repeat. Credibility compounds over time. One builds a career upon the back of their personal credibility. And credibility may be the most durable system you'll ever build. Thanks for listening. I'll see you soon. This week's episode uses an AI voice clone trained upon hours of my natural speaking voice. While the voice you hear today is cloned, the words, thoughts and ideas here are 100% my own.