http://www.mindsetinnovationsconsulting.com/

Mindset Innovations Consulting, PO Box 1167, Waukee, IA (2026)

05/26/2026

Most consultants will tell you that resistance to AI is a people problem.

I am going to tell you something different.

After walking into dozens of organizations and sitting with the people everyone has labeled as "resistant," I have learned this: resistance is not one thing. It is three completely different things wearing the same mask.

Let me explain what I mean.

Fear-Based Resistance

This sounds like: "AI is going to replace all of us" or "I heard it makes mistakes all the time." When someone tells you things they believe to be true about AI but clearly do not know the specifics, that is fear talking. They are not lying to you. They are filling a knowledge gap with a narrative that feels safer than admitting they do not understand.

Think of it like electricity. Most people do not know how electricity works, but they use light switches every day without fear because they trust the system. With AI, we are asking people to flip switches they do not understand in a system they do not trust yet.

Grief-Based Resistance

This sounds like: "I have been doing this job for 20 years" or "What is the point of my experience now?" This person is not afraid of AI. They are mourning. They built an identity around being the person who knew things, solved problems, or had the answers. AI feels like an obituary for who they used to be.

You cannot logic someone through grief. You cannot convince them their experience still matters. You have to help them discover what their new identity looks like in a world where AI exists.

Legitimate Objection

This sounds like: "This workflow will not work with our current system" or "Our customers will not respond well to this approach." This person is not resisting AI. They are resisting a sloppy implementation. They see something you missed, and they are brave enough to say it out loud.

Here is what I have learned: the loudest objector in your company may not be your problem. They may be the last honest voice you have left.

The Real Question

When someone pushes back on your AI rollout, do not ask "How do I overcome this resistance?" Ask "What kind of resistance is this, and what is it telling me?"

Because fear needs education. Grief needs acknowledgment. And legitimate objection needs you to listen and adjust course.

Three different problems. Three different solutions.

Stop treating them all the same.

05/19/2026

The person you want to fire may be your best diagnostic tool.

I sat across from a new CEO client last month who was ready to move someone off his AI implementation team. "She questions everything," he said. "Every meeting, she's got three reasons why it won't work."

I asked him to describe the questions.

"She wants to know how the AI will handle the account's custom requirements. She's worried about data quality in the legacy system. She keeps asking what happens when the system goes down during peak season."

I looked at him. "Those aren't resistance questions. Those are implementation questions. Good ones."

Here's what I've learned after years of walking into these situations: the person everyone calls difficult is often the person who's actually thinking through the consequences.

Fear based resistance sounds like this: "I heard AI takes jobs." "Everyone knows it makes mistakes." They're filling knowledge gaps with invented narratives because they don't understand the technology.

Grief based resistance sounds like this: "I've been doing this for 20 years." "This isn't how we've always done it." They're mourning the loss of an identity or skill set that defined their value.

But legitimate objection sounds different. It's specific. It's system focused. It names real gaps in your rollout plan.

The CEO thought he had a people problem. What he actually had was someone brave enough to point out the holes in his implementation before they became expensive failures.

Few months later, guess what happened? The account integration failed exactly how she predicted. The legacy data quality issues caused two weeks of rework. And the system outage during peak season cost them their biggest client that quarter.

She wasn't being difficult. She was being diagnostic.

Your most vocal objector might not be fighting your vision. They might be the only person in the room who's actually thinking it through.

The question isn't how to get past the resistance. The question is what the resistance is trying to tell you.

Listen to the person everyone else has written off. Sometimes the loudest voice in the room is the only honest one you have left.

05/12/2026

I had lunch with a CEO last week who said something that stuck with me.

"Dave, I keep telling my team we're implementing AI, and they nod along in meetings. But I can feel the tension in the room. Nobody's asking questions. Nobody's pushing back. And that worries me more than if they were arguing with me."

Smart guy. He knew something was off.

I asked him one question: "When was the last time someone on your team admitted they were confused about something and it went well for them?"

He sat there for a minute. Then he said, "I honestly can't remember."

That's the conversation most leaders need to have with themselves.

Because here's what I've learned after sitting in hundreds of these conversations: your people aren't resisting AI. They're responding to a culture that punishes uncertainty. And if you can't name your own fears about this technology, how can you expect them to name theirs?

The good news? The hardest part isn't teaching people to use AI. It's creating the conditions where they feel safe to learn. And that starts with one honest conversation.

