
215: The Paradox of Moving Goals
An AI-generated episode based on a human-composed blog post: The Paradox of Moving Goals
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

An AI-generated episode based on a human-composed blog post: The Paradox of Moving Goals
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
What if I told you that the team member who is constantly demanding the newest, most expensive software is actually the one doing the least amount of work? Or worse, what if you are that person? Right. Today, we're exploring this universally frustrating phenomenon. You set a goal, you map out a really meticulous plan, and you finally deliver the project. And then the person waiting for it, your boss, a client, or even just that critical voice in your own head looks at it and says, Yeah, that's not really what we wanted.
We need this entirely different thing instead. It is maddening. Suddenly, the finish line isn't just moved. It's like in a totally different time zone. It really is. So we're taking a deep dive into an article called The Paradox of Moving Goals. Right. Written by Dr. Gary Ackerman over at hackscience .education. Exactly. And I mean, just looking at your setup today, your visual backdrop is amazing. Oh, thanks. It's a... a bit chaotic. It looks like this crazy hybrid between a modern classroom and like a really
complex constantly shifting flowchart. Well, that felt appropriate because Ackerman is an innovative leader in instructional technology. Right. And that field basically exists in a state of perpetually shifting goalposts. It's just constant unyielding change. I can only imagine. It sounds like living inside a flowchart where if you fix one dependency, three more immediately break. That is the defining challenge of the role, honestly. So the goal of this deep dive today is to unpack all of that, the psychology
and the practical realities behind why these goals constantly shift. Because we need to figure out if moving the goalposts is a sign of brilliant innovation or just an excuse to avoid hard work. OK, let's unpack this. Because to me, constantly moving goals feels like like chasing a mirage in the desert. That's a really great analogy. You know when you drive on the highway on a really hot day and it looks like there's a puddle of water way up ahead? Oh yeah, the heat haze. Right. And you keep driving toward it, but you never actually reach the puddle. Just when you think
you're there, the destination shifts further down the road. And that creates a massive headache for leadership. Ackerman really grounds the conversation in that core dilemma. Which is what exactly? Well, in any organization, resources are strictly limited, right? budgets, time, personnel, software licenses. Right. You don't have infinite money. Exactly. So when someone consistently asks for new tools, right at the exact moment you fulfill their previous request, you have to evaluate their motivation. Yeah, like are they just changing
the requirements to avoid the hard work of updating their practice? Or, on the flip side, were their initial estimates simply wrong? Right, maybe they genuinely uncovered new requirements through the friction of doing the work. And that ambiguity carries massive risk. Both situations look identical on a spreadsheet. They both just look like another purchase order. Have you ever done this? I mean, I want you listening to think about your own workplace or personal projects. I know I'm totally guilty of this in my personal life. Oh, we all have that tendency. Like, I decide I'm going
to get in shape, so I buy expensive running shoes. Then I decide I can't possibly run until I have moisture wicking shirts. Of course. Need the right gear. And then I need a smartwatch to track my heart rate. I call it getting prepared, but really I haven't jogged a single mile. It's procrastination disguised as preparation, and Ackerman provides a brilliant framework for diagnosing this in a professional setting. So let's get into the case studies. Let's look at the first scenario. It focuses on a high school geometry teacher.
Okay, lay out the facts for us. Yeah. Because I remember reading this and thinking... Her requests didn't sound that crazy on the surface. Right. So she's asked by her principal to integrate technology into her lessons. The IT department gives her these repurposed laptops. Which is pretty standard for a school budget. Yeah. Enough for the students to work in pairs. And they install an older but totally functional version of the required math software. So they give her a solid starting point. But she rejects it almost immediately. She says she needs individual workstations for
every single student. Wow. And she wants the absolute newest version of the software. OK, wait. Let me play devil's advocate here for a second. Go for it. Because if I'm a parent in that district, I want my kid to have their own computer. I want them using the newest software. Sure, absolutely. That's a totally normal reaction. So why is Ackerman framing this constant rationing up of needs? as a bad thing. Isn't she just trying to get the best educational experience for her students? Well, what's fascinating here is the
crucial detail that Ackerman observed between her requests. What do you mean? The IT department actually fulfills her request. They secure the workstations. They buy the new software licenses. Problem solved, right. The goal is met. No. Once she gets them, she pivots. She decides workstations aren't enough, she absolutely must have Chromebooks. Why Chromebooks? You just got brand new workstations. Because the neighboring school districts use Chromebooks for a specific web application. Oh, so the justification completely shifted. Yes. It went from my students need individual access
to we need to match the school down the street. That is wild. And miraculously, the school manages to procure the Chromebooks. The new goal is met. Let me guess. She moves it again. She does. She claims she cannot possibly teach geometry with technology unless the school installs a smart board in her room. The goal posts are just loaded onto a freight train at this point. Exactly. But the damning part, the thing that dismantles the whole she just wants the best for her students argument, is her pedagogy. Right. How is she
actually teaching? She made those escalating demands after only a single attempt at using the previous technology. Wait, really? Just one attempt? Just once. She looked at the laptops once, looked at the workstations once. She made zero changes to her actual teaching methods. So she wasn't even trying to adapt a lesson plan for pairs of students? No. She basically threw her hands up and refused to adapt. Ackerman concluded she was just waiting for the perfect technology as an excuse. Oh, wow. That makes so much sense. She gets to say she's waiting on IT so nobody
can blame her for not changing. It's all about avoiding vulnerability. Implementing new tech means an experienced teacher has to become a novice again. And doing that in front of a room full of teenagers sounds terrifying. Exactly. By moving the goal, she maintains control and shields her ego. But for leadership, it's a disaster. Resources are just hemorrhaged. OK, so that's the excuse side of the paradox. But Ackerman contrasts this with a scenario where someone does the exact same thing, but for a good reason.
Right. The statistics teacher, her identical behavior stems from a completely different motivation. So she starts with Chromebooks, right? The ones the school already has. Yes. But the spreadsheet on the Chromebooks lacks the analytical capacity to create the complex graphs her students actually need. Which is a real objective limitation of the tool. Not an excuse. Exactly. So she tries this web -based add -on, but the interface is notoriously clunky, and it looks nothing like real professional software. So she asks for the real stuff. She does. They approve it, but they
put it on desktop PCs in a multimedia room down the hall. Oh, what an administrative nightmare. Completely. She has to fight for calendar time, march her kids down the hallway, log them into unfamiliar machines. That sounds awful. It is highly disruptive. So finally, she goes back and asks to purchase dedicated laptops with the software pre -installed for her classroom. Goalpost moved again. Chromebooks to software, software to lab time, lab time to dedicated laptops. But the underlying mechanism driving those requests
is entirely different. Here's where it gets really interesting because it's like leveling up in a video game. How so? Well, you know, you start a game and they hand you a terrible wooden sword and a garbage shield. Right. The starter gear. Yeah. You don't just pause the game immediately and demand the legendary flaming broadsword. You take your wooden sword and you fight some low level slimes. You learn the fundamental mechanics. Exactly. You figure out how to block, how to dodge. You level up and then later you face an armored dragon and your wooden sword shatters.
At that point, you're not asking for an upgraded weapon because you're lazy. Right. You need the flaming broadsword because the challenge requires it. Exactly. You've mastered the current mechanics and the tools just can't keep up with your skills anymore. That is a fantastic way to put it. Ackerman noted a huge behavioral difference here. This teacher struggled through several lessons with that clunky add -on. She actually put in the reps. Yes. She did the administrative work to schedule her kids into that inconvenient computer
room. So she used what she had. to its absolute fullest. Exactly. Before determining it didn't meet her needs, she proved it through active application. It's like taking a sports car to the track to find out where the suspension actually fails. Her shifting goals were a byproduct of productive adaptation. The practice outgrew the tools, so the tools needed to evolve. Okay, but as a leader, how do you deal with this? Because you can't read minds. Right. You've got resources on the line. You can't put your team through a lie detector test. How do you know if you're
dealing with a geometry teacher or the statistics teacher? If we connect this to the bigger picture, Ackerman's solution to this dilemma is surprisingly elegant. It cuts through the noise of the requests. I'm all ears. What's the secret? A leader simply needs to observe actions and ask one ruthless question. Is it being used? Just is it being used? That feels almost too simple. The simplicity is its strength. Ackerman argues you must continue to support the individual who is actively using
the existing technology. Regardless of its flaws. Exactly. Because it's only through the struggle of using the current imperfect system that anyone generates real data on what's needed next. So you evaluate the struggle itself. Is it productive struggle or pointless thrashing? Right. The statistics teacher earned the right to ask for an upgrade because she provided undeniable proof that she'd fully utilize it. Whereas the geometry teacher's requests were just built on hypotheticals and pure envy. You do not fund hypotheticals. So what does this all mean for you, the listener? I want to challenge you to audit your own goals
right now. That is a great exercise. Are you sitting back, just waiting for the perfect conditions to start that next project? Or are you pushing the limits of the tools you already have? Because Ackerman's final verdict is unwavering, believe the people pushing the limits. Meet their moving goals without hesitation. But the ones waiting for perfection? No, with absolute certainty that they will simply never be satisfied. Man, that is a profound shift in perspective. To summarize this whole journey, Ackerman's case studies teach
us to look past the request for new tools. You have to examine the behavior of the person asking. Exactly. And this framework isn't just for school administrators. Whether you are managing a team, launching a business, or trying a new hobby. It applies everywhere. Recognizing the difference between productive adaptation and disguised procrastination is basically a superpower. It tells you when to double down and when to close the checkbook. It really is a powerful heuristic. But, you know, this raises an important question, something I'd love to leave you with to explore on your
own. Oh, I like the sound of that. We've thoroughly established that waiting for perfect tools is a dangerous trap, right? Definitely. But at what point does having too many resources or having every request instantly fulfilled actually stifle our ability to innovate? Oh, wow. That is a fascinating flip. Think about the statistics teacher. If the school had an unlimited budget and just handed her the perfect laptops on day one without any struggle, would she have developed the same deep understanding of her curriculum? Exactly. If
we always get exactly what we want right away, do we lose the creative problem -saving that only comes from struggling with imperfect tools? Like the friction isn't just an obstacle. The friction is the path itself. It's the resistance training that builds your creative muscles. I love that. So the next time you deliver a project and someone moves the finish line, look at their shoes. Check for mud. Yes. See if they've been walking through the mud with you, pushing the boundaries of what's possible, or if they've just been sitting on the sidelines pointing at the horizon. Because the truth is in the trenches.
Absolutely. Because if they are in the trenches doing the work, moving the goalposts might be exactly what you need to find the real breakthrough. Until next time, keep digging deep.
Nobody is credited on this episode yet.
An AI-created episode based on a human-composed blog post: Changing Vision of Technology Literacy
An AI-generated episode based on an AI-generated blog posts based on an old microblogging post: The Inquiring Technologist: Why Great Solution Design Begins with "Too Many" Questions
A brief AI-generated episode based on a human-composed blog post: Gathering Organizational Intelligence for Network Security
An AI-generated episode based on a human-composed blog post: Models of Technology-Rich Teaching
An AI-generated episode based on a blog post designed for students in a community college course. Concepts of Operating Systems