When Silence Signals Trouble

Olivia Carter

Hey everyone, welcome back. I’m Olivia Carter, here as always with my co-host, Mark Putnam. And today, I have to say, our topic might sound almost... mundane at first. But, honestly, the most dangerous moments in tech aren’t the big, blowout failures. It’s those polite, quiet meetings that lull us into thinking everything’s fine when, under the surface, things are seriously going sideways.

Mark Putnam

That’s exactly right, Olivia. The rooms are quiet. Nobody’s raising their hand. And in those moments, what you’re really seeing isn’t consensus—it's the early warning sign that something fundamental is being missed. Decades of ERP work taught me this: the collapse of a major project doesn’t begin in crisis, it begins in silence. I saw that firsthand at Athens Regional Hospital. The electronic health system rollout—every meeting was calm, people nodded along, not a single flare-up. But nobody voiced their growing doubts. Leaders stopped surfacing bad news, either to avoid the CEO’s reaction or because they thought it wasn’t their place. By the time the board was informed of issues, patients were already being missed. It was devastating.

Olivia Carter

Yeah, that story just gives me chills. And, to echo what you said, I remember investigating a fintech startup for TechCrunch a couple years ago. They were scaling so fast, all their dashboards were green—everyone so proud, like, "Look, we’re successful! We’re humming along!” But what we found was... well, brutal. People weren’t raising red flags for fear of looking uninformed or slowing things down. By the time the alarms went off, there were major system outages, customer trust just evaporated. I guess what we’re really saying here is: silence isn’t harmless. It doesn’t mean things are working. It’s often where the real risk pools, hidden out of sight.

Mark Putnam

It is. Silence is not alignment—and that illusion of progress can be absolutely fatal in these projects, especially in ERP design, where every early conversation shapes months of downstream work. When those rooms “feel” efficient, you should probably worry.

Olivia Carter

So, let’s dive into how that risk unfolds. I mean, one “simple” decision at the start—a security toggle here, an extra approval step there—it doesn’t just change a settings menu. It unleashes this domino effect you don’t see coming, right?

Mark Putnam

That’s the heart of it. I can recall a moment when our finance team requested a harmless-seeming tweak—an additional approval step for purchasing workflows. Everyone nodded, sure, it seemed wise. Nobody mapped out what it would mean for other teams or during peak cycles. Soon, payroll processes slowed to a crawl, people waited days for routine approvals, and the system was blamed for being “slow,” but it was our own design decision, rippling through places we hadn’t visualized at all. It’s the classic story: tiny pebble, massive wave.

Olivia Carter

And it’s so tempting—not just in higher ed, but I see it in startups, too. You patch one thing quickly to fix a visible pain, but the longer-term costs? Totally hidden. So, how do we actually visualize those downstream impacts, Mark? Have you found frameworks or exercises that help catch those ripples before they spread?

Mark Putnam

What’s worked best is forcing ourselves to ask, every time—what will this change do two or three steps from now? Who else does it touch, which dependencies will be hit? We’d sometimes use something as simple as a whiteboard, mapping second- and third-order effects. I wish I’d done it every time—we’d have saved a lot of pain. But you need the right leadership environment for people to speak up, to question, and to not just accept a quick “yes.” Otherwise, these dominos start falling and, by the time the impact is seen, you’re deep into organizational pain.

Olivia Carter

I love that—we’re definitely circling this idea of consequences not being linear. Let’s dig into the “Cascade of Consequences” framework because this is where it gets both scary and clear. You wrote about the five levels, right? It all starts with that “easy yes”—someone asks for an extra approval or data field, everyone nods, meeting ends, nobody questions the dominoes set in motion.

Mark Putnam

Exactly. So, it begins with that easy yes. Next, local friction shows up—maybe a task that takes longer, someone frustrated at an extra click—but it gets dismissed as a minor annoyance. Then comes the third-order effect: another department gets hit, maybe misses a deadline or an integration fumbles. Trust starts leaking out. No one present at the original decision feels responsible, yet the pain is real and spreading.

Olivia Carter

And then those fourth- and fifth-order effects—those are the ones that terrify me, honestly. The hidden problems that only emerge when everything is under stress, like month-end, or after go-live when the system’s really put to the test. Suddenly, that “tiny” tweak means queues are ten times longer, people invent workarounds, data integrity slips, and the whole system is, at that point, like, fundamentally compromised.