If this sounds familiar, here's what I'd suggest. Ask your team one question this week: "What would make it easier for you to experiment with AI?" Don't defend. Don't problem solve. Just listen.

You might be surprised what you hear. And they might be surprised that you asked.

05/05/2026

Two companies. Same industry. Same AI rollout timeline. Completely different outcomes.

Company A sent an email: "We're implementing AI tools to improve efficiency. Training starts Monday." The CEO followed up in the all-hands: "This is exciting. We're going to be faster and smarter." Clean. Simple. Logical.

Company B started with a question. The CEO walked the floor and asked people one thing: "What worries you most about AI becoming part of your daily work?" Then he listened. For weeks. He heard about job security fears. About feeling overwhelmed by another new system. About not wanting to look stupid in front of younger colleagues.

Six months later, here's what happened.

Company A had beautiful adoption metrics on paper. Everyone completed training. Everyone had access. But usage rates stayed flat. People used AI for safe tasks like email drafts and meeting summaries. The real work stayed human. Shadow AI crept in anyway, but quietly, without governance.

Company B took three months longer to deploy. But when they did, something different happened. People weren't just using AI. They were improving it. Suggesting new applications. Sharing what worked and what didn't. The woman in accounting who was terrified of AI six months earlier became the one training new hires on the best prompts for invoice processing.

The difference was one simple recognition: fear doesn't disappear when you tell it to. It disappears when you address what's causing it.

Company A treated readiness like a checkbox. Get trained, get access, get efficient.

Company B treated readiness like a relationship. Listen first. Address the real concerns. Create conditions where people felt safe to experiment.

One organization deployed AI TO their people. The other deployed it WITH their people.

If you're planning an AI rollout, ask yourself: are you informing people or involving them? Because the difference shows up everywhere. In usage rates. In innovation. In whether your best people stick around to see what happens next.

What worries your people most about AI? Have you asked them lately?

04/28/2026

I was talking to a front desk woman at a trade show last month. Her CEO was standing right there when she told me she was scared of losing her job to AI.

He immediately jumped in. "Don't worry, you're not losing your job. We're just using AI to help you do your work better."

She smiled and nodded. He walked away feeling good about his leadership.

I stayed for a minute longer. "Are you still worried?" I asked.

"Oh, heck yes, I'm still worried. He can say all that he wants, but there are systems out there doing my job way better than I can."

That gap between what the CEO said and what she actually believed? That's where most AI transformations die.

Here's what I've learned in 20 years of helping people through change: when someone says they're not ready for AI, they're usually dealing with one of four things, and most leaders can't tell the difference.

Fear versus Anxiety. Fear is immediate danger. An alligator hissing at you. Anxiety is worry about the future. "Will AI make me obsolete in two years?" Fear needs safety right now. Anxiety needs a vision of what's possible.

Capability Gap versus Confidence Gap. Some people genuinely don't know how to use the tools. Others know exactly how but don't trust themselves to use them well. Training fixes capability. Psychological safety fixes confidence.

Individual Resistance versus Cultural Permission. Sometimes one person is dragging their feet. More often, the whole culture is sending mixed messages. "Use AI, but don't make mistakes. Experiment, but don't fail. Adapt, but don't change anything important."

Readiness Problem versus Leadership Projection. When a CEO tells me "our people aren't ready," I always ask: "What specifically tells you that?" Most can't answer with data. They answer with their own uncertainty reflected back at them.

The companies that get AI transformation right don't skip the human part. They diagnose what's actually happening before they prescribe what people need.

Because here's the thing about that front desk woman: she wasn't wrong. AI probably could do parts of her job better than she can. But her experience, her judgment, her ability to read people and solve problems AI never sees coming? That's something I can buy an AI tool, but I can't buy that.

The question isn't whether your people are ready. It's whether you've created the conditions for them to become ready.

What are you seeing when you look closely at your team's concerns about AI?

04/21/2026

I was standing in a company break room last month when I overheard two employees talking.

"Did you see the email about the new AI tools?"

"Yeah. Guess I better start updating my resume."

The CEO had just finished a town hall about their exciting AI initiative. Talked about innovation, efficiency, competitive advantage. All the right words.

But in the break room, those words translated to: "They're looking to replace us."

Here's what I've learned after 20 years in manufacturing and consulting: You cannot shove AI into a fearful culture and call it transformation.

