All posts by Matt Brady

Matt Brady has been creating digital ecosystems that organize, inform and inspire for two decades. He writes as a curatorial journalist- connecting related stories across disciplines often beyond “Education”- to examine and understand educational leadership in a more adaptive and predictive way.

Does EdTech Coaching Work?

Is instructional tech coaching actually working in K-12, or are we mainly treating symptoms of a broken system? 

I was invited on the EDU Coach Collective podcast to discuss my research @ “tech coaching” and it’s troubling relationship with value delivery in K-12 schools.

Pod: https://ow.ly/6Q5850YyBFX
Transcript: t.ly/-TJqs


TRANSCRIPT:

TLDR Summary:

Reclaiming Brain Cycles for All Stakeholders & Building Structural Synergy

  • The “Leaf Blower” Problem: Many EdTech initiatives create “digital noise”—simply moving tasks from paper to screen—without actually simplifying anyone’s workload or improving student outcomes.
  • From Compliance to Commitment: Success isn’t about forcing teachers to use new tools; it’s about designing “Computationally Kind” systems that work so well that teachers want to commit to them.
  • The “Yak Shaving” Metric: We need to move away from measuring “how many trainings” were held and start measuring how many redundant, irrelevant steps (the “Yak Shave”) have been removed from a teacher’s daily workflow.
  • Collaborative Infrastructure: Coaches are uniquely positioned to act as “Curatorial Journalists,” bridging the gap between Admin mandates, IT constraints, and Teacher needs to ensure the “engine is actually connected to the transmission”.
  • Building Capacity, Not Dependency: The goal of the Edtech Synergist Protocol is to move away from “heroic” one-on-one fixes and toward a scalable system that builds teacher efficacy and school-wide wellness.
  • Proactive System Design: By listening to teachers’ actual goals and testing workflows ahead of time, we can provide “headlights” for leadership to see where friction points are costing the district time and money.

Podcast Transcript: The EDU Coach Collective

Celine Thomas: Calling all instructional leaders, curriculum innovators, and dedicated classroom coaches—or whatever they call you! I’m Celine.

Katie Ritter: And I’m Katie. As coaches, we know the path to school-wide growth can feel isolating, with big responsibilities resting squarely on your shoulders.

Celine Thomas: That’s why we built this space. We’re opening the conversation to connect, collaborate, and bring a unified voice to the world of instructional coaching.

Katie Ritter: Elevate your practice with strategies that work.

Celine Thomas: And finally feel like you have a whole collective cheering you on. So let’s dive into this conversation!

Celine Thomas: Welcome back to the EDU Coach Collective, the podcast dedicated to empowering instructional leaders to drive transformative change. We often talk about the latest strategies and models, but today, we’re pulling back the curtain on a fundamental question: Does coaching actually work? And more importantly, does the system we work in allow it to? So today we have Matt Brady—we’re so excited to have Matt! He is a learning community builder, a digital innovation lead, and project change manager who worked in a US public school and a private international school for almost two decades as a teacher, a digital learning coach, and an administrator. Most recently, he led digital transformations for international school communities in Germany, Japan, and Switzerland. So we’re so excited to have you today!

Matt Brady: That’s fantastic. Thanks for inviting me. I’m so glad to meet you and be here.

Katie Ritter: Matt, I am so—I was telling Celine—I am so excited about this topic. It is something that I am also personally super passionate in. So I told Celine she might have to, like, tell me when I’m making the recording way too long because I’m just so stoked to talk about it and specifically the systems piece that you’re interested in. So you say, you know, in kind of the opening here, right, like: “Does coaching actually work?” So in order to determine if it’s actually working, right, obviously we have to look at some data there to actually make that determination. So in your opinion, what do you think is the single most impactful metric that any instructional coach should be using to, first and foremost, measure their actual impact, but also to be able to justify their role to leadership?

Matt Brady: So, it’s such a great question and just to answer it, I think I would step back just a second and—you just mentioned a couple of key words and as we were talking before we started, we talked about, you know, the definitions of words. And I think words matter in the end. And I think in a lot of times, especially with EdTech, the way that it’s been talked about for so many years—you know, we look at 21st-century learning and all these different kinds of, I guess, stand-ins for what EdTech sort of is involved in or is sort of responsible for. And I think one of the things that’s been really interesting in my work is looking at—undeniably, EdTech and coaching and integration and so on has been absolutely incredible in connecting families and teachers and admins and calendars and sharing. But I think what—when I came to look at that, you know, a lot of that is really digital administration and digital teaching. That’s not really digital learning per se. You know, there’s just these incredible pieces of contribution that Tech has made. And I think what ultimately I came back to about, you know, when we ask the question “is coaching effective,” I think absolutely it is. However, looking at the data about “what is technology contributing to student learning gains” and “how would we move that forward,” I think that’s where my focus has been because ultimately, you know, that’s why we’re there, right? We’re there for students and we’re hoping that they continue to learn and they grow into amazing people that do great things.

So I think, I guess just to clarify a little bit too around that… so, one of the other interesting pieces to come back to the words: You just mentioned the word “implementation.” And and that’s one of the things—and there’s nothing wrong with that word—you know, we substitute so many different words for what Tech is doing or how we do it. And this is one of the core pieces of my research that got me onto this topic in the first place was that when I became a Google Trainer, I recognized on the list there were 70 different names for who Google Trainers are. And I just wondered: How could that be that there’s this many different names for this role?

Katie Ritter: Matt, I don’t mean to interrupt you, but what’s so hilarious is when we launched this podcast back in 2020, our very first episode was “What is a Tech Coach?” And so in preparation for that, I sent out a tweet of “What is your title?” I got 200 responses; every single one of them was different.

Matt Brady: Wow. 200? See, now I was—thought I was actually kind of pressing the limit with 70, but it doesn’t surprise me at all that that’s… and so we’re going to eventually get around to your question. I don’t mean to sort of dance around.

Katie Ritter: No!

Matt Brady: Just to understand, just to clarify a little bit more because as we talked about, you know, my experience is in international schools primarily. So some of the language is a little bit different, some of the sort of workflow—you know, the work conditions are different because we’re often times just working for a single school, not across a district with multiple schools and so on. So, you talked about implementation and I’ve always made this distinction that a lot of times what happens in schools is things kind of stop at implementation. We implemented Google Docs and Canvas and Schoology, but to the extent that they’re actually integrated, that’s to me the question. Because it’s really easy—and I kind of joke about this—you know, a little bit of EdTech is a little bit like a leaf blower sometimes. It just is super loud, makes a lot of noise, but really just kind of moves stuff from one place to another. The problem’s still there, now it’s digital where we have the problem keeping track of the documents and so on.

So those—there’s these little bits and pieces and when you say “is coaching effective,” I think it is. However, kind of when we start to put these little things together—that the coach role is known as 70 or 200 different things—I think what makes it difficult to answer that question is that schools have a hard time supporting what they don’t understand. And I think, especially in international schools, there’s so much turnover in the roles—I mean of course the teacher stays consistent, admin stays consistent, we all know what an English Language Learning (ELL) or ESL… we understand that mode. But for coaching, it seems a little bit… it somehow is different, but for EdTech specifically—I know you guys deal with a lot of instructional coaching in general and I feel like I can see that much more deeply than I can with EdTech, just simply because the sheer amount of focus on the tools with EdTech. Whereas, you know, literacy coaching, they’re not breaking out special tape recorders and stuff like that for that; it’s much more mental.

So, my answer after all that—the answer is, and this is only my little narrow view, but if we think about all the stuff that coaches do, most of the time you’re trying to win. You’re trying to get more points. You’re trying to grow your lead over where you are now or, you know, some baseline and looking forward in the future. What I’ve found over time was I think the metric that I have used the most effectively is not about growth per se, but it’s: How well were you able to remove the factors limiting growth?

So… more and more words. But there is a difference in that, because there’s a difference between—you know, it’s not about doing things differently within the same model, it’s about actually doing different things. And so this can mean lots of different types of measurement, and this is the biggest piece right now that I’m working on is: How do you measure effectively and simply and visibly removing a factor limiting growth? So that’s kind of where I come from on this.

Katie Ritter: I love that so much! So many things… I had to start taking notes!

Matt Brady: It’s all online, you don’t—

Katie Ritter: No, I’m glad that you started with that, like, taking a step back in that introduction because I agree with you so much. I mean, like I said, 200 different titles. And I also agree with you that I feel like when it comes to content coaches or general instructional coaches, the nickel seems to drop a lot faster for folks about what that coach does and how they support teachers in the classroom vs. our tech coaches. Could not agree with you more there. I mean, we talk so much about the importance of role clarity, one for the coach themselves so that they do the work that they should be doing that actually leads to, like, coaching impact, but also for everyone else. So I love that you started with that because I think that’s spot on. And I also totally agree with what you said about, like, it’s hard for the tech metric vs., again, general instructional coaches, because I think, you know, what we often see is that the instructional coaches, dedicated content coaches, right—like literacy coaches—are sitting down with the (in the States) English teachers and looking at student test score data. Right? It’s easier to look at the data, work with them, improve, and then again look at that student data to see if it’s improving. We can come to a conclusion that obviously the instruction’s improving if the test scores are improving. Whereas like the tech coaches, we aren’t necessarily always afforded that same opportunity to sit down and look at the student data with the teachers. And I think some of them would be willing to do it if asked, but I also think there might be a little bit of, like, “Whoa, that’s not necessarily your lane, like what are we looking at?” So I can appreciate the search for a good metric that you’ve been going through because it’s not—you know, our goal, we all know as a… I’m just going to say “Tech Coach,” right? Whatever your title, we’re going to use that for today. Our goal is always to improve student learning. Right? That’s where our passion came from. We came from the classroom too, we just happen to be tech-savvy so now we’re helping you too! So our goal’s always student learning, but it is funny because we’re not always afforded that same opportunity to look at the data. So I think that’s great.

