Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Appropriate Proper Reasonable

Appropriate Proper Reasonable artwork

238: Thoughts of School Leaders and Technology

Sep 5, 202619 minAudio
ShareXLinkedInFacebookWhatsAppEmail

An AI-generated episode based on a human-created blog post: Thoughts of School Leaders and Technology

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

So I want you to imagine that you are boarding this massive state -of -the -art ocean liner. OK, I am picturing it. Right. And the navigation system uses this incredibly complex satellite triangulation. The engine room is just a marvel of automated engineering. Sounds you know incredibly efficient it is and absolutely everything from the deployment of the emergency lifeboats to Like the ambient lighting in the dining room is run by a highly sensitive centralized computer

network Which is great, but I mean that sounds like a system that requires a highly specialized crew to keep it from failing catastrophically Exactly, but then you look up at the bridge and you realize the captain the person who is entirely responsible for the direction of the ship and the lives of everyone on board only really knows how to use the ship intercom system. Oh, wow. That is a terrifying thought. Right. Like if the navigation screen just went blank or the network started flashing red, they wouldn't even know which button to push to reboot it. Yeah, you'd be stranded. But here's the thing. That

terrifying scenario isn't playing out at sea. It's actually happening every single day in our schools. It really is. And that is exactly what we are getting into today. We are taking a custom tailored deep dive into this really fascinating, highly reflective piece of writing. Yeah, it's a great source. It's from Dr. Gary L. Ackerman, published on his site Hack Science Education on June 30, 2026. The piece is titled Thoughts of School Leaders and Technology. And our mission today is to explore a pretty startling observation

he makes about who actually understands the digital infrastructure in our educational institutions. Because what makes this source material so compelling is that it comes from a place of deep, sustained observation over many years. Like this isn't just some reactionary hot take. Right. Absolutely. This is a real look at the people sitting at the very top of the educational food chain, you know, the principals and administrators. Yeah. And it evaluates their actual competence when it comes to the tools. that run their buildings. Okay, let's unpack this because the inciting

incident for this piece of writing is just incredibly relatable. Oh, for sure. The author is doing some digital spring cleaning, right? He's going through old files and he stumbles across a doctoral assignment he wrote years ago. Which we've all done. Right. And in this old paper, he had recorded some rather sharp observations about school principals, specifically noting their collective ignorance when it comes to technology. And, you know, finding an old paper is one thing. But the reality check really hits when he reads those old words in the context. of the present day. Yeah, he looks

at this old assertion and realizes it completely holds up. Exactly. I mean, the landscape of technology has evolved exponentially since his doctoral studies, right? But the leadership's grasp of it remains totally static. Wow. So nothing has changed at the top. Not really. He even explicitly notes that this isn't just a K -12 problem. He's seen the exact same dynamic play out in his post dissertation work with community colleges. Which fundamentally flips how we usually talk about this issue. I mean, whenever the phrase digital

divide gets thrown around, we always immediately think of the students. Right, the kids. Yeah, we think about the socioeconomic gap between kids who have high -speed fiber internet at home versus kids who are like trying to write an essay on a smartphone in a fast food parking lot. Which is a real issue, obviously. For sure. But the argument here is that there is no group of stakeholders where the digital divide is more pronounced than school principals. It's wild to think about. So what does this all mean? Are we saying the

people who most influence the theoretical and practical direction of a school are just entirely in the dark? I mean, the source material does not mince words about this. It points out that while there are a precious few who are genuine technology leaders and maybe a handful sitting in the murky middle, the vast majority are categorized as completely incompetent when it comes to making technology decisions. OK, but hold on. I have to push back on that just a little. Go for it. Is it actually fair to expect a school principal to be an IT systems architect, like? Their doctorate

is usually in educational leadership, right? Or human resources, or curriculum development. Not computer science? That's true. So shouldn't they just be focused on pedagogy and let the IT department handle the routers? Well, that is the traditional defense. But it relies on this totally outdated separation of powers that just doesn't exist anymore. That's so. You simply cannot separate pedagogy from IT infrastructure in a modern school. Principals are the primary stakeholders steering the ship. decide the budget, they set the pedagogical tone, and they define

