"I don't know enough about AI to lead my team." Neither does anyone else.
Leadership says we need an AI plan. You nod. You say absolutely. Then you walk back to your desk and think — I don't even know what that means. If that's you right now, this is for you. The good news: you don't need to be the AI expert. You need to be the structure. And you already know how to do that.
Cloud Systems Engineer · MCT · PMP · Azure Solutions Architect Expert. 40+ years in IT and operations. Builder of the Blair AI Rollout Framework.
Published June 2026
Marcus is Director of Operations at a regional logistics company in Ohio. His VP asked him to put together an AI plan by end of quarter — and he has no idea where to start. This episode reframes that fear: you don't need to be the AI expert, you need to be the structure.
Listen on SpotifyThe conversation nobody says out loud.
It happens in offices everywhere right now. Leadership says we need an AI plan. The director nods. Says absolutely. Then walks back to their desk, closes the door, and stares at the screen — because they have no idea where to start.
This is Marcus. He's a Director of Operations at a regional logistics company in Ohio — three hundred employees, good at his job, respected by his team. His VP asked him to put together an AI plan by end of quarter. His entire AI experience is one ChatGPT question six months ago that he's not sure he even used correctly. And he is genuinely afraid of standing in front of his team without answers.
If you recognize yourself in Marcus, here's the first thing worth knowing: that feeling is almost universal among operations leaders right now, and almost nobody admits it. The honesty to name it is actually your first advantage — because it points you away from pretending and toward the thing that actually matters.
"You don't need to be the AI expert. You need to be the structure. And you already know how to do that."
1. Be the structure, not the expert.
Marcus's first instinct when his VP said "AI plan" was to start Googling. Watch tutorials. Figure out which tools his competitors are using. Get smart fast. That instinct is understandable — and it's the wrong move.
Here's what your team actually needs from you right now. Not an AI expert. Not someone who can explain how a large language model works. Not someone who has tested every tool on the market. They need someone who can create a clear, calm path forward — someone who can say: here's how we're going to approach this, here's what's acceptable, here's what's not, and here's how we're going to make sure nobody gets left behind.
That's not AI expertise. That's leadership. And an experienced operations director already knows how to do that. The pressure to become an AI expert overnight is real — but it's a distraction from the thing your team actually needs, which is structure. And structure is something you build every single day.
2. Start with what you know, not what you don't.
Marcus has been running logistics operations for years. He knows exactly where shipments get delayed. He knows which handoffs break down. He knows which workflows eat time, which processes create friction, and which parts of his operation his team dreads every week. That knowledge is worth more than any AI certification right now.
Here's what most operations leaders miss when they're told to build an AI plan. They immediately look outward — what tools exist, what competitors are doing, what consultants recommend. And they completely overlook the most valuable asset they already have: deep, specific, hard-won understanding of exactly how work gets done inside their organization.
AI doesn't fix broken workflows. It accelerates whatever is already there — good or bad. Which means the operations leader who knows their workflows inside and out is in a far better position to introduce AI responsibly than any outside expert who doesn't.
So don't start with AI. Start with your workflows. Pick one that's repetitive, time-consuming, and low risk. Write down exactly how it works today. That document — that simple, honest description of one workflow — is the foundation of your entire AI plan. You already know more than you think you do. You just haven't connected it to AI yet.
3. Your first move isn't a plan. It's a question.
Marcus has to walk back into his VP's office by end of quarter with an AI plan. Right now he thinks that means a slide deck, a tool comparison, a budget, a timeline, and a rollout strategy for three hundred employees. It doesn't.
Your first move isn't a plan. It's a question — one question you ask your team this week, before you touch a single tool, before you open a single article about AI, before you write a single slide.
"Where does our work slow down?"
Ask your team leads that in your next one-on-one. Where does our work slow down? What takes longer than it should? What do you do every week that feels like it shouldn't take as long as it does? The answers to that question are your AI plan. Not because AI solves every bottleneck — but because now you have a list of real, specific, operational problems that AI might be able to help with.
And when you walk into your VP's office, you're not guessing. You're not presenting something you copied from a consultant's website. You're presenting your organization's actual starting point — in your own words, grounded in your own operation. That's not a weak AI plan. That's the only kind worth having.
How this connects to the Blair Framework.
Everything above — the structure, the workflows, the one question — is exactly what the first stage of the Blair AI Rollout Framework is built around. Not tools. Not technology. Capability. Understanding where you are before you decide where you're going.
Before you do anything else, send one message to your three or four closest team leads. Just this: "Quick question — where does our work slow down? What takes longer than it should?" No agenda, no AI mention, no pressure. Just listen to what comes back. Those answers are your starting point. Write them down. You just built the foundation of your AI plan in one afternoon.
Three things to take with you.
- You don't need to be the AI expert. You need to be the structure. Your team needs a clear, calm path forward — and that's leadership, which you already know how to do.
- Start with what you know, not what you don't. Your operational knowledge is your biggest advantage. AI accelerates whatever is already there, so know your workflows first.
- Your first move isn't a plan. It's a question. Ask your team leads where the work slows down. The answers are your AI plan — grounded in your actual operation.
Turn a vague assignment into a real starting point.
The AI Readiness Score gives you a documented baseline of exactly where your organization stands today — across leadership alignment, governance, workflow fit, and team capability. About five minutes, no email required to begin. It's the honest starting point that turns "we need an AI plan" into something you can actually act on.
Start Here — Free AI Readiness Score →Related resources.
You're Not Behind — You're Unstructured →
Reframe the pressure before you build your response plan.
Your First 30 Days with AI →
The complete 30-day plan before you touch a single tool.
Shadow AI Guide →
What to do when AI is already in your organization before you rolled it out.
AI Pilot Success Scaling →
When the pilot works and leadership wants to scale everything at once.
Common questions.
You don't need to know everything about AI. You need a place to start.
The free AI Readiness Score gives you a documented baseline in about five minutes — the honest starting point that turns "we need an AI plan" into a real, structured path forward.