If I can dig just a little bit deeper: When you say you’ve been—and I can see how it’s hard to show that you’ve removed something—but so when you’re thinking about removing barriers, what are some of the things you’re looking at or the data that you’ve collected as a part of that metric to show that you’ve removed those barriers to learning?

Matt Brady: I mean—so, just to… there are a lot of separate little pieces, but I think just to come to one of my favorite ones and it’s—it’s got a name, it’s called the “Yak Shaving.” And yak shaving is generally a workflow description. And if you’re not familiar with it, it comes from the fact—as simple thing of like, any time somebody has to do, you know, let’s say we have a task we need to do, and in this case they call it, let’s say the yak shaving just simply means that you have to do A, B, C, and D in order to actually do the thing you want to do which is E. And so this the whole concept is that you think about a teacher’s workflow. Like, I—you know, almost every school I’ve been in, they have a Student Information System (SIS), they have an LMS, and those things don’t quite talk to each other. And then there’s also possibly a, you know, a disconnected curriculum tracking system. And what inevitably happens is that when the teacher has to input grades, for example, they have to introduce another Excel spreadsheet to actually somehow get the grades from here to here over in here. And so yak shaving just suggests like when you’re given a task to do X, that that means that you in to do that, you actually are doing these completely irrelevant things, you know, sort of toward that goal, instead of actually doing the thing.

And so part of what I’m looking at, what I’ve worked on as more of a Project Management approach to coaching, was what—look at the process maps for how these, you know, grading or even simple things like submitting PD forms. You know, how many different steps are teachers being asked to do and spend time on to do all these bits when instead of being directly able to just enter your grades into the system, you know, you’re ending up having to do these other—”yak shave” effectively—which is some, you know, relatively of course it looks like it’s moving towards that but why wouldn’t you just enter the grades in the system? So that is one of the big metrics, just looking at something where where you’re not—you’re doing something apart.

Celine Thomas: Can I jump in before you… I just—so many things. One, will you spell “Yak”—are you saying yak?

Matt Brady: Yes, Y-A-K. A yak, like a buffalo.

Celine Thomas: Okay. One of the things I always think about and share, and in the context I always share this with coaches when I’m doing work with them, this quote: “Every system is perfectly designed to get exactly the results it gets.” And I’m always thinking about that, like, if we’re having problems, how have we designed the system to lead to these patterns of problems that we’re consistently seeing? Right? So all of the “app sprawl” of having teachers go from here to there to here to there, I think is so real. I really appreciate that perspective of—I’ve never thought of it like that for teachers, of how do we remove extra steps for them in the way that you just described it. I think it’s really smart. And ironically, I just had a conversation with a colleague about our forward-edge employees for trainings we’re doing around the registration form and having deadlines. And I’m like: Is the point that we want people to get there or is the point that we want them to register by this deadline? Because I think we’re creating a barrier to just get them to show up. So how can we rethink that and just, like, make it as accessible as possible? So right right along the lines of what so—that’s just, like, ringing home to me because I just recently experienced some myself.

Matt Brady: Well—yeah, and we all do. And it’s not something specific to EdTech or schools or anything. I mean, this is system design in general, it’s kind of just general principles. But what you just jogged a little piece for me: This soundbite about “Are you designing systems to make it easy to comply?” And with the mandate or the initiative or the protocol, that’s really what this measurement that I’m trying to find out comes down to. And and you can call—I’ve heard this called different things. It can be called “Computational Kindness.” Like, how much hoop-jumping and do is it you have to go to the email to the website to click here to open this thing? And I think all of that cognitive overhead builds up and because so many of these processes that teachers have to do that aren’t really about—they’re not about it’s the digital teaching part, it’s not about student interfacing, it’s not about designing, you know, curriculum and so on, it’s just the sheer administration of being a teacher. Those are the pieces that oftentimes you can start to look at first to say, are you actually making a difference in the amount of time that a teacher has to be a teacher, rather than a, you know, sort of “techer.”

So, and again kind of comes back to the—so you’re are you designing for people to easily comply, but also at the same time, what you’re really trying to do as a coach is to get them to commit. You know, so you want commitment, not compliance in the end, because people kind of resent compliance. But what you’re trying to do is get them to commit. And that’s again where shifting this lens from looking at, you know, EdTech and coaching and so on as a growth function… what really people want first of all to get them to grow is they want their systems they have right now to work. Hands down. I mean, don’t give me super-duper, you know, App 2.0, I want the apps we have right now to work first. Then they’ll gladly commit to the growth part. But I mean that—so, now, at the end of the at the there you can do them both, this is not an either-or thing, right? So anyway that—this choice of or sort of distinction between commitment and compliance is really interesting one, and I think ultimately we want to be able to comply as easily as possible, because some parts of it is I mean you just these are the things we have to do.

Katie Ritter: Absolutely. I love the “Computational Kindness.” I’m just going to circle back because there was a lot of things there too that I related to as a coach, especially going back to talking about, like, how do you morph into the coach that is needed, especially being that I’ve in my recent district gone in as a Tech Coach, but recently it’s been all about data, like in every single building. So it’s like now I’m in these data meetings and they’re like, “Oh well, what’s the best tech tool that’s going to help achieve this this and this goal?” But then there’s the instructional input that I also want to kind of intercede. So it’s just interesting to see, like, what ways, like you were saying, like how do we streamline the ability to have all these aspects of coaching into more of like a project structure. Like that—I’ll go back to the other thing, but we can go on to the next question.

Matt Brady: You’ve made a really interesting point there, and the idea that I think that I think we’re coming to or I’m coming to is that what you really want to show—and data can be a part of this—is that I think part of the challenge with being a coach in the way that it’s currently done in in an EdTech coach is that, you know, a lot of it is about tools. I mean, that’s that’s the stock and trade of what a lot of this is. But I think what a lot of times it feels like what we’re doing a little bit is building dependency. That you’re the person that’s going to be able to tell them to show… and I think to kind of come back to the first question or the questions, what I think that I’m trying to sort of come to an understanding or a system, you know, consistent system is that: How can you show leadership that you’re building capacity versus a dependency again on you? That that you’re the only person that can come in and, you know, make the sun shine. So part of that element of removing these factors limiting growth first, that allows for the less dependency because then people have bandwidth to actually, you know, they feel like this is actually going to be worth it. The bits that I actually really need to do, I feel pretty confident about, it’s relatively smooth. You know, it’s just… so I totally understand.

Katie Ritter: I mean, we are—it is so often focused on the tools for the tech coaches. And so we often, you know, preach on this podcast and the work that we do with coaches: like, pedagogy first, instruction first. Like, what’s the purpose? What’s the outcome? Then follow it, you know, with the tool to to really drive that you’re there to support that instruction and those students. And I don’t know if you’ve seen it, Matt, but we actually published—it’s called the “Core of Coaching Framework”—and Domain 3 is all about that piece that you’re hitting on of, like, building that sustainable capacity because no, you know, we all want to leave a mark, right? Like we all want, we all hope that we are coming into education to make kids’ lives better, right? And then we become a coach probably because then we find this passion that we have, you know, that has grown from not only students but supporting adults to exacerbate our our, you know, tiny little impact and in some small way and help the teachers then impact their students in a bigger way, right? So that that can’t sustain if they have to come to us with every single question and seek every single thing. So that building capacity is so important, so I just love that you touched on that.

Celine Thomas: I know, I’m like Celine, it’s okay, we’re going to have this recorded for later. I know the social media channel’s going to love all these, like, quotable nuggets you’re throwing at us! I’m over here thinking about structural changes in school districts. What structural changes are essential to transition coaching from, like, a vulnerable, soft thing to something that’s more stable, non-negotiable—something that the school district actually needs or wants?

Matt Brady: Yeah. So, just—I’m going to repeat myself just a little bit because I will talk—I think part of that is is to be able to demonstrate how you’re building capacity. And I think what we’ve typically done when we’ve we’ve answered that question or tried to demonstrate is “how many trainings did we give,” “how many people logged on to the app” or “how many people are participating, using this particular system”—you know, looking at analytics in that way, and there’s absolutely nothing wrong with that. But I think one of the things that too that we could add into that is: How much have you been able to bring EdTech, IT, and teachers and coaches and admin together in collaborative meetings? I think that’s even just that metric: How often have you been able to meet with these different groups rather than just teachers?

And and I we come back a little bit to this the ideas, you know, are teachers there to be passive recipients of our PD or are they there to actually help us to help them? And here’s—here’s the thing that most blows my mind about everything and and I kind of want to talk about this today. I don’t know if it fits. But if you think back to the early 2000s when SAMR, TPACK, TIM, PICRAT—all these things came out, you know, now it’s two decades ago. All of the frameworks super valuable. For me, the simplest one has always kind of been Triple E now (Engage, Extend, Enhance). Really cool, really useful. But here’s the thing about that is that there has not been a single school that I have been to that has any consistent understanding, setup, you know, collaborative process in place to actually make sure those conversations—to talk about what how the tech leads… or sorry excuse me—so the learning leads… it just blows my mind that, yes, we have all these frameworks and things, but there’s no there’s no connection from the engine to the transmission. It’s “Yes, here’s all this wonderful stuff,” but we didn’t… the whole idea about “when does this conversation happen?” I mean other than the sort of—and this is where I think the problematic piece about being a coach a little bit… back to words. Where does a coach—what’s the definition of a coach? What do we think about when we think about coaches? The person on the sidelines. And that’s not—that’s not where we are. That’s not… we’re not over there just kind of blah blah blah. You hopefully should be right in the mix, talking to teachers about their lessons right there. So I get it, but but at the same time I’m just and then you come back again—there’s 200 different titles. So I think part of the structural piece, you know, or this could be looking at: Well, what’s the right name for this role?

