Deep Dive: Cutting that Gordian Knot

Olivia Carter

Alright, let’s set the stage here. Colleges and universities are standing at this massive crossroads, right? They’re deciding whether to go all-in on cloud-native ERP systems like Workday or Oracle NetSuite. These platforms promise the world—agility, automation, real-time data—that whole shiny, modern ecosystem.

Mark Putnam

Oh, they do. They’re game-changers in some ways, Olivia. But here’s the kicker: if you migrate to these systems without addressing the underlying complexity first, you're effectively just moving the mess to a much... shinier box. On the surface, it’s progress. Underneath? Not so much.

Olivia Carter

Right. So it’s like you’re just kicking the can down the road, but now the can costs more. Let’s be real, though—this isn’t just about software, is it?

Mark Putnam

That’s right. It’s not just the technology. It’s the convoluted systems we’ve built over decades: customizations piled on top of customizations, technical debt no one wants to untangle, workflows so bloated that no one remembers why half of them exist. It’s, uh, it’s what Andy Kyte famously called the Gordian Knot.

Olivia Carter

Okay, hold up—Andy Kyte? The guy who brought a... what was it? A scimitar on stage?

Mark Putnam

Yes, a literal scimitar! It was—

Olivia Carter

Wait, was that just for show? Or, like, was he trying to become the tech world’s Zorro?

Mark Putnam

You’d think, right? But no. It was a metaphor, and a striking one at that. He used it to emphasize that digital transformation isn’t just about adding shiny tools to your tech stack—it’s about having the courage to cut through this, uh, tangled web of inefficiency.

Olivia Carter

The Gordian Knot idea—yeah, I get it now. It’s like, all those decisions people made to “fix” issues without rethinking processes. And now, it’s just this mess of patches, right?

Mark Putnam

That’s right. And that’s the problem. Most organizations don’t stop to ask the hard questions. Why does this workflow exist? Does anyone actually benefit from it? What happens if we... cut it altogether?

Olivia Carter

Oof, and people avoid that because it’s hard. Easier to blame the system and just, I don’t know, keep bolting on fixes?

Mark Putnam

Right. But the truth is, no ERP—no matter how advanced—is going to save you if the underlying foundation is cracked. Institutions have to rethink how work is structured, how decisions get made, and strip things down to what’s essential—all before hitting, uh, deploy.

Olivia Carter

So, here’s the million-dollar question: are they actually doing that? Or are we stuck in this loop of, “new system, same problems”? This whole ERP evolution still feels like a spiral we can’t escape. Institutions keep chasing the tech, but they’re not really addressing the complexity. How did this cycle even start?

Mark Putnam

It’s, uh, it’s an interesting journey for sure. Back in the early days of ERP, we had what we now call the Build-It generation. People literally wrote their own systems from scratch. It was a lot of freedom and creativity—but also chaos. Decisions were made on the fly, often undocumented.

Olivia Carter

Wait, so it was just... “build it now, figure it out later”?

Mark Putnam

Exactly that. The motto back then could’ve been something like, “Code it today, deal with the consequences tomorrow.” We built flexible systems, yes, but those systems were fragile, loaded with, uh, dependencies no one could fully explain. We moved fast but left behind a legacy of landmines.

Olivia Carter

Okay, cool, so we started with chaos—and then what? Did someone, like, step in and say, “Hey, let’s clean this up”?

Mark Putnam

Not quite. The second-gen era brought what we call Buy-It systems. Pre-packaged software became all the rage. Instead of building our own ERPs, we started buying them.

Olivia Carter

Oh, that sounds like things should’ve calmed down, right? Like, buying instead of building has to be easier.

Mark Putnam

You’d think. But no. The first thing everyone did after buying these systems off the shelf was, well, customize them. Like, heavily.

Olivia Carter

Hold up! So they just... bought these polished systems and then bent them back into their old ways of working?

Mark Putnam

That’s exactly what happened. It offered short-term wins, sure, but it just added new layers of rigidity and fragility. We fixed one set of problems and created another—problems that would haunt us for years.

