The Vicious Fractal of Complacency: When Leadership Trades Agency for Comfort

Complacency is one of those words we think we understand immediately—usually as a character flaw. It conjures images of laziness, low standards, or people who simply don’t care. But in the real world, complacency is rarely that simple. More often, it’s what happens when friction becomes familiar. When complexity becomes “normal.” When the path of least resistance is rewarded, risk is punished, and “good enough” quietly replaces “better.” Over time, it stops feeling like a choice at all—it feels like reality. Complacency isn’t a public-sector problem or a private-sector problem—it’s what happens when leadership trades agency for comfort. It shows up when we accept avoidable complexity and outsource our blueprint to “the way it is” or to a vendor’s roadmap, trading adaptability (and ambition) for comfort. At its core, complacency is what happens when we stop demanding better—from our tools, our institutions, and ourselves.

In 2017, I saw this up close while working for Oregon’s Department of Revenue, when I visited Microsoft’s Executive Briefing Center in Redmond. It was two days of sleek conference rooms, polished demos, and a nonstop narrative about the future of work—powered, of course, by free, barista-made coffee that was suspiciously good (too good to be free). In one session, a presenter proudly demonstrated real-time collaboration in Office 365. He described the familiar pain of “v1,” “v1_1,” and “final_FINAL” files bouncing around an organization and explained how Word in the browser solved it by allowing everyone to edit the same document simultaneously. I raised my hand and said, “So in essence, you’re taking what Google Docs has been doing for years… to solve a problem that you created.” The room got quiet. And the moment stuck with me—not because it was clever, but because it revealed a broader pattern: complacency disguised as prudence. It’s the same instinct behind the old cliché, “Nobody ever got fired for hiring IBM.” This logic doesn’t come from bad people—it comes from systems leaders build (or tolerate) that punish risk and reward predictability.

Fast forward to today, and the same pattern shows up in a thousand smaller ways. Teams is a chat and meeting tool… until it becomes a file system that actually lives in SharePoint. OneDrive is “your files,”… except it’s also sometimes the gateway to shared files, depending on how something was created and where it was saved. Links look the same, permissions behave differently, and a simple question like “where is the document?” can turn into a scavenger hunt. It all works—mostly—but it doesn’t feel designed so much as assembled. And what’s most interesting isn’t the friction itself—it’s how quickly most of us accept it. We adapt. We create workarounds. We teach the next person “the trick.” We stop expecting our tools to work for us, and we quietly accept that we’ll have to spend energy to make them work. And we stop demanding better (even when better clearly exists).

This is why I’m wary when I hear someone say, “We’re a [single-vendor] shop.” It sounds decisive, even strategic—but it often functions as a quiet surrender of agency. When you declare allegiance to a vendor ecosystem, you don’t just buy tools; you inherit their assumptions, their integrations, their tradeoffs, their pace of change, and their definition of “good enough.” Over time, your technology strategy becomes less about what your mission requires and more about what your vendor happens to be building next. And when your mission shifts—as it always will—you’re left trying to steer an institution with someone else’s roadmap—one designed to take you to the vendor’s strategic destination, not yours.

In my current organization, we are often provided technology as if it were still 2004—locked down, tightly controlled, and designed first around what might go wrong. The underlying intent is understandable: reduce risk, standardize, protect the enterprise. But too often, the result feels less like enablement and more like containment. It’s the “rounded-end scissors” mentality applied to adult work: if we blunt the tools enough, no one can hurt themselves. The problem is that when risk avoidance becomes the primary design principle, we quietly trade capability for comfort. We restrict, contain, and standardize until technology stops serving the work and the work starts bending around the technology.

And then the same complacency pattern kicks in again. We adapt. We create workarounds. We teach the next person the tricks. We normalize friction and call it governance. But governance isn’t supposed to be a tax on effectiveness—it’s supposed to be the guardrails that let people move faster with confidence. The difference between the two is leadership: whether leaders are willing to do the harder work of designing secure environments that still respect capable users, instead of defaulting to control because it feels safer.

If you’ve read anything else I’ve written, you know where I’m going: this isn’t a tool problem. It’s a leadership problem.

I’m not trying to bash any particular vendor—complacency exists everywhere. It exists in government and higher education, sure—but it also exists in the private sector, in our organizations, and in our personal lives. It’s the deferred maintenance at home. The process everyone complains about at work but no one owns. The manual workaround that becomes institutional knowledge. The “we’ll revisit it next quarter” that turns into “we’ve always done it this way.” Complacency isn’t loud. It’s quiet. It’s the slow normalization of friction.

And the most common form of complacency isn’t refusal—it’s delay. It’s delaying the decision-making for change until change is no longer a decision. Time makes it for you. A crisis makes it for you. A vendor makes it for you. The longer we wait, the more expensive it becomes to fix—and the more energy we waste adapting ourselves to dysfunction instead of designing our way out of it.

This is also why “staff don’t trust new things” is rarely as simple as stubbornness. Sometimes it’s learned behavior from being burned by half-implemented change: weak training, weak support, shifting priorities, and leadership that declares victory on go-live day while the people doing the work absorb the pain. And sometimes, candidly, it’s complacency—because learning something new takes effort, and effort feels optional when the organization has trained people that workarounds are the real system. Either way, the cure is the same: leadership that treats enablement as the job, not an afterthought.

At some point, we have to admit what all of this costs. Not just time. Not just productivity. Complacency taxes ambition. It narrows what organizations believe is possible. It turns strategy into accommodation. It trades agency for comfort until comfort becomes constraint.

Complacency also stifles creativity and innovation. When friction becomes normal, people stop imagining alternatives—they focus on coping. And there’s an economic side to this too: complacency reduces demand. When customers stop requiring more from their tools and vendors, vendors stop feeling pressure to raise the bar. The market adapts downward. The result isn’t just a vicious cycle—it’s a vicious fractal: the same pattern repeating at every level, from individual habits to organizational culture to the ecosystems we buy into.

So here’s the question I try to keep in front of myself: What’s our blueprint? If we designed our environment today—around our mission, our people, and the work we need to do—what would we build, and what would we stop tolerating?

Because if leadership won’t define the destination, someone else will. And the path you end up on will be very efficient at taking you somewhere—just not necessarily where you meant to go. So define the blueprint. Take a risk. Demand better.

You May Also Like:

• Enterprise Planning—Take the Reins
• Bhusri Returns as CEO: Can Workday Accelerate Innovation Pace?
• [Webinar] Rebuilding the Recruitment Funnel: How Technology Turns Interest into Enrollment

Originally posted by Thomas Battaglia on LinkedIn. Be sure to follow him there to catch all his great industry insights.