You know, in my very narrow view is that, you know, I come looking at it from Project Management. I’m much more of a Servant Leader in project management because you’re there to enable the stakeholders. And in EdTech’s case, it’s IT, it’s admin, it’s teachers, and you. But if those stakeholders aren’t there at the beginning of the conversations, then you’re just kind of piling things on assumption on… so, I mean structurally, like you kind of mentioned Celine, like we could talk about this forever because I think it’s we’ve EdTech and the and the sort of the machinery of the process has grown so big and so much that we never really ever got back to first principles to say, “Hey, does this actually what we need? Is this the best way to do this?” So yeah, there’s a lot of little pieces in the structure, but I think it’s, you know, a little bit of the the name in the roles. The other bit too is that, you know, you’re really as a coach from my view is you’re building collaborative infrastructure. You’re taking admin initiatives, you’re trying to figure out work with IT to actually make sure that those systems that the initiatives called for actually work with the workflows and the tech that the teachers have, but also then you’re working with those teachers to say “Well, this is the way you do it. Oh, you’re a Modern Classrooms approach teacher, or you’re EduScrum or whatever specific kind of thing they do.” Hopefully you’re trying to facilitate their process rather than, “Hey guys, guess what? We’re all going to do things in rows now, it’s all about…” you know, I think that education—we get in that cycle of like and everybody’s just like, “Oh god, here we go again. It’s all different this year.”

Celine Thomas: Yeah. I’ve noticed a little bit of facilitation definitely coming out of my role this year for sure, especially when it comes to data. So that that makes sense.

Katie Ritter: Yeah. It’s interesting too what you said, Matt, about the—you kind of started touching on it and I loved how you said “collaborative infrastructure.” I love just the visual that that paints about what coaches do. I’ve always felt like coaches have this really unique, especially a tech coach, just have this really unique position to, like, connect stakeholders. But I love the way you said building collaborative infrastructure.

Matt Brady: Just really quickly Katie, I’ve been so frustrated with this process that I actually… this is the model of the collaborative infrastructure of what I do in my job. And if you notice, those four different islands on the, you know, we’ve got admin, IT, coaches and teachers, and then in the middle basically you have this “X” because the work that we’re doing often times what you’re trying to do is bring all those four things together and hopefully tighten that because every—all of the the real nitty-gritty of where things happen are all on the edges, right? The IT’s got their way of doing things, admin does their thing, we do our thing, and the teachers do their thing. But ultimately your real job as a tech coach is that it’s you’re the one that’s kind of making sure that everybody’s—those things are actually working. And here—and so the reason that I think it’s valuable to talk about that collaborative infrastructure is because, you know, it gives people—people need a visual. They—how do you how do you sort of understand your relationship to everybody else in the system if you’re if it’s just—and we come there was a great what’s it called? The Elephant Problem. Right? Where you’ve got four different groups and they’re each touching the elephant, but like one’s got the tail, the other one’s got the trunk.

Katie Ritter: I literally used this image in yesterday’s workshop!

Matt Brady: Did you? I mean it’s very true constantly. Everybody’s looking at this thing and, “Oh no, this is all about it’s working great!” but just depends on where you are.

Katie Ritter: Yeah. It’s a rope, it’s a tree, it’s a wall. Scale back, it’s the elephant. Yeah. Oh my god, if you can send us a photo of that so we could use that, like, with this podcast, because if that’s not the best visual I’ve ever seen of, like, how uniquely situated coaches are to bring these groups together, that is awesome!

Matt Brady: It’s funny because that those that is literally there’s a story about how that came to be is actually probably the more interesting thing than the device itself, but really it’s those—it’s a combination of two failed Christmas presents that just never—they were not failed, but they just never got the traction the way that… you know, my my daughter she she gave it a try, but it wasn’t a big thing and I kind of just sort of had these parts and pieces and I’m like the things that were happening in the background. So for me it’s been helpful just to try to put keep my thoughts together and how does this work.

Katie Ritter: Yeah, I love that. That’s hilarious. I’m going to see what my husband’s built with my failed Christmas presents. Also—so thinking about, so we’ve kind of talked about, like, the structural changes and thinking about some of that, right, but I do believe there’s more in our control to help move that along, right? Like I think your visual of the interconnected and collaborative infrastructure that we can build just kind of proved that. But at the same time there is certainly something things out of the coach’s control. So I want to shift very much to thinking about: What is within the coach’s control, would you recommend to shift their work from just one-on-one teacher support to being able to, like, develop this wide-spread sustainable infrastructure with the teachers so that they can carry on and implement beyond us always needing to be there with them and support one another? What like is your like biggest piece of advice you would give coaches?

Matt Brady: And this is—this is one of the, I guess you would kind of say is that you’re a little bit shifting to less—you’re kind of what you’re talking about is teacher collective efficacy where they have this belief they can do it on their own. They are confident in their systems and their tools. I think what I’m finding in that model was kind of a good example is that what I’m hoping—I don’t think this actually exists as a statistic but—or as a, you know, sort of parameter of data collection—but what I have felt works is to actually develop Cross-Functional Efficacy. Where because you know that those stakeholders the teacher are working so closely together on any one of these initiatives whether it’s, you know, just the just the core function of our learning management system and a student information system and how all this stuff goes. How well are those stakeholders’ needs and goals represented by the system? So for me, I look at it just as much as I I want one-to-one with the teacher, part of that is actually taking those conversations and when I see a trend with teachers that are saying, “Hey, we don’t like the way that the iPads do this” or whatever, documenting all those pieces and then that becomes the next conversation with the IT guys to say, “Hey, is there any other way that we can do this?” It’s called Curatorial Journalism. Where you’re taking bits and pieces from all these different little media or, you know, you’ve got your tutorials and your tips from your groups and then you’re listening to the teachers and then you’re finding out, you know, looking about “What are the data from our parents’ survey suggest?” or whatever and you’re compiling all those to kind of make a case—all the time in this case might be to admin about, “Hey, this is not working for them, this is what they say about it.” I think that ultimately sort of helps teachers in the end because you’re constantly working to just to listen to them about what’s… you know, rather than the sort of—it again is removing those factors that are limiting growth so they’re with because we we I think teachers do get tired of of the growth thing. Right? I mean we see it in our culture, we see it everywhere. We want to grow, we want to get bigger, we want to get faster and better. But it’s exhausting. So and part of that—I mean I guess this is the thing is like you as a coach you can’t scale your heroics either to be able to be there one-on-one with every teacher or whatever but you can scale a system if you get it working. So mapping the mapping the friction points and things and just making that a part of the conversations that you have with these groups. To me, those are the kinds of things that contributes to wellness with teacher… you know, like where you start to get you’re actually able to shift these this belief within the group that, “Yeah, we can work together and actually make this stuff work” rather than sort of against each other. And I think…

Katie Ritter: When you—you mentioned something about folks working closely together on some different initiatives and it immediately made me think of: have you ever seen that image where it’s like there’s a big valley and on the, you know, on one side is are folks who are building a bridge and they’re halfway across and on the other side are folks building a tunnel and they get halfway across and it’s not until they’re both halfway across that they realize there’s already other people working on a way to get across? And that is just like such a visual for me about what I observe so often in education and is just like every so many people are working on accomplishing the same goal and even within the same school system. I think coaches have, again, like this really unique position that we have to, like, wave the white flag and, like, pull people to the table when needed in the way you said about, like, collecting data and being able to bring that to people. I I think coaches absolutely do that, but I just wonder like what about visually mapping that information for admin? But I wonder about, like, visually mapping it out, almost like your little system over there for the the infrastructure—like, would that help admin see like, “Oh wow, this is a lot of—this is a bigger problem, right? We’re connected to so many different things.”

Matt Brady: Yeah. I mean at this point, you know, with the frustrations that I have had of of having to to hope get time with principals and so on to to even get eyeballs on on anything is is often a big challenge, right? So much of the focus is on day-to-day and because I think Tech has gotten the it kind of comes back to a little bit of the leaf blower thing: it’s sometimes so loud and forms such a big function of what we do as I think there’s a little bit of sort of Chicken Little or something about you have to be really careful about how you sort of present this kind of stuff. I think what I’m looking at is these—ultimately people listen to stories. You know, that’s that’s how we pass things on. And I’m that’s where I kind of mention that bit about curatorial journalism, meaning like you’re you’re constantly looking at the stories from these people of what’s really happening and I I haven’t I don’t have the answer to that yet but I feel like there’s got to be a mixture of the demonstrating that you’re able to build capacity that you’re removing a certain amount of teacher time. You know, that eventually if you have to translate into that into money—you know, “Okay so we if we change we changed this workflow process so students don’t know no longer have to do the three steps, well if you multiply that out by well there’s 472 students, they no longer have to do this every that’s X amount of minutes and teachers blah blah blah.” I mean you can calculate that. I think but the challenging part about it is is that we haven’t there’s been a—we haven’t felt like we’ve had to do that. You know, we talked at the beginning of the program about how do we justify or our these positions and it’s a funny it’s a funny place to be to be hired for something and then justify it. It’s a strange and this is where we we occupy this little occluded middle of between these different groups. So you have to kind of make yourself visible but it’s weird that we have to keep doing kind of the same thing all the time. And I think about this with, like, coaching menus. You know every year all the menus come out. “This is what we do, this is where we can blah blah blah.” It just seems like at some point isn’t that menu going to go away?

