Here's a pattern I've seen too many times: an organization hires an AI consultant, runs a discovery workshop, builds a proof of concept — and then watches it die in the hallway. Not because the technology failed, but because the people weren't ready for the conversation.
A recent research puts it bluntly: only 10% of companies generate significant value from AI. And their "10/20/70" rule explains why — 10% of AI success comes from algorithms, 20% from technology and data, and 70% from people and process transformation.
The most productive AI conversations I've been part of — the ones that actually led to shipped, adopted, valued solutions — happened when the organization had done the mindset work first. Not technical training. Not tool selection. Mindset.
These seven practices cost nothing, require no technology, and can start today. They prepare your team, your leadership, and yourself to have better conversations — internally and with any AI consultant or strategist you bring in.
AI isn't about replacing what works. It's about giving superpowers to the practices you've spent years perfecting. But superpowers only work if the person wearing them is ready.
Keep a Pain Journal, Not a Technology Wish List
For the next two weeks, carry a simple list — physical or digital — and write down every moment in your operations where you think: "This is frustrating." "This takes too long." "We keep getting this wrong." "I wish I knew X before Y happened." Don't filter. Don't think about AI. Just document friction.
This creates something invaluable: a problem inventory framed in your language, grounded in your reality. When you eventually sit down with an AI consultant, you hand them this list instead of asking "What can AI do for us?" — a question that puts you in a passive position and invites generic answers.
The shift is powerful. You go from "Tell me what AI can do" to "Here are my problems — which ones can you help me solve?" That's a completely different conversation. McKinsey calls this approach "domain-led AI" — starting from operational expertise and pulling technology toward it, not the other way around.
Open a shared note with your direct reports. Title it "Things That Slow Us Down." Ask everyone to add to it for two weeks. No categories, no prioritization — just raw operational friction. You'll be surprised what surfaces.
Reframe AI as "Getting Your Best People's Time Back"
The single most effective internal message for AI adoption — confirmed by Deloitte's enterprise AI research — isn't about efficiency, cost savings, or competitive advantage. It's this: "AI frees you to do more meaningful work."
Identify the top 3–5 tasks your most experienced people spend time on that don't actually require their expertise. Your best dispatcher manually reviewing routine schedules. Your senior technician filling out compliance paperwork. Your operations manager compiling weekly reports from spreadsheets.
Now reframe: "AI isn't here to replace Sarah. AI is here to stop wasting Sarah's talent on things that don't need Sarah." When your best people hear that their expertise will be amplified rather than automated, resistance transforms into curiosity.
Ask your three most experienced team members: "What's the one part of your job that feels like a waste of your skills?" Write down what they say — those are your first AI use cases, pre-qualified by the people who matter most.
Run the "Extra Hour" Exercise
In your next team meeting, ask one question: "If AI could give you back one hour every day by handling one repetitive part of your job, what would you do with that hour?"
Write every answer on the whiteboard. Three things happen simultaneously. First, you surface genuine use cases from the people who know the work best — not from a vendor pitch deck. Second, you shift the emotional frame from fear ("AI will take my job") to aspiration ("AI will give me time for the work I actually care about"). Third, you build a ready-made list of high-value activities that justify the AI investment to leadership.
When your team says things like "I'd finally have time to do proactive maintenance walks" or "I could spend more time mentoring junior techs" or "I'd actually follow up with customers instead of just closing tickets" — that's the human story that makes an AI business case compelling.
Dedicate 15 minutes in your next standup or team meeting. Ask the question, capture the answers, and share the results with leadership. Framing: "Here's what our team would do with the time AI could give back."
Use "Copilot" Language — Always
Words shape perception. In every AI conversation — with your team, leadership, vendors, or consultants — use the word "copilot" and reject "autopilot." AI recommends, humans decide. AI drafts, humans review. AI flags, humans act.
MIT Sloan Management Review found that organizations using augmentation language had measurably lower employee resistance and higher participation in AI pilots — even when describing the exact same technology as those using automation language.
Practice these swaps until they're second nature:
- Instead of "AI will handle scheduling" → "AI will recommend optimized schedules for dispatcher review"
- Instead of "Automating customer service" → "Giving service reps AI-powered suggestions in real time"
- Instead of "AI replaces manual inspection" → "AI pre-screens data so inspectors focus on what matters"
- Instead of "We're implementing AI" → "We're giving our team AI-powered tools"
This isn't spin — it accurately reflects how enterprise AI actually works. Human-in-the-loop is the norm. Own that framing from day one.
Sketch Your "Process Napkin" Before Talking to Any Consultant
AI consultants spend an enormous amount of time — and your budget — just understanding how your operation works. You can skip weeks of discovery by preparing a simple one-page sketch for each major process you want to discuss. Four elements:
- What triggers the process (a customer call, a sensor alert, a scheduled date)
- The 3–5 major steps (triage, schedule, dispatch, resolve, close)
- Where decisions happen and who makes them
- What data exists at each step — and be honest about its state
That last point is critical. Be candid about your data reality: "We track this in Oracle Field Service." "This lives in Maria's spreadsheet." "We don't measure this, but probably should." "This data exists but it's inconsistent across regions."
A good AI strategist can work with imperfect data. What they can't work with is a false picture. Honesty about data maturity earns you better, more specific recommendations instead of generic pitches.
Pick your most painful process. Spend 20 minutes sketching it with the four elements above. You'll be surprised how clarifying it is — even before any AI conversation happens.
Run a Pre-Mortem on AI Resistance
Before announcing any AI initiative, gather your team leads and ask: "Imagine it's six months from now and our AI project has completely failed because our people rejected it. Why did they reject it? What went wrong?"
This technique — developed by psychologist Gary Klein and widely adopted in management practice — surfaces resistance before it solidifies. You'll hear the real fears: "Technicians thought it was surveillance." "Dispatchers felt their expertise was being dismissed." "Nobody explained why we were changing." "Middle management saw it as a threat to their role."
Each of these is now a solvable communication problem rather than a surprise obstacle. Harvard Business Review's research on AI-powered organizations (Fountaine, McCarthy & Saleh) found that cultural readiness is the number one predictor of AI initiative success — ahead of data quality, technology choice, and budget.
Share the pre-mortem results with your AI consultant. Ask how their approach addresses each concern. If they dismiss the concerns or say "the technology speaks for itself" — find a different consultant.
Schedule a 30-minute "pre-mortem" session with your team leads. Set the context: "We're exploring AI for our operations. Before we go further, let's be honest about what could go wrong on the people side." Document everything — this becomes your change management playbook.
Start an AI Curiosity Circle
Not a committee. Not a task force. Not a working group with deliverables and deadlines. A curiosity circle.
Invite 4–6 people from different roles — a field tech, a dispatcher, a customer service rep, a manager, someone from IT. Meet for 30 minutes every two weeks. The only agenda: each person shares one thing they learned about AI that week. A podcast episode. An article. A conversation. Something they tried with ChatGPT. No presentations. No pressure. No homework.
BCG and MIT's research found that employees who personally experimented with AI tools were 3x more likely to support organizational AI initiatives. This circle creates that experimentation space — safe, informal, and cross-functional.
After 2–3 months, something remarkable happens. These circles naturally produce internal champions — the ones who say "I tried using AI to draft customer communications and it saved me 45 minutes" or "I saw how a company like ours used AI for scheduling." These organic advocates are far more persuasive than any top-down mandate or vendor demo.
Send a casual invite to 4–6 people across roles: "I'm starting a low-key AI curiosity group. 30 minutes, every other week. No expertise required — just bring one thing you found interesting about AI. Coffee's on me." That's all it takes.
The Conversation Starts Before the Consultant Arrives
Every one of these practices can start this week. None of them require a budget, a technology purchase, or permission from IT. They're about building the organizational muscle that makes AI conversations productive — the muscle that BCG's research says accounts for 70% of AI success.
When an AI consultant finally walks into your building, the difference will be immediate. Instead of a room full of people wondering "What is AI going to do to my job?" you'll have a team that says "Here are our biggest pain points, here's how our processes work, here's what we'd do with the time AI gives back, and here's what we're worried about." That's a team ready for a real conversation.
The organizations that get the most from AI aren't the ones with the biggest budgets or the most advanced technology. They're the ones whose people walked into the room prepared — curious, honest about their challenges, and ready to be given superpowers.
Further Reading
The insights in this article are informed by research from McKinsey ("The State of AI," "Domain-led AI"), BCG ("10/20/70" rule, BCG/MIT AI adoption studies), Harvard Business Review (Fountaine, McCarthy & Saleh, "Building the AI-Powered Organization"), MIT Sloan Management Review (Ransbotham et al., "Winning with AI" series), and Deloitte ("State of AI in the Enterprise"). The "pre-mortem" technique was developed by psychologist Gary Klein.