We’ve Tried That Before: Building Healthy Disrespect for the Status Quo

This article kicks off Signal Without the Noise, a leadership series for data, analytics, and AI leaders who want to share best practices on the harder leadership challenges like building trust, navigating culture, fostering communities, and harvesting and communicating value. In this article, Ryan Sousa explores how D&A leaders can challenge the status quo and build energy around a better path forward. Join Sousa’s webinar on July 7 for candid conversation on eliminating the power of old patterns and leaving with the mindset that “the obstacle is the way.”  

We’ve tried that before. Every data, analytics and AI leader has heard some version of it.

“That will never work here.”

“The business won’t adopt it.”

“Leadership won’t support it.”

“Our culture isn’t ready.”

Sometimes those statements are true. Organizations carry scar tissue from prior attempts at transformation. People remember the projects that overpromised, the dashboards no one used, the governance councils that faded away, the AI pilots that generated excitement but never changed a workflow. Skepticism is not always resistance. Sometimes it is organizational memory trying to protect people from repeating a familiar pattern.

But there is another version of “we’ve tried that before” that is more dangerous.

It is the version that ends the conversation before anyone asks what happened. It treats prior failure as permanent evidence instead of incomplete information. It turns history into a veto. It allows the organization to avoid the harder questions: What was different then? What has changed now? What did we misunderstand? What did we underinvest in? What conditions would have to be true for this to work today?

That is the space we are opening in the first session of Signal Without the Noise.

The session is called “We’ve Tried That Before: Building Healthy Disrespect for the Status Quo.” It starts with a phrase that shows up in nearly every complex organization. Any organization that has been through waves of transformation develops a reflexive immune system. New ideas are judged not only on their merit but on their resemblance to old disappointments.

For data, analytics and AI leaders, that creates a real leadership challenge.

Most organizations are not short on activity. They have reports, dashboards, platforms, pilots, steering committees, governance conversations and AI experiments underway. The harder question is whether that activity is creating value and whether that value is compounding over time. Are decisions getting faster? Are workflows improving? Are teams learning? Are leaders aligning around a clearer version of value? Are people becoming more confident in their ability to use data to act?

When the answer is no, the status quo often has more strength than people realize. It is not just a set of old processes. It is a pattern of belief, incentive, memory and behavior that keeps pulling the organization back to familiar ground.

I know this because I have been the resistor.

Earlier in my career, I had enough success to believe I had a pretty good sense of what was possible and what was not. After about 10 years, I had pattern recognition, experience and confidence. Those are valuable things, but they can also become a trap. In my case, they became hubris. I was not as humble as I needed to be.

That changed for me in the early days at Amazon.

I found myself surrounded by people who were constantly pushing the envelope. Many were much earlier in their careers. They had not yet been corrupted by experience. They had not accumulated all the reasons something could not be done. That gave them the freedom to believe, to explore and to test the bounds of what was possible.

I was often the one convinced that certain ideas were not possible – not impractical, not difficult, impossible.

I was wrong.

Many of those “crazy” ideas turned out to be possible. Some of them changed an industry. The experience changed how I listen when someone says something cannot be done.

Since then, I have tried to add one phrase to every statement about what is not possible: “given how things have been done in the past.”

That phrase changes everything.

“We cannot do that” becomes “we cannot do that, given how things have been done in the past.”

“The organization will never adopt this” becomes “the organization will never adopt this, given how things have been done in the past.”

“That model will not work here” becomes “that model will not work here, given how things have been done in the past.”

The original statement may still contain truth. But it is no longer a verdict. It becomes a hypothesis. It creates room to ask what would need to change, what assumptions are embedded in the current model and whether the constraint is real or inherited.

It also points to a deeper mindset shift.

I have come to see obstacles less as reasons not to move forward and more as the actual work of making progress. That is the entrepreneurial mindset I have appreciated most in startups and high-growth environments. Problems are not barriers that end the effort. They are obstacles to understand, work through and overcome.

Ryan Holiday captures this with the phrase, “The obstacle is the way.” I have found that to be more than a useful line. It is a practical leadership posture. If an organization can shift from using obstacles as proof that something cannot be done to treating them as the path through which progress happens, it is already on its way to a different level of performance.

That experience also changed how I think about the phrase “ignorance is bliss.” I used to hear it as dismissive, as if ignorance meant naivety or lack of seriousness. Now I hear something different. Sometimes not knowing all the reasons something is supposed to be impossible gives people the freedom to explore the bounds of what is possible.

That freedom matters more now than ever. New AI capabilities are dramatically expanding what is possible, but many organizations are still interpreting the future through the limits of their past. The goal is not to stay ignorant. The goal is to avoid becoming so fluent in the constraints of the current system that you stop seeing alternatives.

That is why healthy disrespect matters.

Healthy disrespect for the status quo is not cynicism. It is not rebellion for its own sake. It is not dismissing the experience of people who have been in the organization for years. It is not walking into a room and telling everyone they are thinking too small.

It is disciplined curiosity about whether the current way of working is still serving the mission.

It respects prior experience without being trapped by it. It listens carefully to why something failed before, then refuses to accept that failure as the final word. It separates the lesson from the scar tissue. It creates room for a different outcome.

It is also not naive optimism. People are rarely resisting only because they do not understand. They may be protecting capacity. They may be responding to incentives. They may have seen similar efforts collapse when executive attention moved elsewhere.

And it is not learned resignation. Leaders can see the political complexity, cultural drag, operational constraints and long memory of the organization, then quietly lower ambition. The language becomes practical, but the posture becomes defensive. We stop trying to create momentum and start trying to avoid disappointment.

Neither posture is enough.

The work is to challenge old patterns without pretending they are easy to change. That requires trust, influence and a grounded understanding of how change actually moves through an organization. It requires finding the people who still have energy for a better path and helping them see themselves in the work.

Most of all, it requires leaders to treat resistance as data.

When someone says, “we tried that before,” the wrong response is to argue. The better response is to investigate. What exactly was tried? Who was involved? What failed? Was the idea wrong, or was the timing wrong? Was there enough sponsorship? Was the workflow actually changed? Did the team have the authority, capacity and trust needed to make the effort real?

Those questions turn resistance into learning. Instead of selling change, the leader starts diagnosing conditions. Instead of pushing a mandate, the leader starts building a coalition. Instead of asking people to forget the past, the leader helps the organization interpret the past more usefully.

That is the spirit behind Signal Without the Noise. The series is not about more technology commentary. There is plenty of that already. It is about the work behind the work: the human, organizational and political realities that determine whether data, analytics and AI efforts take root.

The first conversation begins with the status quo because that is where so many efforts lose momentum. Think of how many smart people with positive intentions you work with. Intelligence, intent. These are rarely the issues. Old patterns are powerful, they can – and often do – win the day.  

Building healthy disrespect for those patterns is not about being louder. It is about being more precise. It is about knowing which parts of the past deserve respect, which parts deserve interrogation and which parts no longer deserve the authority they have been given.

Because “we’ve tried that before” should not end the conversation.

It should start a better one.