Fear is immediate. Like an alligator hissing at you 4 feet away. When employees hear "AI implementation," many hear "job elimination." When you dismiss that fear with "don't worry, you're not losing your job," you might as well be talking to a wall.

The woman at the trade show told me straight: "He can say all that he wants, but at the end of the day, there are systems out there that do my job way better than I can."

She didn't believe her own CEO. Because reassurance without a system is just noise.

Most leaders think readiness is a training problem. Run a workshop. Check the box.

When your culture makes it dangerous to ask questions, people will not ask questions about AI either. When mistakes get punished instead of learned from, people will avoid AI tools entirely. When job security feels threatened, every new technology feels like a threat.

The companies getting AI right are not the ones with the best tools. They are the ones where people feel safe enough to learn, experiment, and even fail while figuring it out.

Your employees are not resisting AI because they are stubborn. They are responding rationally to conditions you created.

The question is not whether your people are ready for AI. The question is whether your culture is ready for your people to be ready.

Start there.

04/14/2026

I had coffee with a CEO last week who said something that stuck with me.

"Dave, I think my people are using ChatGPT for everything now. Should I be worried?"

I asked him one question: "What makes you think they are?"

"Well, Sarah in accounting mentioned she uses it to write emails. And my operations manager said something about asking AI to help with scheduling conflicts. And honestly, half the reports I'm seeing lately sound way more polished than they used to."

He wasn't wrong. His people were solving problems faster, writing clearer, thinking through decisions with a thought partner that never gets tired.

But here's the thing: he had no idea what data they were feeding these tools, what decisions they were letting AI make, or whether they even knew the difference between good AI advice and sophisticated sounding nonsense.

"I don't want to be the guy who bans the thing that's making my team more productive," he said. "But I also don't want to be the guy who finds out we've been pasting client contracts into ChatGPT for six months."

That's the shadow AI dilemma in one conversation.

Your people aren't rule breakers. They're problem solvers. They found tools that work and they're using them because waiting for an official AI policy felt like waiting for permission to be efficient.

The question isn't whether you should stop them.

The question is whether you're curious enough to understand what they've already figured out.

If this conversation sounds familiar, here's what I've learned works: start with one honest conversation. Pick one person you trust who you suspect is already using AI tools. Ask them what they're doing, why it's helpful, and what they worry about.

Don't audit. Don't investigate. Just listen.

You might discover your best market research has been happening in browser tabs you didn't even know were open.

04/07/2026

Two CEOs. Same industry. Same week. Both discovered their teams were quietly using ChatGPT for customer service responses.

John's reaction: "Absolutely not. This is a liability nightmare. Block everything. We handle customers with human judgment, not AI."

Sarah's reaction: "Interesting. Show me what you're actually doing with it."

John issued a company wide email that Monday. ChatGPT blocked at the network level by Wednesday. Three of his best customer service reps gave notice within the month. Because they felt like criminals for trying to solve problems faster.

Sarah spent that Monday in the customer service pit. Watched her team work. Asked questions. Learned they were using AI to draft responses but always reviewing them before sending. Faster first drafts, same human oversight.

John's team went back to taking 40 minutes per complex customer issue. Sarah's team formalized what they were already doing. Created guidelines. Built review checkpoints. Same quality, half the time.

Six months later, John's customer satisfaction scores dropped 12 points. His response time complaints doubled. Sarah's team became the departmental model for the rest of the company.

The difference was not the technology. The difference was curiosity versus control.

John saw his people reaching for AI and assumed they could not be trusted. Sarah saw her people reaching for AI and wondered what they knew that she did not.

Both reactions made sense in the moment. Both CEOs cared about quality and customers.

But John led from fear. Sarah led from questions.

When your employees start using tools you did not approve, your first instinct tells you everything about your leadership defaults. Do you ask why they needed to go around you? Or do you just close the door they opened?

The fear reaction is normal. The learning reaction is rare.

Your people are not trying to break your company. They are trying to fix problems you have not seen yet.

What would happen if you asked one question before you locked one door?

03/31/2026

I was talking to a manufacturing leader last week who told me something that stopped me cold.

He said, "Dave, I've been managing people for 15 years. I can read a room, handle conflict, make tough calls. But now when a problem comes up, I go straight to ChatGPT first. And my team has noticed."

He paused. Then: "They're not following my judgment anymore. They're following whatever sounds most sophisticated."

This is what I call the Shadow AI Handoff. And it's happening in companies everywhere.