Katie Ritter: Yeah, like don’t they have it memorized? I think administrators and and IT guys should also have to do it every year. Anyway, so—

Celine Thomas: I’d be interested to know, like, what ways you’ve collected data to either like identify issue or workflow with teachers or students. Like what are some like personal examples of things that you’ve done that you’ve seen that were successful?

Matt Brady: I’ll give a specific example: We have Chromebooks in the middle school and we also have iPad carts. I have an art teacher and he’s really excited, would loves to take pictures and so on but he’s also he’s got, you know, Grade 6, 7, 8—all these classes so everything has to be super, you know, as quick as possible. One of the first forays into testing this process of trying to get in front of lesson planning, we were talking about “Well, how are we going to run this unit and how’s that going to work?” and he was his in his assumption was, “You know, we’re not going to use the Chromebooks because it’s too too wonky with flipping the book and blah blah blah and trying to…” he’s like “we’re going to do iPads.” But I and you know on the surface that makes total sense. But when I actually went and looked at it afterwards, I took the iPad and the Chromebook and I calculated all the time for switching Google Drive login, so kids forgetting and which iPad and blah blah all that kind of stuff. And but the but the kicker was is that when I went into the Chromebook, all of the wonkiness about the Chromebook went away when because it has a scan function which will actually take a look at and cut out all the pieces, you know, extra stuff and actually made a better image than these better resolution iPads.

So in the end, just being able to listen to the teacher, what they actually wanted to accomplish, and then take the time to just do the testing. Like look at it and go, “Okay here’s—and then I just presented it back to him.” I said—it was a two-slide Google Slide deck. I’m like “Here’s the process with the iPad. Here’s the calculated time cost switching, you know, having to have the iPad cart in the classroom and blah blah blah.” And he was flabbergasted because he’s like, “Yeah, the…” and he was blown away because he just assumed that “Yeah, the iPad’s got a great camera, it’s much easier for the kids to handle.” But when you look at the total workflow—and I think that’s what what we’re the only ones that really have a good idea of that because we we understand a lot of people just don’t figure in the fiddling cost of oh my gosh the way that the logins work in the iPads with Grade 7 because of the blah blah blah. You know, those are the kinds of things where the value of the role comes in, is that you can if you can just actually get that ahead of time, then you’re not fighting fires all the time. You’re just you’re proactive rather than reactive. And I think that’s if anything kind of comes back to the SAMR and TIM and all these kind of things—all that’s wonderful, but you can really make such a big difference too just by making the basics of what we already have work. And people—and he was kind of over the moon about the fact that all of this infra—you know, all the reservations of the iPad carts and having to go and do all those kind of things, that just didn’t need to be done. And I think that people appreciate the fact that you can kind of shine headlights on a place that they just if they were to have to do it, they’d just say “Forget it, I’m just going to just have the kids hold it up” or whatever. That’s one example.

Celine Thomas: Yeah, that’s really good. Yeah, I feel like I notice once I started being more proactive versus… I think when I first started coaching I was like, “Oh, I’m just going to give you as many solutions as I can. Like we’re going to fix it as soon as possible.” But like your just explaining that approach of: it’s okay to sit back and like let’s lay out and then pick the one simple solution that’s usually the easiest thing in the book versus going about and just reaching for things is super important.

Matt Brady: But it took to get that meeting to happen for the first time was I connected EdTech to the MTSS (the multi-tiered support), and that even to do that was me lobbying to say, “You know, just get EdTech in with that group.” You know, I’m just like constantly advocating for like: I’m not going to—and I think this has been part of the problem because the mentality of inviting the EdTech person means that they’re going to, “Well, have you guys seen this though? This if you just do this, all we have to do is…” you know, and it’s like where you’re going to sort of dominate the thing with your tool. And I just I just feel like you’re we’re much better off a lot of times as listeners and then… you know, my role in the meeting was almost nothing. I just came back afterwards and said, “Hey, this is what I looked at. Here’s what do you want to do?”

Katie Ritter: Matt, as we kind of wrap up here, is there any kind of last words that you would want to share that we didn’t touch on? And I definitely want to make sure folks know how they can find and connect with you.

Matt Brady: I have all sorts of little notes. I appreciate your patience with my answers. I’m definitely one of those people that is, you know, as wonderful as it is to be able to talk and interact with people, I often times need to kind of come back to my little shell to think things over because I have, you know, so many different ideas and things come up when people are talking. But I but I really—it’s been really a pleasure to kind of listen to you guys and try to both understand sort of where your perspective… because it’s very close in so many ways to obviously what I’ve experienced, but also, you know, thinking about “what are the important things that are different or that are interesting that are emerging that we can…” and obviously, you know, these ideas about little models and… so I just really appreciate the opportunity to do that.

Katie Ritter: Oh my gosh, it’s been amazing!

Matt Brady: I guess there were certain little bits and pieces, right? We already touched on leaf blowers, so you you got that element. I think the whole idea of the EdTech piece, what we talking about in measurements and so on, you know: our accountability and being able to demonstrate that accountability. I hope that we can come up with some better wellness sort of metrics or ways to measure that because I think so much of what the real role is is if you’re really doing it as a coach, you can make someone’s life so much easier. And that can be everything from, you know, offering to to write the email to IT for them when the smartboard is not working and all these there’s so many different ways that just contribute at the end of the day to… you know, go to the principal to go, “Well, I’ve for 14 people I wrote the email to IT instead of them having to sit there and in even though that those kind of elements are so huge sometimes because your ability to explain what exactly happened rather than ‘My smartboard doesn’t work again, please fix’.” You know, you can do those explanations. And that the challenge of figuring that out I think is the core of sort of what we’re talking about about this accountability piece. Building the infrastructure I think that makes—I call it the School, but it’s really all of us: the admin, the IT, and teachers—that that afford makes visible the system so we can be more accountable for the things that happen within it. You know, we’re all looking at different perspectives. And so having this kind of common language to come back to—so important.

And that’s kind of what I’m working on, and people can—I write a bit on Substack and I have a website and I publish a little bit on The International Educator. And those those things are so—the addresses are so long that no one would remember. Maybe we can drop those in there, but I write at Edtech Synergist. And Synergist is the name hopefully what I came up for is this piece: Like, what are we really doing? We’re trying to build synergy between these four groups so we have something a little better than the sum of the parts.

Katie Ritter: Absolutely. Thank you so much, Matt. This was truly a joy.

Celine Thomas: Thank you for being a part of the EDU Coach Collective today. If you found value in this episode, the best thing you can do is share it with another educator or leader who needs to hear it.

Katie Ritter: You can also connect with us on social media. Just look for The EDU Coach and let us know your biggest takeaway or what topics you want us to unpack next. New episodes drop every other Tuesday. Be sure to subscribe and leave us a review wherever you listen to your podcasts so we can reach more coaches just like you. Remember, you are not on an island. You are part of a powerful movement. Now, go coach fearlessly!

Save our Brainforests!

Sustainable growth comes from user centred digital ecosystem design that removes friction.

(Originally published at The Fix.)

More than any other theme, sustainable development dominates K-12 classrooms. We teach students about collaboration, conservation and protecting finite resources.

At the same time, has there ever been greater pressure on school departments to meet relentless “growth goals”?

Grow test scores. Grow enrollment. More EdTech, more data, more systems, more engagement.

If you work to support a school in IT, HR, or Operations, you know this tension. Leadership wants growth or cost reduction or both. Teachers need support. You’re in the middle, implementing systems designed to help but somehow creating more friction.

You’re working harder than ever. Your team is firefighting daily. Every department is overloaded, yet still siloed, working against each other when everyone needs to work together.

The problem isn’t effort, so what is it?

Consider This Scenario

A new IT system saves HR tons of data entry and costs two thousand dollars less per year. 

Sounds efficient. But the system offloads that work to sixty teachers who never had a say in designing it. 

Teachers now spend 20 minutes navigating unfamiliar interfaces for what used to take them 10.

What would you call that? Efficiency? Digital transformation? Robbing Peter to pay Paul?

All this added complexity, offloading administrative debt and paying for it with staff brain cycles. When does constant “growth” become the problem, not a solution?

Consider This Shift

What if you stopped asking “How do we grow, get faster, more efficient within the department?”

What if you asked instead: “What factors are limiting growth and how do we remove them for the people we’re here to serve?”

The latter changes what you build.

When workflows are designed with user input up front, your support processes reclaim brain cycles instead of burning them. When departments solve problems together, you multiply teacher impact without multiplying effort.

You create the conditions for collective efficacy – the number one driver of student learning gains.

It starts with changing the question. 

Process Behavior Jams

Behavior jams are the moments when accountability falls between departments and nobody knows who owns the problem.

Where does feedback about your team’s work consistently bottleneck?

Why are other departments using workarounds instead of your process?

When teachers avoid your systems, what’s your first assumption? That they’re resistant to change? Or that something in the design isn’t working for them?

Here’s the shift: Move from “tool-first” to “workflow-first.”

The question becomes: How do we design process X so we get the work done without imposing shadow work on our colleagues?

Offloaded Invisible Labor

When was the last time a teacher was in the room when you designed a new process?

If the answer is “never” or “rarely,” what does that tell you about who the system is optimized for?

  • What cognitive overhead are you forcing onto end-users?
  • Is your department constantly solving problems or finding them upfront before they occur?
  • How many disjointed, prerequisite tasks are needed before someone completes the work you’re asking them to do?
  • Does your system anticipate problems because you took steps to understand user behavior first?
  • Was support built directly into the workflow at the most likely point of need?

Consider these questions:

If you don’t know the answers, that’s actually the most important data point because it means the feedback loop is broken.

Stop Celebrating Firefighting

When was the last time your department celebrated someone for being a hero? For staying late, for saving the day, for making the impossible work?  Probably today.

Here’s what that hero narrative might actually be signaling: unsustainable infrastructure.

What if you celebrated something different?

What systems could you build that don’t require heroism to survive?

What if the highest form of contribution was friction removal – when a team identifies and removes a factor limiting growth?

When you throw a parade for that, you signal what actually matters. When you explicitly credit the cross-functional collaboration that made it possible, you generate curiosity. Others start asking: “How did they do that? Could we do that with our problem?”

That’s how the real mechanism that drives innovation – the way things come together and connect – becomes permanently operationalized, not a fluke requiring superhuman effort.

Look to nature

We teach students that healthy forests require biodiversity, interconnection, and careful stewardship. That every organism affects every other. Our brain forests work the same way. The paradox about improving collaboration? It only takes one person.

This week, pick one process your department owns. Ask a teacher: “Where does this create friction for you?”

Listen without defending. What you build together? That’s the fix

A Better Way to Do IT in 2026: Synergistically

For 2026, I propose a radical change for EdTech provision in K-12 Schools— actual, sustained collaboration between IT, Admin, Teacher and Integration teams.

Even more outlandish? The work has nothing to do with “thought leadership”, “growth, now!” or “coaching/fixing” people.

The space I’m working to change is the shadowy side of things where the “tech bro and sister” sun doesn’t shine because of the absence of deliberate, collaborative work in:

  • Cultivating collective cross functional efficacy across the community, the #1 correlate of student achievement growth.
  • Moving beyond “problem solving” to building collaborative, “problem finding ” culture instead.
  • Identifying and removing gumption traps and bottlenecks that drain teacher time and energy
  • Illuminating the rube-goldbergian, internal systems yak shaving on administrative systems that create shadow work for teachers.
  • Building computationally kind infrastructure that delights in its consistency of function because its design was aided by those who need to use it, up front.


Interestingly, none of these are really “technology problems” at all, and they’re not solved by the approaches “Tech Coaches” typically use as they’re not about “tool training”– they’re collaboration challenges wearing technology masks. 

The Synergist Project is a deeply human, context flexible protocol and set of role-defining resources for transforming how individuals and teams within educational communities collaborate and learn together to build collective cross functional efficacy. The work defines the “how” of digital transformation work regardless of the “what” of objectives, goals, platforms, devices, & software.  

Drawing on established systems frameworks (ISTE, MIT Center for System Awareness, Senge’s 5th Discipline @ learning organizations) the Synergist Protocol makes an original contribution by organically integrating and applying these “elements” to the specific archetypes & challenges in the K-12 technology integration space.

You can further convince yourself of the need for a better way in solving the “EdTech value delivery problem” at synergistprotocol.com.

You get the free resources to begin implementing the work at edtechsynergist.com.

Happy New Year!

Why Is Your K-12 Learning Community Tech Rich But Systems Poor?

You Can’t Name It? You Can’t Tame It.

Schools invest millions in learning management systems, collaboration platforms, and digital tools, yet many teachers avoid technology, IT departments still field the same support tickets, and administrators struggle to measure real impact. The problem is that we’re trying to solve 21st-century collaboration challenges with 20th-century change management approaches.

Walk into most schools and you’ll find the digital equivalent of archaeological layers. Managebac sits on top of Google Classroom, which overlays the legacy SIS, all while teachers maintain their own spreadsheets because the systems don’t talk to each other in ways that actually serve their work.

We implement technology as if schools were machines where you can swap out parts, rather than complex adaptive systems where every change ripples through relationships, workflows, and cultures.

Why Traditional Change Management Fails

Schools are collaborative ecosystems. Teachers need to coordinate across departments, IT needs to balance security with usability, and administrators need to support innovation while maintaining compliance—all simultaneously. Each group operates from their own expertise and constraints, often unaware of how their work impacts others.

Traditional approaches assume you can plan change, implement it, and then maintain it. But collaborative work is emergent. The best solutions arise from the intersection of different perspectives, and you can’t mandate perspective-sharing any more than you can mandate creativity.

When we try to force collaborative systems into hierarchical change processes, we get what systems theorist Peter Senge calls “complexity catastrophe”—the harder we push for change, the more the system pushes back, and we get what we see today:

Kabuki Integration: Adopting some of the performative language of innovation while core structures & workflows remain unchanged.

Weak matrix paralysis: People who understand the work (teachers/integrationists) do not direct it, and those who direct it (administrators, IT departments) do not understand it.

Solution proliferation: The tendency to adopt a new tool for every new problem, creating a disconnected digital environment.

The Missing Piece: Transparency for Alignment

School systems don’t need more management; they need more transparency. When stakeholders can see how their work connects to others’ work, when they understand the constraints each group faces, and when they have shared language for navigating complexity together, alignment emerges naturally.

This isn’t about consensus—it’s about clarity. It’s about creating conditions where:

  • Instructional technologists can design with teachers’ actual workflows in mind
  • IT can anticipate needs rather than just respond to crises
  • Teachers can adapt tools to serve learning rather than just comply with initiatives
  • Administrators can measure what matters rather than what’s easy to count

What’s needed is a framework that honors the collaborative nature of educational work while providing concrete steps for navigating the messy, non-linear process of sustainable change. Not another top-down initiative, but a way of working that grows from the ground up through transparency, shared understanding, and aligned action.

This is where the EdTech Synergist Protocol begins. What actually happens when smart, committed people have the language and tools for thought to collaborate effectively across the community?

I spent 15 years battling across this dysfunctional gap and built the tools bridge it. The free, open source project will drop just in time for Christmas.

Why I Stopped “EdTech Coaching”

A moment of obligation is when you see something so fundamentally wrong that you can’t unsee it.

Eighteen years ago, on my first day as an international school computer lab teacher for elementary students, I watched an eight-year-old try to log on to a lab computer.

Before she could open the browser and start class, she had to click through the entire Windows XP “fresh install” setup sequence. Fifteen separate pop-ups requiring precise clicks; one wrong click invoked long spools of additional software installs. Most students did not read well, nor did they understand what the prompts meant even when they did. It was a nightmare.

No problem though, I thought at first. It’s just this initial login from summer maintenance; we just have to do that once.

The next class came in a period later. I was wrong. It was every login. Every student. Every class. Permanent. I was told by IT that unless all the computers were re-imaged—which there was no time to do—this was the reality. They had worked most of the summer making the computers work this way.

IT had implemented this in good faith. They were protecting the machines from USB viruses. They solved their problem and created ours—a janky time-suck to start off every single class.

IT’s internal priorities were security, system integrity, and making their jobs easier in an understaffed school. Student learning wasn’t part of their team’s communication loop, so it wasn’t part of their system design. No one was “wrong”; the infrastructure for a conversation to avoid failure for student learning simply didn’t exist.

The Hero Trap (Or: How I Made It Worse)

I was new to the school and realized there was little we could do in the short term. So, I “fixed” the machines each day by logging in for the kids ahead of every period I could. It took me about 10 minutes to prep the whole lab. Problem solved.

I’d turned a systemic failure into my personal daily ritual. The better I got at absorbing the dysfunction, the longer it survived.

This is what I now recognize as the first trap of educational technology work: individual heroism masking collaborative infrastructure failure. We are the people who make broken communication and tech systems appear functional—and in doing so, we make it more likely those systems remain.

The Escalation That Failed

Eventually, I stopped being the hero. I escalated as it was just too ridiculous and other similar symptoms of “siloed decisionmaking” were cropping up all over the schools tech infrastructure. I pointed out the “collaboration” problem directly—to the techs who’d configured it, to the Tech Director, to the Principal, to the Head of School.

The Tech Director understood, but said “local staff” operated quasi-independently; he was half-embarrassed but without pull. The Principal understood but didn’t have the bandwidth or context. Everyone else heard a complaint, not a systemic issue. I wasn’t surfacing a design thinking flaw; I was being difficult.

That’s when I started to understand: there was no shared space where “IT’s security needs” and “student learning time” could be weighed against each other. I was asking for a conversation the school’s infrastructure didn’t support.

Two paths, both failures:

  • Path 1 (Hero mode): Absorb the problem. Nothing changes. Burn out quietly.
  • Path 2 (Escalation mode): Surface the problem directly. Look like a complainer. Allies now? Too late.

Be more resilient. Advocate louder. I tried both. Neither worked.

I Stopped Calling Myself a “Tech Coach”

At my next school, I became an official “EdTech Coach”, but I didn’t stick to what the title suggested. I was not on the sidelines (the very definition of a coach), nor was I there to “fix” teachers or push only for “growth.”

I started thinking of myself as someone removing friction. Alongside training, I focused on connecting stakeholders before problems emerged. Instead of training teachers on tools they did not request, I built the communication infrastructure that let IT, Curriculum, and Administration actually see each other’s constraints regarding the tools teachers depended on.

In short—I stopped waiting for permission to do the work that actually needed doing.

As in all schools, there was always a lot of loose talk about collaboration, but interestingly, not one of the words in the allstaff slide decks or meeting norms changed any structures.

So, I set up the collaborative calendaring system with the Learning Support team when IT told the Dept. Head they could not look into it for “several weeks.” We just built what the department needed to start functioning in our ecosystem, not what IT wanted to build when they found the time to overengineer it.

Then, having shown myself a capable listener and collaboration partner with the Learning Support team, and having access to the LS collaboration calendar, I showed up to my first meeting to support the LS team and the teacher before anyone asked me to.

This action shift sounds small and a bit awkward…but it was neither.