the strategic priorities. Okay, that makes sense. Right. So if you are proving a million dollar curriculum overhaul that relies on synchronous cloud -based collaboration, but you have no concept of whether your building's current bandwidth can actually handle 1 ,500 simultaneous video uploads, well, your pedagogical vision is entirely useless. Oh yeah, the blind spot at the top just cascades down and breaks the system in the classroom. Exactly. Which naturally makes you wonder, like, If they have a blind spot that massive regarding something so fundamental to modern education,

how do they maintain their authority? That's the big question. Right. How do you run a tech -driven organization in 2026 if you don't actually understand the tech? You rely on a facade. Basically, you rely on the illusion of competence, which is maintained through what the text calls technology lip service. Ah, lip service. So they learn the buzzwords. Oh, absolutely. They know that to be taken seriously as a modern leader, they can't be seen as a Luddite running a 19th century schoolhouse. Right. So they passionately declare in board meetings that technology transforms teaching

and learning. Or they talk about synergistic digital platforms. Yes, all the corporates speak. But what's fascinating here is the massive gap between that grand rhetoric and their actual operational capability. It's a huge gap. Despite tossing around terms like 21st century skills, these leaders usually cannot articulate a specific actionable vision for technology in their building. And furthermore, they can't identify specific technology -rich practices that facilitate meaningful learning. Right. They know what the brochure

says, but they don't know the mechanics of how those tools actually help a student grasp a complex concept. The text lays it out perfectly. It says, if one of these principles were suddenly required to actually teach a classroom lesson using the very technology they champion, they would be absolutely lost. It is the ultimate do as I say, not as I do situation. Totally. But I want to clarify something important because there is a highly specific irony here. It's not that these administrators are incapable of turning on a

computer. No, not at all. They aren't writing internal memos by candlelight. Many principals actually use technology quite effectively for their own professional communication. Right. They're wizards at managing their calendars, firing off emails, and navigating digital HR reports. Which brings us back to your ocean liner metaphor. They know how to use the intercom to make announcements to the crew. Exactly. But that is personal one -to -one or one -to -many communication. It is a completely different universe than understanding enterprise level instructional

technology. Yeah, being highly efficient at achieving inbox zero does not mean you understand data privacy compliance. Or how an entire software ecosystem integrates with your student information system. I want you listening right now to just think about this in your own career. Have you ever had a manager who always had the sleekest new smartphone and was incredibly fast at replying to Slack messages. But the second you asked them to log into the specialized proprietary software your team actually relies on to do the daily

work, they froze up in a panic. We've all been there. It is a very specific modern leadership gap. You mistake personal digital fluency for enterprise operational knowledge. And in schools, this gap doesn't just impact what software the math department uses, it physically impacts the building. This is such a crucial expansion of the problem. When the general public thinks of school technology, they usually just picture laptops on desks or maybe an interactive smart board. But enterprise school tech is infinitely broader and deeper than just end -user devices.

Here's where it gets really interesting. The definition of what constitutes school technology encompasses incredibly expensive hidden infrastructure. Yes. We are talking about the backend systems that dictate all build -in -wide communication. We're talking about power over ethernet networks that keep the security cameras running. We're even talking about the centralized IP -based systems that keep the physical doors locked. to keep the students safe. Right. It is literally the nervous system of the entire physical plant. And that is exactly where this administrative

blind spot transforms from just an academic annoyance into a critical operational vulnerability. The text shares a very stark realization here. In all these years of observation, the author has yet to find any principal who truly understands the support, management and operation of these highly complex networks installed right inside their own buildings. So to go back to my pushback earlier, This is why they can't just leave it to the IT guy, because if a principal doesn't understand the network, they fundamentally do

not understand the physical security. of their own building. Exactly. Today, those are the exact same thing. Precisely. Principals have a largely unmet responsibility here. These infrastructure systems are incredibly hungry. They make massive demands on human resources. Meaning you need highly skilled, expensive engineers to maintain them, not just a teacher who happens to be good with computers. Right. And they make demands on the physical plant. They require dedicated climate controlled server rooms, battery backups,