Most CEOs think shadow AI is about data security or policy violations. Those are real concerns. But the deeper issue is leadership abdication disguised as efficiency.

Here's how it works. An employee hits a decision point. Instead of using their experience, their judgment, or asking their manager, they paste the situation into an AI tool. The AI responds with something that sounds authoritative because it uses bigger words and more structure than the employee would naturally use.

So, the employee defers because it sounds more confident than they feel.

Now multiply this across your organization.

Your people aren't just using AI to write emails or summarize documents. They're using it to make calls they used to make themselves. And every time they do that, a little bit of their decision-making muscle atrophies.

The real question isn't whether your employees are using shadow AI. They are. The question is whether they're using it as a thought partner or as a replacement for thinking.

A thought partner helps you clarify your own judgment. A replacement makes the judgment for you.

The difference is in how you frame the conversation with the AI. "Help me think through this decision" builds capacity. "What should I do about this situation" surrenders it.

Your best people didn't get where they are by following scripts. Don't let shadow AI turn them into script readers now.

If you're going to govern AI use in your organization, start there. Not with what tools they can access, but with how they're supposed to interact with those tools.

Because you hired leaders, not prompters.

What are you seeing in your organization? Are people using AI to think better, or instead of thinking?

03/24/2026

I was having coffee with a manufacturing CEO last month and he said something that stuck with me.

He told me about discovering his plant manager was using ChatGPT to help resolve conflicts on the production floor. Not just for ideas, but actually copying and pasting the AI responses into emails to his team.

The CEO's first reaction was anger. His second was curiosity.

He started digging and found out this wasn't isolated. His accounting team was feeding budget data into online AI tools to generate reports faster. His marketing person was using it to rewrite customer communications. His operations lead had built some kind of scheduling workflow with AI that was actually outperforming their expensive software.

Nobody had asked permission. Nobody had mentioned it in leadership meetings. It was just happening.

Here's what really got to him though. When he talked to these employees individually, they all said the same thing. They weren't trying to be sneaky. They were trying to get their jobs done better and faster. They found tools that helped, so they used them.

The plant manager told him something like this: "I figured if it was a problem, someone would have told us not to use it. Since nobody said anything, I assumed it was okay."

That's when it hit this CEO. The silence wasn't permission. It was a leadership vacuum. His people were filling it with whatever they could find.

Now here's the thing that keeps me thinking. This isn't happening at one company. It's happening everywhere. Your best people are already using AI. They're solving problems you didn't even know existed. They're building workflows you never approved.

And most of them have no idea they might be creating risks for the company. They're just trying to do good work.

So the question isn't whether your employees are using AI tools without telling you. The question is what you're going to do when you find out they are.

You can panic and shut it all down. You can ignore it and hope nothing bad happens. Or you can get curious about what they've discovered and build some guardrails around the good stuff.

But you can't pretend it's not happening. Because pretending is just another form of leadership vacuum. And your people are going to fill that space whether you're paying attention or not.

The conversation you're avoiding about AI in your company? It's already happening. You're just not in the room.

02/11/2026

Your Paradigm is the Problem.

If AI feels confusing, threatening, or “not for your culture,” this first episode is for you.

We just launched a brand-new YouTube channel: The PrecisionX System™

And Episode 1 is all about the real starting line for AI adoption: Mindset.

In this episode, Kacy Webster with Profit Quiver and Dave Machovsky with Innovations Consulting break down:
✅ The social reaction curve to innovation (ignore, mock, resist, adopt, integrate) and where most teams are stuck.

✅ Why “we’re not using AI here” is usually an illusion (hello, Shadow AI).

✅ The shift from “AI replaces people” to the truth: humans become sense-makers and decision architects.

✅ How to move from finite thinking (fear, short-term, protection) to infinite thinking (learning, iteration, long-term value).

✅ A real example of using AI as a mirror to challenge your own thinking and expand your leadership capacity.

If you lead a team, run a company, or care about culture, this is the conversation most organizations are avoiding and it’s costing them momentum.

The wave is here. The leaders who learn to ride it will create the next competitive edge.

Enjoy!

Watch Here: https://youtu.be/9-XhiM1vcpU?si=54TjHdhj90PzCEv6

Mindset Innovations Consulting

05/26/2026

05/19/2026

05/12/2026

05/05/2026

04/28/2026

04/21/2026

04/14/2026

04/07/2026

03/31/2026

03/24/2026

02/11/2026

Address

Website

Alerts

Shortcuts

Share

Category