CHANGE CULTURE OR TOOLS BINARY BUSINESS EP BB-12

Change Culture or Change Tools First? Binary Business - BB-12

A company spent $1.2 million on an AI platform. Six months later, adoption was at 8%. The frontline employees built a workaround in Excel. They chose a spreadsheet over a million-dollar platform. That's not a technology problem. That's a culture problem wearing a technology disguise.

In this episode, I break down how to diagnose whether your AI rollout needs a culture play or a tools play first, and why most leaders get the sequence wrong because they default to whichever one they're more comfortable with.

What You'll Learn:
• Why a maintenance crew ignored a predictive system that could see failures 72 hours out — then adopted it a year later (same tool, different approach)
• The firm that spent eight months on "AI readiness" while three competitors shipped AI products
• How one company spent $200K on change management when the real problem was a UI that looked like "a tax form and a spreadsheet had a baby and nobody loved it"
• The three-question diagnostic that tells you where to start
• Why "a culture shift with no tool produces meetings — and meetings don't ship"
• Forty-seven slides and a stock photo of a handshake (the digital transformation presentation nobody needs)

🎯 Download the free Binary Decision Scorecard: https://entrenovaai.com/scorecard

👍 Like this video and subscribe for more signal, no noise.

Timestamps:
0:20 - Context: The Debate That Never Ends
2:30 - Binary 1: Change Culture First
5:30 - Binary 0: Change Tools First
8:00 - ABCD Breakdown
8:15 - Audience: Are They Resisting the Change or the Tool?
10:30 - Build: Pilot Groups vs. Minimum Viable Deployment
12:15 - Convert: Slow and Sticky vs. Fast and Fragile
14:00 - Deliver: The Three-Question Diagnostic
16:00 - The Call: Fear vs. Frustration

About William Guidry:
Will Guidry is CEO and Founder of EntreNova AI, a Houston-based Microsoft Cloud Solutions Partner. He helps operators diagnose the real constraint in AI adoption — culture, tools, or strategy — using the Binary Decision Scorecard framework.

Previous Episode: BB-11 - AI for Speed or AI for Accuracy?
Next Episode: BB-13 - Trust AI Outputs or Require Human Review?

Binary Business is a business decision podcast for operators navigating AI.

Each 10-15 minute episode breaks one AI decision into a clear binary choice using the ABCD framework: Audience, Build, Convert, Deliver.

100 Episodes. 4 Seasons. One System.

Season 1 (Jan-Mar): Who AI decisions are for
Season 2 (Apr-Jun): How systems break when AI scales
Season 3 (Jul-Sep): Where AI moves money
Season 4 (Oct-Dec): How to execute AI decisions

New episodes drop every Tuesday & Thursday.

This isn't a podcast about AI hype. It's a framework for making high-stakes decisions in a world where AI is changing the rules.

Subscribe to follow the full arc. By Episode 100, you'll have a portable decision system that works for any business challenge.

🎯 Free Resource: Binary Decision Scorecard
https://go.binarybusiness.tech/gzkqjw9n-yt-pod-bb-01

💼 Work with Will:
https://app.usemotion.com/meet/willguidry/EntreNova-Will?d=30

🔗 LinkedIn:
https://linkedin.com/in/williamguidry

Binary Business. All signal. No noise.

Transcript

0:00