miles of specialized cable. And critically, they make continuous compounding demands on monetary resources. Right, because enterprise tech is never a one -time purchase. No, it's software licensing, it's replacing access points every few years. If the leader doesn't understand the underlying machinery, they just cannot accurately budget for its survival. And that leads to situations where a well -meaning principal approves a massive purchase of, say, 500 new tablets because it looks great for the school's image. But they didn't allocate a single dollar to upgrade the

network bandwidth required for those 500 devices to simultaneously connect to the cloud. Exactly. So they basically bought 500 expensive paperweights, and the IT staff is left pulling their hair out trying to explain why the network keeps crashing. Which... Brings us to the root cause. Like, why does this specific glaring blind spot exist among these highly educated professionals? We're talking about people holding advanced degrees and doctorates in leadership. That's a great question. Where does this disconnect come from? Well, the source offers a fascinating demographic and historical

explanation based on direct career context. The origin stories. The text points out a specific trend. The principals observed were typically older than the author, specifically noting that within weeks of turning 40 at the time of the initial observation. So in the context of the timeline, this means they were beginning their teaching careers right around the late 90s or early 2000s. Right. But more importantly, it looks at what they were teaching. They overwhelmingly began their careers in fields like special education, language arts, or social studies. Now if we connect

this to the bigger picture, the late 90s and early 2000s were a highly fractured time for technology adoption in schools. Very much so. Those specific disciplines, special ed, language, social studies, traditionally adopted technology much later than the science and math departments. Like if you were a physics or calculus teacher in the year 2000, you were already deeply integrating graphing calculators, dialoguing probeware, and early simulation software into your daily practice. Yeah, you had to learn to troubleshoot on the fly. Technology was already a core component

of your instructional method. But if you were teaching history during that exact same era, your primary technology was a physical textbook, a chalkboard, and maybe, like, a television wheeled in on a metal cart once a month to watch a documentary. Exactly. This early career environment resulted in what the author describes as a long -term professional ignorance of technology as a professional tool. Right. These principles spent their formative professional years in an environment where technology was strictly supplemental or just entirely absent

from their core methodology. And because they never had to internalize technology as an essential non -negotiable professional tool early on, they never really built the mental framework for it. So now, decades later, as administrators, they operate in ways that are contrary to their own current performance standards. Because that foundational understanding was never laid. I think this is such a profoundly human psychological trait. Think about your very first job, whatever it was, listening out there. Think about the specific tools you used every single day to get that job

done. Yeah. Whether you realize it or not. Those early experiences secretly shape what you consider to be essential versus what you consider to be like an optional luxury in your current profession. It's so true. Like if you learn to build a house using a manual hammer, a pneumatic nail gun might always feel like a fancy add on in your mind rather than the baseline standard, even if you are now the CEO of the construction company. That is the exact psychological inertia at play here. They view enterprise technology as an add -on today because it was an add -on when they

were forming their professional identities 25 years ago. Okay, so we have this entrenched background. We have leaders who came up in non -tech heavy disciplines who are now in charge of buildings entirely reliant on complex tech infrastructure. Given this reality, what happens when a leader actually recognizes their own technological shortcomings? Because surely self -awareness has to kick in at some point when you are staring at a server rack you don't understand right. It does for some, and the text identifies a very clear fork

in the road here. When administrators inevitably realize they are out of their depth as technology leaders, they tend to take one of two distinct approaches. Let's start with the unsuccessful path, the dark side of leadership. What does that actually look like in practice? Well, the bad approach is rooted in a total refusal to seed control. These administrators are terrified of looking incompetent, so they forge ahead and make uninformed decisions. Or, perhaps worse, they make decisions without truly understanding the long -term implications of the choices in