This was the school’s first truly collaborative, regularly scheduled planning meeting for student support—held before the teacher’s unit began, and it was as if the seas finally parted.

Welcome to Assumption

At the meeting, the art teacher explained that he planned to require students to take quality photos of their projects throughout the unit.

“iPads, obviously—everyone knows iPads take better pictures,” he said. I knew there were some caveats to this—which iPad cart he had, availability, etc.—but I knew what he thought he knew.

I started to mention that student Chromebooks could do this, but before I could explain the pros and cons, he stopped me. Nope. He didn’t want my input. They were going to use iPads. He knew how to do it with iPads. To him, the “tech coach” was the person adding more complexity to his plate, and the last thing he wanted was anyone else telling him what else he needed to do.

I was fine with it, didn’t argue, made a few suggestions for differentiation possibilities and the meeting was a big success.

Then, I Tested the Assumption

The result? The Chromebook camera image was sharper because of its built-in scan/tilt image functions, and faster because each student already had everything they needed. The workflow of the iPad cart, the Google login times, the student retrieval and return of the iPads, all that device-switching chaos—it was all unnecessary.

The 10 minutes I took to test things saved at least a dozen cumulative hours of student busywork over multiple lessons across all his classes. Several failure/chaos points—20 students getting ipads, logging into each student’s Google Drive, upload, logout of Drive, replace the ipads in the right places—gone. Three steps instead of ten. Zero IT support tickets generated. Everything the students needed in a single 30 second video of the Chromebook scan/adjust feature.

He was slightly embarrassed for having been so certain there was “no other way.” He invited me to his own art show some months later, ironically titled “Welcome to Assumption.”

After that, everything shifted. He started calling me before things went sideways because I’d removed friction instead of adding more; his (and many others in education) impression of what “Tech Coaches” aka “IT people” do.

Here’s What I Learned

  1. Schools focus “tech coaching” on the lowest-leverage points: training, apps, and devices. Meanwhile, the highest-leverage point remains untouched: the collaborative infrastructure that would let IT, integrationists, teachers, and administrators actually work together.
  2. SAMR, TPACK, TIM—all the EdTech “frameworks”—falsely assume (and depend on) coherent, consistent collaboration processes. They are great destinations, but they mean little when there are no roads.
  3. Every hour spent as a human workaround is an hour the system doesn’t have to change. Every crisis you absorb is a collaborative conversation that never happens.
  4. You can’t scale individual heroics. You can only scale collaborative systems.

A Question You Can Ask Yourself

If you’re an EdTech integrationist, a technology coach, or a digital learning specialist—whatever your title is among the 80+ variations in the field—

Are you solving the real problems, or is your “heroism” helping to hide them?


Matt Brady has spent 15+ years in educational technology leadership across international schools. He is the developer of the Edtech Synergist Protocol, a framework for supporting instructional technologists in building collaborative infrastructure within K-12 schools.

Yak Shaving: The Hidden Costs of Shadow Work in Schools

The question isn’t whether you can afford to fix these problems; it’s whether you can afford not to.

Schools waste hundreds of hours of instructional prep time per year through poorly designed systems that offload administrative work onto teachers.

Unnecessary screen time breeds serious staff wellness problems as well as productivity losses.

What Does Yak Shaving Look Like?

Consider the teacher who needs to record their expenses, update their emergency contact info, or apply for PD, for example. These procedures often trigger multi-platform odysseys:

Go search for the form because the initiator forgot to directly link to the form in the reminder email. The teacher navigates by muscle memory to one of the likely two or three different portals they remember the form might be, finds the old form (that wasn’t removed from “the old storage place”,) and fills that out and sends it. They then get a response back the next day saying “that was the old form” and get redirected to a different platform to fill out the new form, and then discover the new form requires a line manager’s approval, which triggers another set of emails.

