WEBVTT 00:00:00.000 --> 00:00:02.859 Welcome to the Deep Dive. If you've ever sort 00:00:02.859 --> 00:00:05.040 of scratched your head wondering why getting 00:00:05.040 --> 00:00:08.220 new technology into schools feels, well, almost 00:00:08.220 --> 00:00:10.660 like a political campaign, today we're really 00:00:10.660 --> 00:00:13.539 diving into a big part of the answer, the Technology 00:00:13.539 --> 00:00:16.719 Steering Committee. Our mission here is to unpack 00:00:16.719 --> 00:00:19.699 what this group actually does, yes, but maybe 00:00:19.699 --> 00:00:23.260 more importantly, why it even exists and how 00:00:23.260 --> 00:00:26.500 it acts as this crucial operational firewall 00:00:26.500 --> 00:00:28.600 for school leaders. We're getting into the weeds 00:00:28.600 --> 00:00:31.440 of some pretty high stakes ed tech decision making. 00:00:31.679 --> 00:00:33.119 Yeah. And I think it's really necessary context 00:00:33.119 --> 00:00:34.859 to start with the administrator's perspective, 00:00:35.299 --> 00:00:37.140 the burden they carry. You know, these are licensed 00:00:37.140 --> 00:00:39.380 professionals hired by the school board. They 00:00:39.380 --> 00:00:41.500 have the ultimate responsibility for making policies 00:00:41.500 --> 00:00:43.820 and decisions happen across the district. But 00:00:43.820 --> 00:00:45.899 the sources we looked at make this really critical 00:00:45.899 --> 00:00:48.299 point. The effective administrators, they know 00:00:48.299 --> 00:00:50.399 they can't possibly have all the expertise needed 00:00:50.399 --> 00:00:52.859 to make every single tech decision wisely on 00:00:52.859 --> 00:00:55.380 their own. OK, so the person with the actual 00:00:55.380 --> 00:00:58.000 power, the one signing the check, knows they 00:00:58.000 --> 00:01:00.119 shouldn't be the only one deciding. But if that's 00:01:00.119 --> 00:01:02.820 true, why not just, you know, hand it off to 00:01:02.820 --> 00:01:04.980 the IT department, let them buy the stuff? Doesn't 00:01:04.980 --> 00:01:07.219 that just kick the political can down the road? 00:01:07.579 --> 00:01:10.260 Ah, but that's exactly where this steering committee 00:01:10.260 --> 00:01:13.439 really proves its worth. See, the administrator's 00:01:13.439 --> 00:01:16.180 job means constantly setting limits. Limits on 00:01:16.180 --> 00:01:18.340 what tech gets bought, limits on hiring more 00:01:18.340 --> 00:01:21.659 staff to support it and crucially resolving these 00:01:22.990 --> 00:01:25.310 disagreements when different groups want different 00:01:25.310 --> 00:01:27.909 things prioritized. If you've got teachers saying, 00:01:28.069 --> 00:01:30.430 we need X, IT saying, we need Y to support X, 00:01:30.489 --> 00:01:31.930 and the budget office saying, there's no money 00:01:31.930 --> 00:01:34.409 for either. Well, all those conflicts land right 00:01:34.409 --> 00:01:35.950 at the administrator's feet. Yeah, that sounds 00:01:35.950 --> 00:01:38.909 like a recipe for constant gridlock, a guaranteed 00:01:38.909 --> 00:01:41.230 conflict loop, like you said. So how do leaders 00:01:41.230 --> 00:01:43.510 actually navigate that? These really intense, 00:01:43.769 --> 00:01:45.849 often opposing demands without everything just 00:01:45.849 --> 00:01:48.870 grinding to a halt. Well, the main reason, the 00:01:48.870 --> 00:01:50.810 primary driver for even having this committee. 00:01:51.150 --> 00:01:54.209 is conflict reduction, or maybe conflict synthesis 00:01:54.209 --> 00:01:57.250 is a better term. You absolutely need a dedicated 00:01:57.250 --> 00:02:00.390 kind of safe space to hammer out the differences 00:02:00.390 --> 00:02:02.810 between what teachers are asking for, what the 00:02:02.810 --> 00:02:05.810 tech folks know is necessary for stability, and 00:02:05.810 --> 00:02:08.349 what the budget and existing policies actually 00:02:08.349 --> 00:02:10.930 allow, that structure, that process. That's really 00:02:10.930 --> 00:02:12.710 what we mean when we talk about the operational 00:02:12.710 --> 00:02:15.020 firewall. an operational firewall. I like that 00:02:15.020 --> 00:02:17.979 framing. So the committee sort of absorbs the 00:02:17.979 --> 00:02:20.199 political friction. It filters all those competing 00:02:20.199 --> 00:02:22.919 demands before they hit the administrator's desk, 00:02:23.340 --> 00:02:25.400 making sure whatever gets recommended is actually 00:02:25.400 --> 00:02:28.210 well. doable. Exactly. It forces these different, 00:02:28.530 --> 00:02:30.889 often conflicting viewpoints to wrestle with 00:02:30.889 --> 00:02:32.849 each other and find some common ground, some 00:02:32.849 --> 00:02:34.830 kind of implementable solution. OK, so let's 00:02:34.830 --> 00:02:36.229 talk about who's actually on this committee, 00:02:36.389 --> 00:02:39.330 who gets a seat at that table. Our sources really 00:02:39.330 --> 00:02:41.710 emphasize it needs to be a diverse group, you 00:02:41.710 --> 00:02:43.330 know, representing different parts of the school 00:02:43.330 --> 00:02:46.270 community. But what specific qualities are they 00:02:46.270 --> 00:02:48.810 looking for in a member beyond just being, say, 00:02:49.009 --> 00:02:51.740 a teacher or an IT person? Yeah, good question. 00:02:51.800 --> 00:02:55.560 It's really about vision and operational intelligence. 00:02:56.460 --> 00:02:58.500 Committee members ideally are picked because 00:02:58.500 --> 00:03:01.340 they hold a strong kind of overarching vision 00:03:01.340 --> 00:03:03.659 for the whole organization, not just their own 00:03:03.659 --> 00:03:05.900 little corner of it. They're expected to have 00:03:05.900 --> 00:03:08.080 a pretty broad understanding of how the entire 00:03:08.080 --> 00:03:10.759 school or district operates. Because if you only 00:03:10.759 --> 00:03:13.080 see your piece of the puzzle, you can't really 00:03:13.080 --> 00:03:15.810 negotiate effectively for the whole system. Right. 00:03:15.849 --> 00:03:17.710 So they're not just showing up with their department's 00:03:17.710 --> 00:03:19.849 wish list. They need to be genuinely interested 00:03:19.849 --> 00:03:23.009 in finding technologies that plug real gaps, 00:03:23.469 --> 00:03:26.289 whether those are gaps in teaching or gaps in 00:03:26.289 --> 00:03:28.830 how the whole place runs. They're basically solution 00:03:28.830 --> 00:03:31.370 finders. And that shared vision. or at least 00:03:31.370 --> 00:03:34.189 the process of building it is what makes the 00:03:34.189 --> 00:03:36.409 committee potentially work. It's that shared 00:03:36.409 --> 00:03:38.729 space where teachers, technicians, administrators, 00:03:39.090 --> 00:03:41.270 maybe even parents or students sometimes actually 00:03:41.270 --> 00:03:44.169 sit down together. They hash out solutions that 00:03:44.169 --> 00:03:46.050 hopefully support everyone or at least balance 00:03:46.050 --> 00:03:48.310 the needs. That's where the alignment has a chance 00:03:48.310 --> 00:03:51.750 to start. That alignment piece leads us right 00:03:51.750 --> 00:03:54.129 into the core tension, doesn't it? Because the 00:03:54.129 --> 00:03:55.590 requirements from these different groups can 00:03:55.590 --> 00:03:58.680 seem, well, fundamentally at odds sometimes. 00:03:59.280 --> 00:04:01.319 Let's break down those demands. What are teachers, 00:04:01.479 --> 00:04:03.400 the folks actually using this stuff in the classroom, 00:04:03.560 --> 00:04:06.240 what are they looking for? Teachers, yeah, they 00:04:06.240 --> 00:04:09.639 have some baseline needs. Things that are pretty 00:04:09.639 --> 00:04:11.939 much non -negotiable if you want them to actually 00:04:11.939 --> 00:04:14.620 use the tech effectively. First and foremost, 00:04:14.919 --> 00:04:17.740 it absolutely has to be secure. It has to be 00:04:17.740 --> 00:04:19.519 reliable. It has to be robust. I mean, think 00:04:19.519 --> 00:04:22.740 about it. If the system is always crashing, or 00:04:22.740 --> 00:04:25.079 if it's vulnerable and puts student data at risk, 00:04:25.600 --> 00:04:28.000 it's worse than useless. It's actively harmful. 00:04:28.279 --> 00:04:31.259 Totally. Reliability is table stakes. But that's 00:04:31.259 --> 00:04:33.600 just the start, right? Teachers also need the 00:04:33.600 --> 00:04:36.180 tech to let them and their students do specific 00:04:36.180 --> 00:04:38.319 things, tasks that are actually necessary for 00:04:38.319 --> 00:04:41.060 the curriculum, for learning, a rock -solid system 00:04:41.060 --> 00:04:43.180 that doesn't actually help. teach or learn anything 00:04:43.180 --> 00:04:45.660 useful that's just, you know, expensive furniture. 00:04:46.180 --> 00:04:48.500 Exactly. Now, let's flip the coin. Look at the 00:04:48.500 --> 00:04:50.740 IT professionals. They're also driven by the 00:04:50.740 --> 00:04:52.860 same core mission supporting teaching and learning, 00:04:52.920 --> 00:04:55.439 but they absolutely view the world through a 00:04:55.439 --> 00:04:59.560 different lens, a lens of longevity, stability, 00:05:00.160 --> 00:05:02.540 manageability. They must insist that any new 00:05:02.540 --> 00:05:05.259 system aligns with good sound principles of IT 00:05:05.259 --> 00:05:07.459 management. This is where they provide that crucial 00:05:07.459 --> 00:05:09.879 reality check. And that reality check often boils 00:05:09.879 --> 00:05:12.790 down to things like capacity and expertise, doesn't 00:05:12.790 --> 00:05:15.209 it? Can we actually handle this thing? Precisely. 00:05:15.430 --> 00:05:18.269 The IT team has to look at it and say, OK, can 00:05:18.269 --> 00:05:20.350 we actually support this new system with the 00:05:20.350 --> 00:05:22.930 people and the skills we have right now? It's 00:05:22.930 --> 00:05:24.990 just not sustainable organizationally to bring 00:05:24.990 --> 00:05:27.550 in some super specialized piece of software if 00:05:27.550 --> 00:05:29.389 you don't have anyone on staff who knows how 00:05:29.389 --> 00:05:31.959 to. fix it, update it, keep it secure five years 00:05:31.959 --> 00:05:34.319 down the line. That really clarifies the conflict. 00:05:34.779 --> 00:05:36.720 We used that car analogy before, and it fits 00:05:36.720 --> 00:05:38.779 perfectly here, I think. The teacher might want 00:05:38.779 --> 00:05:41.339 the fastest, flashiest sports car, you know, 00:05:41.540 --> 00:05:43.639 packed with digital features to solve an immediate 00:05:43.639 --> 00:05:47.040 need they have, speed, performance. But the IT 00:05:47.040 --> 00:05:49.319 team, they have to step in and say, hold on, 00:05:49.639 --> 00:05:52.019 we need to buy a reliable fleet vehicle, something 00:05:52.019 --> 00:05:54.319 the existing mechanics in our garage actually 00:05:54.319 --> 00:05:56.740 know how to fix, something we can afford to maintain, 00:05:56.899 --> 00:05:59.500 get parts for easily. Otherwise you end up hiring 00:05:59.500 --> 00:06:02.019 three new specialists in panics you can't afford, 00:06:02.379 --> 00:06:05.060 or the car sits broken in the garage. It's that 00:06:05.060 --> 00:06:09.339 constant tug of war desired function versus operational 00:06:09.339 --> 00:06:11.879 reality. And if you don't find a way to reconcile 00:06:11.879 --> 00:06:14.060 that tension, the whole initiative is likely 00:06:14.060 --> 00:06:16.800 to fail. It just fizzles out or becomes a constant 00:06:16.800 --> 00:06:18.579 headache. This is really where the committee 00:06:18.579 --> 00:06:20.899 does its hardest work. The real work is that 00:06:20.899 --> 00:06:22.879 simultaneous negotiation of what our sources 00:06:22.879 --> 00:06:26.040 call the DCI triad. That's appropriate design, 00:06:26.579 --> 00:06:29.000 proper configuration, and reasonable implementation. 00:06:29.379 --> 00:06:31.720 OK. Let's pause on that DCI triad for a second 00:06:31.720 --> 00:06:33.720 because that sounds like the core mechanism for 00:06:33.720 --> 00:06:36.439 getting it right. How does getting one of those 00:06:36.439 --> 00:06:38.839 wrong mess up the others? Can you give an example? 00:06:39.100 --> 00:06:41.839 Sure. Think about it like this. You can have 00:06:41.839 --> 00:06:44.620 a system that's, let's say, reasonably implemented, 00:06:44.819 --> 00:06:47.600 meaning you did great training, the rollout seemed 00:06:47.600 --> 00:06:50.920 smooth. But if the underlying design of the software 00:06:50.920 --> 00:06:53.899 itself is maybe just not built for a large school 00:06:53.899 --> 00:06:56.199 district, perhaps it can't handle thousands of 00:06:56.199 --> 00:06:59.800 kids logging in at once, then your smooth implementation 00:06:59.800 --> 00:07:02.519 doesn't matter. The system falls over. Ah, OK. 00:07:02.879 --> 00:07:05.300 And configuration, where does that fit? Configuration 00:07:05.300 --> 00:07:07.649 is like the crucial link in the chain. You might 00:07:07.649 --> 00:07:09.930 pick the best design system out there, theoretically 00:07:09.930 --> 00:07:13.029 perfect. But if your IT team configures it poorly, 00:07:13.490 --> 00:07:15.490 maybe they set up the security permissions wrong, 00:07:15.790 --> 00:07:17.750 or it doesn't integrate properly with existing 00:07:17.750 --> 00:07:20.889 student databases, then the implementation, from 00:07:20.889 --> 00:07:23.370 the teacher's perspective, is going to feel chaotic 00:07:23.370 --> 00:07:26.910 and broken. So the committee's job is to constantly 00:07:26.910 --> 00:07:30.269 check that all three design, configuration, implementation 00:07:30.269 --> 00:07:32.990 are staying aligned throughout the whole process 00:07:32.990 --> 00:07:35.120 before the final recommendation goes up. Which 00:07:35.120 --> 00:07:37.000 really means they aren't just picking a product 00:07:37.000 --> 00:07:39.540 off a shelf. They're vetting and approving a 00:07:39.540 --> 00:07:41.740 whole synchronized process for weaving that product 00:07:41.740 --> 00:07:45.600 into the school's daily life. Okay, so we understand 00:07:45.600 --> 00:07:48.040 the players. We understand the intense negotiation 00:07:48.040 --> 00:07:50.879 that has to happen with this DCI triad. Now for 00:07:50.879 --> 00:07:53.920 the payoff, right? What does success actually 00:07:53.920 --> 00:07:56.360 look like when a system improvement comes out 00:07:56.360 --> 00:07:58.579 of this process? If they manage to nail that 00:07:58.579 --> 00:08:01.879 DCI negotiation, what are the sort of ultimate 00:08:01.879 --> 00:08:05.689 criteria? for a winning, truly sustainable outcome. 00:08:06.189 --> 00:08:08.389 Right. The ultimate success, according to the 00:08:08.389 --> 00:08:10.310 framework in our sources, is defined by what 00:08:10.310 --> 00:08:13.230 we can call the MPS framework. Any resulting 00:08:13.230 --> 00:08:15.910 system, any improvement must be manageable, predictable, 00:08:16.089 --> 00:08:18.569 and sustainable. If it fundamentally fails on 00:08:18.569 --> 00:08:20.930 any one of those three, then the core organizational 00:08:20.930 --> 00:08:23.069 challenge hasn't actually been solved, even if 00:08:23.069 --> 00:08:24.750 the tech looks cool. Okay, let's break those 00:08:24.750 --> 00:08:27.629 down. Manageable. What does that mean specifically 00:08:27.629 --> 00:08:30.189 in a school context? Is it just about IT workload? 00:08:30.629 --> 00:08:33.250 Manageable definitely includes workload. but 00:08:33.250 --> 00:08:36.529 it's broader. It refers to the overall operational 00:08:36.529 --> 00:08:40.149 burden. Crucially, it has to be within the existing 00:08:40.149 --> 00:08:43.330 technological capacity and expertise of the organization. 00:08:44.070 --> 00:08:46.509 So for instance, if your IT team is really skilled 00:08:46.509 --> 00:08:49.110 and certified in, say, a Windows environment, 00:08:49.730 --> 00:08:51.789 suddenly rolling out a critical new system that 00:08:51.789 --> 00:08:54.809 runs only on a niche Linux platform, That might 00:08:54.809 --> 00:08:57.070 not be manageable. It immediately strains your 00:08:57.070 --> 00:08:58.990 existing capacity, could lead to staff burnout, 00:08:59.529 --> 00:09:02.230 and almost guarantees more system downtime because 00:09:02.230 --> 00:09:04.649 nobody knows it well enough yet. Got it. That's 00:09:04.649 --> 00:09:07.590 capacity. Predictable, though. Yeah. That sounds 00:09:07.590 --> 00:09:09.269 like it speaks much more directly to the user 00:09:09.269 --> 00:09:11.149 experience, the teachers. It absolutely does. 00:09:11.450 --> 00:09:13.710 Predictability is just critical for teacher trust, 00:09:14.289 --> 00:09:16.789 for avoiding chaos in the classroom. If teachers 00:09:16.789 --> 00:09:19.190 can't reliably predict how the system will perform 00:09:19.190 --> 00:09:21.539 day to day, If it works perfectly on Tuesday, 00:09:21.740 --> 00:09:23.820 but then constantly glitches after a forced update 00:09:23.820 --> 00:09:26.320 on Wednesday morning, it completely disrupts 00:09:26.320 --> 00:09:28.840 teaching. And frankly, it just encourages teachers 00:09:28.840 --> 00:09:31.500 to give up and find workarounds. Predictability 00:09:31.500 --> 00:09:33.899 means it works reliably over time without nasty 00:09:33.899 --> 00:09:36.519 surprises. Makes total sense. And the last one, 00:09:36.720 --> 00:09:39.379 sustainable. That sounds like the long -term 00:09:39.379 --> 00:09:42.559 budget reality check kicking in. It definitely 00:09:42.559 --> 00:09:45.720 covers finance, but also scale. Sustainability 00:09:45.720 --> 00:09:48.970 essentially means Can we actually do this at 00:09:48.970 --> 00:09:51.610 the necessary scale across the whole district 00:09:51.610 --> 00:09:54.970 or school for the long haul? We're talking a 00:09:54.970 --> 00:09:57.450 minimum three to five year window both financially 00:09:57.450 --> 00:09:59.870 and technically. You might manage to run an amazing 00:09:59.870 --> 00:10:02.090 expensive pilot program in three classrooms for 00:10:02.090 --> 00:10:04.110 one year with a special grant, but if there's 00:10:04.110 --> 00:10:06.149 no realistic plan to scale that district -wide 00:10:06.149 --> 00:10:08.490 for five years without needing massive new budget 00:10:08.490 --> 00:10:11.110 lines every year or hiring a dozen new specialists 00:10:11.110 --> 00:10:13.789 you don't have, well then it simply wasn't a 00:10:13.789 --> 00:10:16.220 sustainable solution from the start. Wow, okay. 00:10:16.500 --> 00:10:18.860 That MPS framework, manageable, predictable, 00:10:19.340 --> 00:10:21.580 sustainable, ties it all together really nicely. 00:10:21.899 --> 00:10:24.039 It shows the committee's success isn't just about 00:10:24.039 --> 00:10:25.820 picking the tool with the fanciest features. 00:10:25.940 --> 00:10:28.539 Not at all. It's really about making sure that 00:10:28.539 --> 00:10:31.659 tool, however great it seems, actually fits the 00:10:31.659 --> 00:10:34.960 school's operational reality. The capacity, the 00:10:34.960 --> 00:10:36.980 need for predictability, the long -term scale. 00:10:37.100 --> 00:10:40.139 They're essentially acting as guardians of realistic 00:10:40.139 --> 00:10:43.019 long -term effectiveness, protecting the administrator, 00:10:43.220 --> 00:10:45.690 and ultimately, protecting instructional time. 00:10:45.950 --> 00:10:48.490 That really is the ultimate aim, yes. This whole 00:10:48.490 --> 00:10:50.570 structure just confirms that EdTech decisions 00:10:50.570 --> 00:10:53.870 aren't simple purchases. They are complex organizational 00:10:53.870 --> 00:10:56.250 challenges. And effective administrators handle 00:10:56.250 --> 00:10:58.669 that complexity by deliberately setting up a 00:10:58.669 --> 00:11:01.230 process, the committee, to synthesize these diverse, 00:11:01.690 --> 00:11:03.470 often conflicting perspectives from teachers, 00:11:03.649 --> 00:11:06.009 from tech teams, from finance folks, to arrive 00:11:06.009 --> 00:11:07.909 at conclusions that are actually implementable 00:11:07.909 --> 00:11:10.529 and crucially sustainable. That's the key for 00:11:10.529 --> 00:11:13.090 the long haul. It genuinely reframes how you 00:11:13.090 --> 00:11:15.049 think about school technology choices, doesn't 00:11:15.049 --> 00:11:17.210 it? It shifts it from just being about features 00:11:17.210 --> 00:11:20.389 to being about, well, smart organizational governance. 00:11:20.950 --> 00:11:23.669 So if that core challenge is really about balancing 00:11:23.669 --> 00:11:26.250 what people want with what the organization can 00:11:26.250 --> 00:11:29.350 realistically manage, predict and sustain. Here's 00:11:29.350 --> 00:11:31.730 a final thought for you listening. What specific 00:11:31.730 --> 00:11:33.990 organizational metrics should a school actually 00:11:33.990 --> 00:11:36.070 track? Maybe things like teacher retention related 00:11:36.070 --> 00:11:39.309 to tech frustration, or maybe unplanned IT maintenance 00:11:39.309 --> 00:11:42.230 costs, or even actual classroom usage rates beyond 00:11:42.230 --> 00:11:44.490 the first month to know if its steering committee 00:11:44.490 --> 00:11:47.230 is truly succeeding. Beyond just keeping the 00:11:47.230 --> 00:11:49.809 peace and reducing visible conflict. Something 00:11:49.809 --> 00:11:52.009 to consider based on the framework we've explored 00:11:52.009 --> 00:11:52.370 today.