A company spent$1.2 million on an AI platform. Nine months later, adoption was at 8%. The CTO said the tool works perfectly. The vice president of operations said nobody trusts it. And the frontline employees, well, they built a workaround in Excel, a spreadsheet. That's not a technology problem. That's a culture problem. Wearing a technology disguise today, change culture or change tools. First, let's untangle this. Welcome to Binary Business. I'm Will Guidry. every episode we take a real business decision, strip out the noise and run it through a binary filter, because the best operators know that the hardest problems aren't technical. They're human. Let's get into it. This is one of those debates that's been going on since the first company tried to implement any new technology ever, and the debate always sounds the same. One side says, we need to change the culture first, get buy-in, build trust, shift mindsets, then bring in the tools. The other side says, just give them better tools. The culture will follow those. Once people see the results, both sides have evidence. Both sides have horror stories and both sides think the other side is the reason projects fail. Here's what I've seen after working with companies across manufacturing, finance, and technology. The answer depends on what's actually broken, and most leaders don't diagnose correctly because they're biased toward whichever one they're more comfortable with. CTOs love tools. They can demo tools. They can measure tools. Tools. Have ROI, calculators and vendor presentations and roadmaps, HR leaders and change management consultants. Love culture. culture has workshops and surveys and transformation frameworks, and a lot of post-it notes. Neither is wrong, but one comes first and getting the sequence wrong is expensive, not oops, kind of expensive. We just set a million dollars on fire and blame the vendor. Expensive. So let's sort it out. Here's the binary. Two schools, one sequence. Here's how each one plays Binary. One, change culture first, binary one says, culture eats strategy for breakfast, and it especially eats technology for lunch. The argument is straightforward. If your people don't trust ai, don't understand why it's being introduced and feel threatened by it. No tool on earth will save you. You'll buy the platform, deploy the platform, and watch the platform collect digital dust while everyone quietly goes back to the way things were. I saw this firsthand at a manufacturing plant. They rolled out an AI powered predictive maintenance system. Technically brilliant, Could predict equipment failure. 72 hours in advance, game changing capability. The maintenance crew ignored it completely. Why? Because nobody told them the tool was coming. Nobody asked what problems they actually had, and the first time the system flagged a false positive, which was predicting a failure. That didn't actually happen. The crew chief said, see, I told you computers don't know machines. And that was it done. The whole team wrote it off, not because the tool was bad, because the introduction to the tool was bad, the culture wasn't ready. A few months later, the company brought in a change management consultant. A few months of workshops, ride-alongs and the maintenance team, small pilot program. Then they introduce the same tool, same platform, same algorithm, and adoption hits 78%. Same tool, different culture, completely different result. So culture first works when there's active distrust of AI technology, or technology in general. When previous tech rollouts have failed and people are cynical, or when the workforce feels threatened by automation. And the leadership hasn't communicated the why behind the change. Binary zero change tools first. Binary, zero says stop talking and start showing. People don't change because of workshops. They change because they see something better. And honestly, there's strong evidence for this. One professional services firm spent eight months on AI readiness surveys, town halls, training sessions, change champions, COEs, the whole nine yards. by the time they were culturally ready to deploy ai, three competitors had already shipped. AI powered client deliverables. All those months of preparation, zero AI in production. Competitor Advantage gone. Meanwhile, another firm in the same industry just deployed a tool, no fanfare, no transformation workshop. They picked one team, gave them an AI writing assistant, and said, try it for two weeks. If you hate it, we'll pull it. Two weeks later, the team asked for more licenses. The tool was so obviously better that nobody needed a workshop to understand why they didn't need a cultural change. They needed a capability change. The culture shifted because the tool was good, not because someone gave a presentation about digital transformation with 47 slides and a stock photo of a handshake. tools first works, when the existing culture is open to experimentation, when the tool delivers obvious and immediate value, or when competitors are moving and you're falling behind, and when the culture problem is actually just unfamiliarity with the tool. Hey, if this is making you think differently about your next rollout, do me a favor. Hit Like and subscribe. It literally takes one second and helps this show reach more operators who are stuck in the exact same. Now, let's keep going. The A, B, CD breakdown. let's run this through the A, B, CD framework. A is for audience. Here's the diagnostic question. Most leaders skip. Is your team resisting the change or resisting the tool? These are two completely different problems with two completely different solutions. If your team is resisting the change. They don't want AI in their workflow. They feel threatened. They think it's going to replace them. That's a culture problem. No tool fixes fear. You have to address the fear first. But if your team is resisting the tool, the UX is terrible, the output is unreliable. It's slower than the manual process, that's a tool problem. No amount of workshops fixes a bad product. I had a client who was convinced that they had cultural resistance around ai. They brought in consultants, did personality assessments. They held offsite retreats. They spent a few months in over$200,000 on change management. Then someone on the IT team quietly upgraded the AI tool to a newer version with a better interface. Adoption went from 12% to over 60% in three weeks. It was never a culture problem. The tool was just bad. The old version had an interface that looked like it was designed by someone who hates joy, like if a tax form and a spreadsheet had a baby and nobody loved it. So step one, diagnose correctly. Watch people use the tool. Ask them what's frustrating. Don't assume the answer before you ask question. B is for build. If you decide culture comes first, what does that actually look like? And if you decide tool comes first, what does that look like? Culture first builds look like pilot groups, not company-wide rollouts. You pick your most influential team, not necessarily the most technical, but the most influential, and you make them the early adopters. They become the proof. When they succeed, they tell stories. Stories change culture faster than memos. The key metric in a culture First build is an adoption. It's advocacy. How many people are voluntarily telling others, man, you gotta try this. Tools first builds look a little bit different. Minimum viable deployment. Pick the tool that solves the most painful problem for the smallest team. Don't try to transform the entire organization. Transform one workflow for one group and let the results speak. The key metric in a tools first build isn't sentiment, it's usage. How many people are using the tool without being told to? And here's the honest truth, both approaches require you to start small. The difference is whether you start small with conversations or you start small with capabilities. C is for convert. Getting people from, I'll try it to, I can't work without it. That's conversion Culture first. Conversion is slow, but it's sticky. When people genuinely understand why AI matters and feel safe using it, they become advocates. They don't just use the tool, they defend it, they train others. That's durable adoption, but it takes time, months usually, and during those months, you're spending money losing competitive ground and hoping the culture shift sticks. Tool, first conversation. It's fast, but it's fragile. People adopt because the tool is useful, not because they're internalized to a new mindset, which means the moment the tool breaks or a new tool comes along, or leadership changes, priorities, adoption evaporates. I've seen this exact pattern over and over. Company adopts AI tool adoption spikes. CEO gives a keynote about digital transformation. Then the tool has a bad week of outputs and everyone goes back to email and spreadsheets like AI never happened. That company treated the tool like a trend, not a capability. So the real conversation play, you need both. The question is, which one leads? D is for deliver. here's the framework I like to use with clients. It's a diagnostic, not a dogma. Ask three questions. Number one, have previous technology rollouts failed? If yes, culture first, you're fighting scar tissue. People remember the last time leadership promised a tool that would change everything and it didn't. Two. Is the current pain point obvious and acute? If it's a yes tool first, when people are drowning, they don't need a workshop about water safety. They need a life raft. Number three, does your leadership team agree on why AI is being introduced at all? If no. Culture first. if the C-suite can't articulate a consistent reason for the change, nobody else can either. And inconsistent messaging from the top creates paranoia at the bottom. So here's the sequence that I see work most often. If the diagnosis is cultural, lead with communication and small pilots earn trust. Then introduce tools gradually. If the diagnosis is tools, lead with an MVP deployment for one team and let the results create pull. Then formalize that cultural adoption. if you really just can't tell, start with tools because a good tool with no culture still produces some value. A culture shift with no tool produces meetings and meetings. Last time I checked, don't ship. So here's the call. Culture and tools aren't alternatives. They're dependencies, but one has to come first, and most leaders default to whichever one they're more comfortable with, instead of diagnosing what's actually broken. If your people are afraid, change the culture first. Fear doesn't respond to features. If your people are frustrated, change the tools first. Frustration doesn't respond to workshops. And if your leadership can't agree on why AI is being deployed in the first place, stop everything. Go and get alignment. Because you're not fighting a culture problem or a tool problem. You're fighting a strategy problem. And no amount of technology or transformation theater fixes that. So grab your binary decision scorecard. Does this sequence create leverage? If you're running change management workshops while your competitors are shipping AI products, that's not thoughtfulness. That's delay. if you're forcing tools on a team that doesn't trust you, that's not speed, that's sabotage. Pick the right sequence, the results are going to follow. If you haven't done it already, download your free binary decision scorecard. The links in the description. Use it to diagnose whether your next rollout needs a culture play or a tools play. Before you spend any money like this episode, hit that like button and subscribe. Every new subscriber makes this show reach another operator who's tired of noise and ready for some signal. In the next episode, trust AI outputs or require human review. We're diving into the review layer debate. It's gonna get real binary business all signal, no noise. See you next time.