What should have been a five to ten minute task takes 30 minutes over two days.

    This is a form of “yak shaving”– doing Z, to do X, to do Y…so you can do A– and it happens when systems are designed to be locally efficient for the department that built them, but impose significant cognitive overhead on everyone else.

    Yak shaving is not at all unique to schools; it festers anywhere a culture of administrative control is pervasive; where technology adoption means “following orders.” This approach prioritizes ensuring users follow a process over designing systems that make compliance seamless.

    Building a Culture of Collaboration & Design Thinking

    Your teaching staff didn’t sign up for a second job managing and tracking shifting administrative infrastructure; they came to teach and support students. If they are avoiding a new system, creating workarounds, or flooding inboxes with questions about processes, it’s a sign there is a collaborative literacy problem, not “user resistance” or “people having technology problems” problem.

    The path forward requires a fundamental shift in perspective to design and support systems that enhance people’s sense of competence and wellbeing not sometimes, but all the time.

    1. Shift to a Service-Oriented, Design Thinking Mindset: Flip the framework from “How do we ensure compliance with our systems?” to “How do we design systems that make compliance as effortless as possible?” This change doesn’t just improve technology adoption rates, it plays a significant role in transforming your entire culture.
    2. Foster True Collaborative Literacy/Elevate Your Community into Active Agents of Change: Staff should be designing system innovations, not just implementing them. Before you deploy any new system or process, map the task journey with real users to identify every cognitive switching cost, authentication step, and form field that requires external input or other non-intuitive extras.
    3. Get Feedback Proactively- Organize sessions with staff members to gather feedback and incrementally iterate your processes until every pain point has been minimized before you launch the new process.

    Yak shaving and the shadow work it creates reveals a deeper organizational issue, because when systems prioritize departmental convenience over your mission and user needs, you’re not just wasting time and productivity, you’re communicating that your most valuable human resources exist to serve administrative processes rather than educational outcomes.

    What can Teachers, Tech Coaches, IT Support, and Administrators Learn About “Collective Teacher Efficacy” From F1 Racing Pit Crews?


    Formula 1 is a dynamic, ever-evolving sport with constantly changing technology and regulations (like school). The relentless pursuit of improvement and innovation is ingrained in the DNA of Formula 1 (maybe not so much like school). In the 1950s, the typical pit crew team consisted of four engineers— today there are as many as twenty specialized crew members in the pits.

    Pit stops became faster and faster as the sport caught up to the reality that pit stops play a critical role in race outcomes, and teams gradually involved more and more people in the process. Equipment and performance improvements have evolved so that average stop times take 96% less time today than they did when F1 began in 1950.

    What makes high-touch support and collaboration like this possible?

    Matching outfits and headsets help, but it’s the shared vision— clarity, and planning done ahead of time and around the work of helping the driver (teacher) succeed that drives the teams. It takes collaboration, communication, and consistent feedback loops—as without feedback, a system does the same thing again and again.

    A pit stop is the educational equivalent of a specialist integration 

    Having this collaborative purpose/vision means they’re all working on fueling and changing the tires as quickly as possible, making the car go faster (more students learning) and keeping the drivers (students & teachers) safe from accidents. Yes, it’s all of those, but they all share a much bigger purpose, too. Even though the pit crew members are all specialists, they think bigger than their specific task, focusing on the success of the whole as much their piece of the car (learning). 

    Ad hoc tech use, and the fire-fighting problem solving it creates, should be avoided because of this tendency toward invoking Process Behavior Jams (PBJ). Instead, collaborative Practice, Insight and Execution (PIE), all the time, every time, as much as possible wins races. (eg- good days teaching; everybody loves PIE, PBJ, not so much)

    Commonalities with team dynamics that contribute to the success of F1 crews that inform our practice in teaching teams are:

    * Preference for collaboration (scheduled meetings ahead, or just in time). Does everyone on your team dig collaboration because it’s a catalyst for “winning”: innovating, getting support and avoiding unplanned jams?

    * Periodicity of feedback; not just per lap, but per race, per season (or per lesson, per unit, per year). Deliberate periodicities of feedback aid understanding, optimize readiness for intervention, and inform changes and improvements.

    * Listening to & leveraging the driver/user feedback (staff, students, admin, IT). Are you consistently monitoring that all user needs are being met as effectively as possible? Is your work “computationally kind” to your users; eg- systems and processes that are easily accessed and focus on usability and engagement for students?

    This is just one example to begin to build our mental models around what is possible if we consistently apply a systematic approach that focuses on collaboration and collective efficacy—it’s the top of what moves the needle for gains in student achievement. (Hattie, Visible Learning)

    Asking questions, digging, double-checking, and caring enough to push through the inertia of “we’ve always done it that way” (ad-hoc) is the key to identifying and redesigning systems and processes that fritter away–in large and small increments of PBJ– hundreds of hours of our most precious resource—human brain cycles.

    The Hidden Reality of EdTech Work

    What becomes possible when you start designing learning as infrastructure rather than intervention?

    As I look ahead to the new year, I’m stepping back from traditional “edtech coaching” goals toward something that feels more authentic to the work I actually do, and what’s most needed in my schools: building collaborative infrastructure/capacity.

    I think many of us in EdTech struggle with an unspoken identity crisis. We’re hired as “edtech coaches,” “digital learning specialists,” or any 70+ similar titles, and too often nobody else in the building really understands what we do beyond being one of the “IT people who helps with technology.”

    What I see is that every “technology integration” initiative is actually a complex stakeholder alignment project where success depends not just on technical implementation, but on managing the conflicts that arise when people’s expectations, values, and working assumptions collide given scarce resources like time and attention.

    Most of us doing this work possess strategic insights about learning ecosystems that we’ve never been taught or allowed to articulate. We see patterns that others miss because of where we sit—we understand the gap between a school’s aspirations and daily reality because we live in that gap.

    Here’s an example: It has been roughly two decades since almost all of the most familiar models of technology integration in education arose: SAMR, TIM, TPACK, etc.

    In the three K-12 schools I was hired to support digital transformation in the last decade, none of these tools addressed the key component each of the frameworks take completely for granted—a clear, well understood system of collaboration between Admin/IT/teachers/edtech integrationists to enable these collaborative conversations to happen consistently, or frankly—at all.

    The result? Technology that can seem to function like a leaf blower: making a lot of noise but often just moving problems from one place to another; in effect creating as many problems as it solves.

    Our challenge is particularly complex because while we’re trying to create conditions for focused, collaborative learning, we’re simultaneously navigating systems designed to fragment attention, extract data and monetize distraction.

    To me, no matter what AI “FOMO” has everyone feverish, or “new directions” are shouted from administrative mountaintops, the sides of the mountain—how are people oriented and supported towards collaboration?—is the real need.

    So, my goal is to reframe my work toward building collaborative capacity alongside individual skills. Instead of asking “How do I coach people to use tools better?” I’m asking “How do I help all of my stakeholders align their expectations and work through inevitable conflicts toward shared outcomes?”

    By moving from training delivery to facilitating collaborative design processes, we co-create solutions that honor actual workflows and constraints. This kind of collaboration aims for a win-win outcome where all parties involved (Admin, IT, teachers) find a solution that satisfies each their needs, while compromise involves each party giving something up to reach a mutually acceptable solution, often resulting in a lose-lose scenario.

    Given your current collaborative capacity and constraints, what becomes possible when you start designing learning as infrastructure rather than intervention?

    Reimagining Your Story @ Digital Learning: Three Questions

    You stand at the water’s edge, looking out at the vast ocean of possibilities that technology holds for your school community in 2023/2024. The first of the big Chat GPT waves from last year have receded, leaving behind a relative sense of calm — a moment of introspection. 

    You look toward the horizon and see wispy clouds, seagulls…and wait, is that a giant digital clockface flashing 12:00? It is. It’s the infamous “blinking 12:00″ from VCRs of yore, encapsulating the frustration that arises when technology requires more cognitive load than users are willing to bear. When the perceived cost in time and effort exceeds the perceived benefit, resistance to technology ensues.

    Which begs the question, so you ask yourself “Despite consistent and undeniable technological advancement, why hasn’t the enormous investment in educational technology over the past two decades resulted in anything more measurably significant in terms of student achievement gains than if we’d instead focused on using simple, well-known teaching strategies?”

    You wonder: Could it be that technological transformation is far more a social process than it is a technological one?

    Might the path to meaningful progress be high-touch as much or more than it is high-tech? You consider your school’s overall past performance in challenging established norms, dismantling paradigm paralysis, and encouraging innovation…and…what’s clear is a fresh approach certainly couldn’t hurt.

    Dynamic school leaders see their role as serving their communities, as co- constructors of systems and workflows that prioritize the needs of students, staff and the community–the users—first. This is how dynamic school cultures do difficult things.

    You know that organizations fall to the level of their systems far more easily and more often than they rise to the level of their goals so you realize you need to know which strategies to achieve “techno-social system transformation” have the best shot at moving the needle for gains in student achievement.

    You smile as three question pathways appear before you:

    What if you, ask not—“How do we get there?” but instead, “Where can we get from here?”

    What if instead of setting top-down goals, you collectively envision a broad direction and cultivate an evolutionary mindset among staff by asking “Where can we get from here?”

    Leadership, in its truest sense, is not about extracting from people; it’s about enabling people and teams to move forward by fostering a sense of collective empowerment and community. Hierarchical authority as it is in schools, however, tends to evoke compliance, not foster commitment. Commitment and collaboration will take your community farther than compliance so we must rethink our policies to motivate rather than constrain, drive change from within rather than enforcing it from above.

    What if you elevated staff and students into active agents of change and ruthlessly went after systems and processes that are diverting energies to administrative Yak Shaving over student learning and support?

    A pivotal first step towards meaningful progress is to engage everyone in collective inquiry @ system and process redesigns. Students and staff should be designing technology innovations, not just implementing them. Encourage teams to question deeply held assumptions, challenge the “we’ve always done it that way” mentality, and examine systems and processes that are too often frittering away our most precious resource — human brain cycles.

    Daisy chained, pieced together systems lacking stakeholder input from day 1 get put into place in ways that may seem locally efficient (for the IT Dept, Office staff, Admin) but make yak shavers of the users these systems are ostensibly supporting.

    What if you deliberately re-balanced your digital ecosystem toward high touch support?

    More than anything, we need to ensure that inquiry and experiments in digital transformation do not create an onerous burden for our community but instead provide meaningful, user-friendly, and beneficial change. Computational kindness, a concept that refers to the way we design and use technology in ways that are considerate of human factors, should be at the heart of our endeavors. This shift toward a “user focus” prioritizes high- touch integration support and proactive problem finding alongside the “reactive problem solving only” style of support that is the relatively prevalent norm.

    By turning this inquiry into action we are in much better shape to write the next chapter.

    Not So Hot for Teacher?

    Disruptive Classroom Technologies: A Framework for Innovation in Education by Sonny Magana, Corwin, 152 pp., $29.95


    To doubt everything or to believe everything are two equally convenient solutions; both dispense with the necessity of reflection. Jules Henri Poincaré (1854 – 1912)


    NOTE: I’ve heard it said that great writing is ‘clear thinking about mixed feelings,’ and I have a lot of them after working through Sonny Magana’s book and the research and marketing behind it.  As an experiment, I published this post and then published a follow up post after I saw Magana speak about his book in person at the ELMLE conference in Budapest. I wanted to be open to changing my mind if I was misunderstanding him or his work etc., The follow-up post is here.

    NOTE2: By the way, the title of this post is a “riff” off of Magana’s “rock and roll!” related storytelling/style; that at some level the genesis for the book started around a campfire hearing Eddie Van Halen for the first time as a young man learning guitar.


    What follows builds on my previous post where I wondered aloud if anyone had any evidence or data on technology’s positive effects on student achievement? I look at Magana’s work in the context of the wider Edtech zeitgeist and examine it not just for what it contains, but what it does not contain, how it is marketed, and who it is marketed towards.

    By the end, I hope readers will not only better understand the issues Magana addresses in his book, but also hope you will be more confident in making an informed judgement when hearing your own heads of school and principals offer solutions to the challenges of technology integration.

    First, my conclusions:

    Magana’s framework is itself sound— (I know, I created one largely identical to it a decade ago as an MYP IT teacher.), so one can argue it could be an improvement over SAMR, Triple E. TPACK, etc., but the problem is that for generalist teachers, it’s akin to putting a new stereo in your car to fix a faulty transmission.  As “Julie’s” review of the book on Amazon.com explains perfectly: (click the review to open it in a new window to read)

    Despite claiming “It’s important to refrain from assigning any kind of blame” in promotional pieces for the book, Magana’s claims teacher’s “tell and practice” model of teaching is the reason technology’s effect on student achievement is so “dismal.” He says it again, and again and again, over, and over in different ways. It’s most notable because of the contrast: Magana has nothing at all to say in his book about how leadership, policy, school programming and other actors actions or inaction around technology and teaching and learning bears any responsibility for what is happening in classrooms. I don’t mean he doesn’t focus on it, I mean he doesn’t say a word. I don’t understand how you get teachers to follow your framework if the first thing they need to do is get themselves out from underneath the bus.

    Magana’s research partner, John Hattie, blurbs the book and seems to be saying the opposite, claiming that understanding why performance is so low is “critical”. I don’t get the sense that either Hattie or Magana understand very well what happens when you approach people and tell them “you’re doing it wrong,” especially without acknowledging/affirming first what they are up against that is completely outside their control.

    Magana points to Hattie’s Visible Learning data which claims “computer technology” as having effects underneath the zone of desired effects for the past 50 years.  If this type of research and technology integration has been his “life’s work”, the lack of explanation, pushback or questioning of Hattie’s data, methodology or vague categorization of what exactly Hattie supposedly measured with regard to “computer technology”, seems incongruent.

    In a promotional piece on Magana’s website written about a school that implemented his T3 framework, the actual changes made to implement it could only have been done by Administrators, not teachers. The piece claims success came from the provision of tech training for teachers through a “Curriculum Camp” and allowing demand from teachers to drive tech choices/integration instead of top down decision making. This does not square with the claim that the problem with tech failure stems from “tell and practice” teaching methods. What this piece actually demonstrates is that technology sprayed into classrooms without adequate teacher training is going to result in low teacher efficacy with technology. You have to change the admin approaches first, not the other way around.  Nowhere in Magana’s book are administrators asked to be responsible for these types of changes, yet they are front and center in the “success stories?”

    Corwin’s stable of authors all blurb the book effusively on the Corwin site, on Amazon, LinkedIn, Sonny’s website, etc., without disclosing that they are all fellow Corwin authors. How is this different than Amazon product reviews where the financial incentives/conflicts of interest are not disclosed? If this kind of intra publisher back scratching is common practice, so be it, but it seems contrived.

    —————————

    “Where are the nuts and bolts?”  

    For two former teachers and tech integrationists who’ve no doubt shared many of same experiences in schools, I draw different conclusions than Magana does about the root cause of low impact technology integration. I began writing about these realities in TIE back in June of 2019. I called some of the phenomena Trickledown Edtechonomics, the Edtechochamber and Kabuki Integration.

    During the decade and a half plus years I taught, coached and lead Edtech programs in several schools and countries, I worked with administrative leadership who more often than not had a limited grasp of technology but could both micromanage and starve IT programs of attention simultaneously; no small feat. My hope in publishing this review is to offer my experience so you can make up your own minds what you think makes sense as the best next step to invest scarce time and resources in your own school. On to the review.

    The studies the book is based on some consider “Pseudoscience”

    One cannot review Magana’s book without first reviewing the material on which Magana bases it on, which is the work of Australian researcher, John Hattie. 

    Hattie’s partnership with the educational publisher Corwin (both Hattie’s and Magana’s publisher) is to develop professional publications and learning workshops.  Hattie has co-authored about twelve different books since publishing the original Visible Learning book in 2009, all variations on the same theme and all containing the same highly controversial analysis as a starting point.  One can find Visible Learning books for math, literacy, K-5, science, teaching, and a host of other spinoffs, the most recent being Magana’s book.  

    There are many critics of Hattie’s work and it’s conclusions, but the core complaint is that the work is unscientific and his meta-methodology draws conclusions that simply cannot be drawn. Another is that Hattie’s work facilitates the rise of the guru, one who outlines how things could be and provides aspirational descriptions of a utopian future if we just do the work…often without any consideration of how the labor involved in the new work will be “paid for” and by whom.

    ————————————

    The Role of Leadership, Teachers and Solutions in Technology Integration

    Role of Leadership

    Any school that believes the use of technology can improve instruction must find a way to provide training for teachers and opportunities for them to practice and prepare technology enhanced lessons.

    If they can’t or don’t, then school administration should be held responsible for the failures and no one else. Otherwise, what does their “leadership” even mean?  Who is hiring all these “tell and practice” teachers Magana and Hattie say are mucking everything up?  Who is setting and directing the schedules that enable or disable the collaborative planning necessary to coordinate such “transformative education frameworks?” Who is controlling the PD budgets? The management of the IT department?  The overall school culture?  

    It’s not teachers. 

    At best it is disheartening when you see leadership responsibilities foisted on teachers who have zero power to make the programmatic decisions that would enable and increase the possibility of success for technology integration.

    In a separate TIE article, I argue this behavior is a deeply ingrained pattern of deflecting responsibility that goes well beyond Education and I offered a parallel with the 737 Max disasters where the pattern of Boeing leadership blaming pilots and distracting attention from systemic issues led to the accidents.  Hattie and Magana’s type of “help” is music to administration ears because it eliminates any need for changes to school programming and policy, administrative leadership style and accountability or rebuilding for high-touch versus high-tech support

    Nearly everyone would agree that Edtech has been successful in getting kid’s parents connected to the school, making student assessments viewable online, enabling endless variations on digital teaching, made many forms of collaboration a breeze, survey data collection is now easily done, the list goes on. Edtech’s successes are in command and control, communication and collaboration among teachers, but this is largely digital teaching, not digital learning, and thus it’s not really aimed at student achievement.  Magana does not address this or make any distinctions about what exactly he’s talking about when he talks about “computer technology.”

    Schools have been successful with this kind of digital teaching, and I think that’s why more and more you’re seeing schools trying to commingle the success of command and control tech and sell it as part of “digital learning” that is benefiting students. It’s a very convenient conflagration for schools to make, sort of like digital “Kleenex”, but everything being lumped together makes real problem solving much more difficult.

    Most schools have some kind of marketing for Information Technology, descriptions of their aim to provide 21st century, student centered learning and some even have a scope and sequence/curriculum for digital learning, a makerspace, etc..  On close inspection, a much smaller number of schools actually have an operational vision, processes, expertise and leadership to make it all function for powerful discovery and learning for students.

    Underneath the high visibility, low impact provisioning for students is in large part I think the pernicious myth of the digital native.  This nearly 20 year old, evidence free myth was started by Marc Prensky (another Corwin author) and I would argue one of the myth’s most significant effects was that it gave school administrators a rationale and cover for minimizing time and resources deployed to train staff and students on the devices they were pushing into classrooms. 

    Which has lead us to the reality of much of Edtech in the classroom, Kabuki Integration.  This is when culture hasn’t changed because no skill-sets nor mindsets were changed:  New boxes, old ideas.  Magana calls it “technology rich and innovation poor”, I call it FOMO and virtue signaling over virtuosity.   Whatever you call it, it is high concept performance art; the expensive hardware and software is all there, but the critical bits behind it all, the “mindware”, is largely missing. Without having done the work to create a functional digital culture, absent a user focus and the requisite socio-technical feedback and iteration processes, many of today’s Edtech implementations are the equivalent of giving teachers chainsaws:

    It all depends on how teachers use it. We don’t buy a chain saw for every teacher. If we did, a few teachers would do brilliant work with the chain saws, a few others would cut off their thumbs, and the vast majority would just make a mess.” Dr. Gary Stager

    So in a sense, Magana is right in that teachers would be better teachers if they were also better technologists, but what is interesting about Stager’s quote is that we in fact have given chainsaws to almost every teacher, many times with only the barest minimal of instruction/support in how to use it. The result?  A mess.  What else should we expect? 

    Teachers

    We’ve been steadily increasing the amount of operating systems, apps and hardware every teacher and student must know each year.  Our orientations and PD include a tiny fraction of the training teachers eventually piece together on their own just to stay afloat, let alone innovate. In my last school we had over a half-dozen major software platforms staff needed to navigate and that didn’t even include any “learning” apps for lessons, etc., that was just for infrastructure, grades, curriculum, communications, storage, etc..

    Why aren’t teachers efficacious at imparting digital learning skills even when they have integration support? Because the tech integration process into units/lessons, the functional integration system and mechanisms that connect a schools digital learning “aspirations” to actual classroom activity are often completely absent or inconsistent at best in all but the smallest percentage of schools, even the “better” schools.  And this floundering is as at least as much or more the result of programming choices by administrators, as it is the way teachers teach, and Magana has nothing at all to say about this in his book.

    There is no shame in being an “Average user” as without continual access to training and knowledge, without being told that it’s not worth pursuing a certain course of action because there’s a non-obvious roadblock that leads to negative results, without someone to tell them they should try procedure X in this specific step because “it just works better when you do it this way,” everyone struggles.   Getting access to this kind of hard earned tech knowledge and skill is an enormous performance advantage and that’s why it’s such a shame that so much tech is rolled out with so little time devoted to coaching and integration support. 

    Also mentionable, in teachers defense, regarding the common refrain from the school community peanut gallery that “The kids are just sitting there on their devices watching/doing X instead of doing the work in class…”  To suggest that a teachers inability to defeat the work of professional psychologists, behaviorists, gamification experts, and all the other people paid to make devices, games and social media addicting is somehow the fault of the teacher is at best irksome.

    Solutions

    Magana is correct that we’re putting computers and other technology in a school system that was designed for a totally different epoch. In part, we’re still living under the legacy of the blackboard, the overhead projector and pencil and paper, technologies that required presentation bit by bit…which is why it had to be divided into curriculums, subjects, assignments…where children then had to be organized into age groups and rows because what could be taught was restricted by the conditions under which the knowledge was disseminated.  

    Today, knowledge dissemination is largely the reason “computer technology” is assigned to students to use in schools—most often it’s used as an efficient content delivery and assessment system; and it’s prescriptive, not imaginative. It does things to children; rather than empower them to do things that are important to them.  Tech use in schools is largely about following rules and copyright, finding the right answers, consuming in the basic ways what you’ve been told to consume; it’s the way you process and turn in assignments.  Magana is correct that schools generally remain at this type of “translational”, surface learning.

    Magana’s recommendations are in sync with the feedback I’ve gotten from students over the years is that information technology has been the most beneficial to students as an autodidactic launching pad; enabling self determined, independent learning.  Unfortunately, schools, leaders and teachers today are ill prepared, and often hostile towards this type of learning as it requires an entirely different approach to “School.” And no, you cannot single teachers out as the resistance, most I have worked with would love to loosen up how and what they teach, but parents, school leadership and even students often reject these “new teaching methods”.

    As far as new ways of doing “School”, teachers largely do not seem to have the support systems necessary to re-conceptualize their educational roles and the requirements placed upon them. Whether it’s Magana’s framework or another, absent change at an administrative level that not only acknowledges the need for teacher training/support, but actually devotes adequate (ongoing) resources toward it; creating the culture, calendaring and communication systems to support the collaboration it requires, godspeed to you in “disrupting Education.”

    Assuming the Status Quo in Schools Stays Pretty Much The Same (it’s a safe bet), What Might a Truly New Framework for Digital Learning Look Like?

    So, if the computing “grammar” and ecosystem kids experience in school, its structure and constraints, stand in the way of the real possibilities computers and the internet represent for learning, what then? 

    Outside of the school environment, digital tools can offer an incredible breadth of experience in a tiny footprint, — IF and it’s a big IF, you know how to use IT yourself and have the ability and patience to guide others in how to use IT. 

    Assuming a person had the skills and patience, what might be possible?

    What if you set schools aside completely, forgot about them as part of digital learning until the Magana’s and the Admins and the teachers of the world get their priorities and responsibilities worked out, and instead you focused on cultivating one of the most accurate (and uncontested) predictors of student achievement: parental involvement in their child’s education? 

    In other words, what if you were to design a system that was about learning with technology, not teaching with it; acting as the curator and coach of students’ and parents learning experiences together? e.g., A framework that includes dedicated “mindware development” for digital learning, rather than focusing on the process and devices and apps for digital teaching which is a different animal altogether?

    This way you could imprint the better angels of what technology is useful for and ingrain the right types of “screentime” from the start. Young children would then have a useful tool that follows them through the rest of the their schooling, not a debilitating distraction as many children today seem to relate primarily with devices.

    Perhaps technology is best learned as an autodidactic launchpad, not taught as the way to turn in assignments?

    I will have to generate some data on that idea.