front of them. Right. They might look at a vendor's glossy catalog. see some buzzwords that match their lip service rhetoric, and just sign a massive check for a closed ecosystem platform that doesn't integrate with a single piece of software the school already uses. Creating massive data silos and wasting incredible amounts of money all because they were too proud to admit they were just guessing. Exactly. They guess while projecting absolute certainty. That sounds like a nightmare for the IT department. It is. But there is a successful

path outlined for these leaders, and it requires something that can be very difficult for people in authority to embrace, which is humility. So what does the good approach entail? Administrators who take the successful path actively seek out and hire people who actually have the technical expertise to inform these decisions. And then crucially, they do one of two things. They either empower those knowledgeable people to make the technical decisions outright, or they take their advice incredibly seriously when signing the checks. They recognize that their job as a principal

is not to possess all the knowledge in the building, but to orchestrate the expertise of others. And the conclusion drawn from having work with both types of administrators is absolute. The ones who take that second path, the ones who empower others and rigorously follow expert advice, are vastly more successful in promoting effective, sustainable technology use in a school. This raises an important question about how we define leadership not just in education, but in any modern organization. Oh, absolutely. We often cling to this outdated, heroic model of leadership,

where the person at the top is supposed to be the smartest person in the room about every single operational detail. But this observation proves that true leadership isn't about omniscience. It is about having the rigorous self -awareness to recognize the boundaries of your own expertise. And the professional confidence to delegate authority when you are staring at a system you do not understand. It really is the difference between a boss and a true leader. A boss pretends to know how the network routing protocols work to save face. A leader hires a brilliant IT director, gives

them the budget they need, and just gets out of their way. As we wrap up this deep dive, let's just look at the incredible journey this source material took us on. It's been a ride. We started with a dusty doctoral assignment pulled from an old file which revealed a glaring persistent digital divide not among the students in the classroom, but at the very top of the organizational chart. We explored how leaders often mask this knowledge gap with buzzwords and lip service. While remaining dangerously blind to the massive hidden costs and complexities of the enterprise

networks they oversee, networks that control everything from curriculum delivery down to the physical safety locks on the doors. And we traced the root of this ignorance back to the early career demographics and psychological inertia of these principles. And finally, we saw that the only real path forward is a leadership model based on humility, delegation. Yeah. Now I want you to take a look around your own workplace this week. How does your organization handle the gap between executive decision -making and frontline technological reality? It's a great

thing to reflect on. Does your leadership empower the technical experts or are they just making uninformed expensive guesses from the bridge of the ship? And I will leave you with this final thought to mull over building on that stark reality. If technology now controls absolutely everything in a modern school building, from the specific data -driven software a child uses to learn to read, to the literal electronic locks on the physical doors that keep them safe from harm, and the people legally in charge of the building

do not inherently understand those systems, are we actually being led by educational visionaries? Or are we just crossing our fingers and hoping the system doesn't break while they figure out who to hire? It certainly makes you wonder who is actually steering the ship. Thank you so much for taking this deep dive with us today. We will see you next time.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. 250: Changing Vision of Technology Literacy

    Nov 14, 202619 minAudio

    An AI-created episode based on a human-composed blog post: Changing Vision of Technology Literacy

    Credit the people on this episode

  2. 249: The Inquiring Technologist: Why Great Solution Design Begins with "Too Many" Questions

    Oct 27, 20265 minAudio

    An AI-generated episode based on an AI-generated blog posts based on an old microblogging post: The Inquiring Technologist: Why Great Solution Design Begins with "Too Many" Questions

    Credit the people on this episode

  3. 248: Gathering Organizational Intelligence for Network Security

    Oct 25, 202622 minAudio

    A brief AI-generated episode based on a human-composed blog post: Gathering Organizational Intelligence for Network Security

    Credit the people on this episode

  4. 247: Models of Technology-Rich Teaching

    Oct 16, 202613 minAudio

    An AI-generated episode based on a human-composed blog post: Models of Technology-Rich Teaching

    Credit the people on this episode

  5. 246: Concepts of Operating Systems

    Oct 11, 202621 minAudio

    An AI-generated episode based on a blog post designed for students in a community college course. Concepts of Operating Systems

    Credit the people on this episode