Olivia Carter

Okay, so then someone must’ve been like, “Alright, let’s stitch this all together”?

Mark Putnam

And that’s the third era—Integrate-It systems. Institutions started moving toward, uh, best-of-breed solutions. Each area—finance, HR, procurement—adopted specialized tools. Then we stitched them all together with integrations.

Olivia Carter

So everyone’s using “the best tools,” but now you’ve connected them with duct tape?

Mark Putnam

Right. Except the duct tape was “data warehousing.” Every integration added complexity, every connection created, uh, new dependencies. Just getting a basic operational report sometimes took weeks—or even months.

Olivia Carter

Wow. So Andy Kyte’s whole “complexity gets engineered” thing—it’s been happening for decades, huh?

Mark Putnam

Absolutely. Complexity isn’t accidental. It’s engineered, one decision at a time. And unless someone has the courage to intervene—to ask tough questions and make hard cuts—it just keeps snowballing into the next generation of systems.

Olivia Carter

And now here we are. Legacy systems groaning under the weight of all that history. It’s like trying to play Jenga with skyscrapers, right?

Mark Putnam

That’s right, Olivia.

Olivia Carter

So, now we’re getting into what you’ve been describing as the fourth generation of ERP systems, right? Things like Workday and Oracle Cloud—are these really supposed to be the ultimate answer to everything we’ve been wrestling with?

Mark Putnam

That’s the idea. These systems are designed for adaptability. We’re talking low-code automation to work faster, composable architecture built to evolve, and even AI tools that can learn from data to improve processes on their own over time.

Olivia Carter

Uh-huh. Sounds pretty fancy. But, Mark—real talk—if they’re so great, why does it feel like everyone’s still so cautious about jumping in?

Mark Putnam

Because, Olivia, the technology is only part of the equation. If you take all your old baggage—outdated processes, unnecessary steps, and overcomplicated workflows—and dump them into a shiny new system, well... you’re just burying that system’s potential. These tools can do a lot, but they can’t think for us. They can’t simplify chaos.

Olivia Carter

Okay, so they’re like... mirrors. They reflect what we bring to the table?

Mark Putnam

Exactly. If we bring clarity—streamlined, intentional processes—they shine. But if we bring clutter, they just carry that forward. And honestly, a lot of organizations still haven’t recognized how critical this transformation is. They think the software will fix everything, but the truth is, it’s a partnership between the tool and the people using it.

Olivia Carter

Okay, but here’s the big question—what’s stopping us? Like, if these platforms are so powerful, what’s the holdup?

Mark Putnam

It’s fear—fear of change, fear of cutting too deep. People get attached to the status quo, even when it’s inefficient. And then there’s the complexity of the rewriting process itself. Asking questions like, “Why do we do it this way?” or “Can we eliminate this step?” That takes courage. It’s not easy to rethink everything, especially when it’s been done a certain way for decades.

Olivia Carter

And I bet some folks are like, “Hey, let’s just automate what we’ve got, and then we’ll figure it out later.”

Mark Putnam

That’s a common pitfall. Automating complexity doesn’t solve the problem—it just makes it faster. The truth is, these platforms are a moment of truth. They offer us the tools to transform, but transformation isn’t guaranteed. It requires a whole new mindset—one that’s willing to rethink and redesign from the ground up.

Olivia Carter

So, the question isn’t just “What can these systems do for us?” It’s more like, “What are we willing to let go of before we start?”

Mark Putnam

Correct.

Olivia Carter

So, Mark, if it really comes down to letting go of the clutter before we begin, what does that process actually look like? You’ve been saying it starts with simplifying, but why is that such a hard step for most organizations?

Mark Putnam

Because it’s easy to overlook. Simplification doesn’t sound exciting, Olivia—it sounds tedious. But the truth is, most processes we’re automating today? They’re relics. They’ve been around for decades, never questioned—just... repeated. The first step has to be asking, “Why does this exist? Who benefits? What happens if it’s gone?”

Olivia Carter