Mark Putnam

That’s how deep it goes. Fifth order? That’s full-on institutional breakpoints—burnout, shadow IT, declining trust, cultural retreat. Everyone absorbs pain in silence because fixing the system now costs more than if choices had been scrutinized in the first place. What’s worse, most leaders assume those risks will get caught with testing or that consultants will fix them. But if those early “tiny” decisions go unscrutinized, you’re basically building fragility into the institutional DNA. That’s what we’re up against.

Olivia Carter

And this isn’t just an ERP thing, right? It’s everywhere—universities, hospitals, anyplace where processes get patched and nobody asks, “Wait, what’s this really going to cost us down the road?” That’s how tiny, local decisions morph into culture-deep weaknesses.

Olivia Carter

Let’s talk about a myth that drives me nuts: just getting people “in the room” means you’ve got engagement. If only it were that easy! All the right titles might be on the meeting invite, but if no one’s actually asking hard questions or pushing back, it’s just theater, not real collaboration.

Mark Putnam

Absolutely. Hierarchy often discourages honesty, especially if people feel challenging a design will be seen as resistance or incompetence. I’ve seen leadership teams, consultants, and even business owners prioritize polite agreement just to keep a project on schedule. At that big public university’s HR rollout—consultants wanted timeline wins, so discussions were quick, dissent was rare. Problems only surfaced at go-live. By then, it was far too late for easy fixes.

Olivia Carter

It’s that difference between cosmetic alignment and genuine scrutiny, right? Real engagement means surfacing risks, even if it’s uncomfortable or slows things down. Just having a crowd in the room isn’t enough. Were people actually awake? Did anybody challenge the assumptions or just nod along?

Mark Putnam

And leadership responsibility is huge here. Unless executives insist on clarity, make it psychologically safe to question, and actually show up visibly in the trenches, silence will rule. Representation is not engagement—engagement is active, challenging, sometimes messy.

Olivia Carter

Yeah, and when you skip that real engagement, you end up with latent problems, hidden until the worst possible moment. That’s just organizational disaster waiting to happen, even if meetings felt “smooth” at the time.

Olivia Carter

Okay, so, what does it take to break that culture of silence? I feel like leadership gets repeated a lot, but let’s get real—what can execs and teams actually do to make it safe, even expected, to challenge and stress test decisions?

Mark Putnam

First, leaders have to be visibly present and engaged. At my university, I pushed for open forums and deliberate stress tests—places where people could bring up flaws before they hardened. We’d actually run simulations, map second- and third-order impacts, and challenge process owners to articulate risks. That friction wasn’t dysfunction—it was required. When people know dissent is welcomed, you catch problems early, long before they cost the institution.

Olivia Carter

And practical tools matter, too—impact mapping is huge, even if it’s just sticky notes and a whiteboard. Normalize questioning as part of every design session. Make tradeoffs and owners visible—like, annotate which team asked for each change, what it might cost, and who owns the outcome. It slows things down at first, but it builds trust and accountability. I know, I keep saying this, but: you need friction. The absence of it, like, isn’t peace—it’s risk that hasn’t surfaced yet.

Mark Putnam

I couldn’t agree more. ERP success comes from treating silence as a red flag, not a green light. Question early, dig for hidden risks, build clarity. If institutions do that, breakdowns become learning moments, not existential threats. But it starts from the top. Leaders have to model curiosity, transparency, and the willingness to slow down for real understanding—not just apparent progress.

Olivia Carter

Totally. That’s all for today, but I feel like this theme—surfacing real risks early, embracing transparency, making room for honest debate—it runs through every episode we’ve done, from negotiation ladders to AI adoption. Silence might feel productive, but it’s dangerous. Friction is your friend, even if it’s uncomfortable. Mark, thanks so much, as always, and thanks to everyone for listening. We’ll dig even deeper into the realities of institutional change in our next episode. Take care—and, Mark, I’ll see you next time!

Mark Putnam

Thank you, Olivia. And thanks to all of you for being a part of this conversation. Keep questioning, stay curious, and don’t let silence fool you. Until next time.