So basically, you’re saying the real transformation happens when you Marie Kondo the system?

Mark Putnam

Exactly, though I might swap tidying up for ripping out unnecessary steps. This isn’t about making processes neatly arranged—it’s about cutting to the core. Anything that doesn’t serve a real purpose should go, because carrying it forward just creates long-term debt.

Olivia Carter

And speaking of debt—those “shadow customizations” you’ve mentioned before. Every time someone tweaks something, they’re basically signing up for future problems, right?

Mark Putnam

Spot on. Customizations can feel like small wins, but they’re like shortcuts that cost you later. Every deviation from the standard has to be justified—like a financial transaction. You don’t spend on a whim without knowing the long-term cost. It’s the same with ERP systems. Every new customization is essentially borrowing against your future readiness.

Olivia Carter

Okay, so stop tweaking for the sake of tweaking. Got it. But let’s talk about the people behind this. What do ERP teams need to do differently if they’re supposed to keep up with this whole transformation?

Mark Putnam

They need to think beyond technology. Technical skills are important, but not enough anymore. ERP teams today have to think like process engineers. They need to understand workflows, how people interact with them, and how those workflows impact institutional goals. It’s not about “delivering solutions” quickly—it’s about asking better questions before building answers.

Olivia Carter

Questions like, “Why are we even doing it this way in the first place?”

Mark Putnam

Exactly. And here’s the thing—you’ve also got to prepare these systems to work with AI down the road. AI thrives in organized, logical environments. If your workflows are chaos, AI’s just gonna magnify the mess. Clean, simple processes are the foundation for intelligent automation to actually work.

Olivia Carter

So the bottom line is, if we skip all this work upfront, no ERP is gonna magically save us. It’s like giving a turbo engine to a car stuck in traffic—it doesn’t fix the gridlock, right?

Mark Putnam

Exactly, Olivia. These platforms are powerful tools, but the tools only reflect what we bring to the table. If we bring clarity and simplicity, then yes, their potential is unlocked. But if we bring clutter? We’ll just bury that power under another generation of bad decisions.

Olivia Carter

That’s brutal... but true. So, what’s next? Do we just need better leadership driving all this change?

Mark Putnam

This goes to the heart of what good CIO leadership should be, not leadership by authority, but leadership through influence and trust.

Olivia Carter

You know, Mark, thinking about what you said earlier about leadership, it feels like ERP systems aren’t just about technology—they’re shaping how organizations make decisions, structure workflows, and even build trust with users. They’re more like the scaffolding for everything we do.

Mark Putnam

Exactly. They’re the architecture of trust in an institution. And because of that, this moment—this move to 4th generation platforms—it’s a rare chance to rebuild. But only if we’re willing to tackle the complexity we’ve normalized over decades.

Olivia Carter

And that’s where the leadership part comes in, right? It’s not just, “Click deploy and call it a day.” It’s about guiding teams to rethink what’s essential and what’s just... noise.

Mark Putnam

Right. Leaders who succeed in this space will be the ones who simplify first, not the ones who move the fastest. It’s about making systems lean, intentional, and ready for the future. That’s where true modernization happens.

Olivia Carter

I love that. So, the future’s not about racing to the finish line—it’s about making sure the foundation’s solid before you even start building. Honestly, that’s a hard lesson in a world that’s, like, obsessed with “go fast and break things.”

Mark Putnam

It is, but it’s the lesson that will define who succeeds in the long run. Simplification requires leadership, discipline, and the courage to ask tough questions. Those are the qualities that’ll drive meaningful transformation, not just fast implementations.

Olivia Carter

Well, there we have it. Cutting the Gordian Knot isn’t just about the technology—it’s about leadership shaping a better way forward. Mark, this has been incredible. Thanks for sharing your insights today.

Mark Putnam

Always a pleasure, Olivia. And I hope this gives our listeners some, uh, clarity on the challenges ahead—and the opportunities as well.

Olivia Carter

For sure. Alright, folks, thanks for tuning in, and we’ll catch you next time!