You can't automate a process that doesn't work and expect it to start working. Everyone is excited about what AI can do, and that excitement is mostly justified. But the conversation underneath the hype doesn't get enough attention: AI doesn't fix broken processes. It accelerates them. If your team is spending hours on a task that's well-defined, consistent, and just plain tedious, AI can be transformative. It executes reliably, handles volume, and eliminates the errors that creep in when humans do repetitive work for too long. But if the process is unclear, inconsistently followed, or lives mostly in someone's head, AI won't save you. It will just make the confusion faster and harder to untangle. The organizations getting real results from AI aren't necessarily the ones with the best tools. They're the ones who did the unglamorous work first. They mapped their processes, identified the failure points, and built enough clarity that a tool could actually follow the logic. So before you invest in the next AI solution, ask yourself one question: could you hand this process to a new employee and have them execute it successfully on day one? If the answer is no, fix that first. If you need help getting there, let's talk.

Your team is already using AI. The question is whether you're part of that conversation. Leaders tell me they're uncertain about AI in the workplace, which is fair. The technology is moving faster than many anticipated, and the answers aren't obvious. Meanwhile, your team is already experimenting. They're using ChatGPT or Copilot to draft emails, summarize documents and speed up repetitive tasks. Some are ignoring security policies because the tools make their jobs easier. Others are quietly worried about being replaced. The worst response is pretending you have all the answers or waiting until you do. My humble suggestion: bring your team into the conversation. Acknowledge the uncertainty. Ask what tools they're already using and why. Talk openly about the risks and the opportunities. Define together what success looks like and how AI might help you get there. People support what they help create. If you want your team to adopt AI thoughtfully and safely, they need to be part of shaping how it's used. That's not an AI strategy. That's leadership.

Your data is messy. And it's not a technology problem. If Tuesday's post resonated with you, here's the harder conversation. Most small businesses have data scattered across spreadsheets, software platforms, and email threads. Customer names entered six different ways. Pricing that lives in one person's head. Processes that work because Mary has been doing it the same way for eleven years and everyone just knows to ask Mary. That's not a data problem. That's a documentation problem. And here's where it gets real: if you can't describe a process clearly enough to write it down, you can't use AI to improve it. What data normalization actually means: Imagine trying to pull every sale you've made to your best customer. Except half your team entered them as "ABC Company," two invoices say "ABC Co.," and one says "A.B.C. Company Inc." The data is all there. But it's not usable. That's a normalization problem. And it didn't come from bad software. It came from nobody writing down how to enter a customer name correctly. That's just one version of this problem. The same thing is happening in your pricing, your inventory, your sales process, and your scheduling. Pick any core process in your business and you'll find a variation of the same story. The root cause is almost always the same: Someone learned the process, got good at it, and it never got documented. It just lived in their head. Then it got passed on informally to the next person, who added their own variation. Then the next person did the same. Multiply that across every process in your business over five or ten years and you have a data environment that no AI tool can make sense of. Garbage in, garbage out. AI won't tell you the output is unreliable. It will just give you a confident answer based on a flawed foundation. So before you invest in AI tooling, ask yourself: Can I describe my core business processes clearly enough to write them down? If the answer is "mostly" or "it depends who you ask," you have work to do first. Not because AI requires perfection, but because the documentation process itself will reveal gaps and inconsistencies you didn't know existed. That's actually valuable work regardless of what you do with AI afterward. The good news: You don't have to solve this all at once. Start with your highest-value processes. The ones that directly touch your customer, your revenue, or your competitive advantage. Document those first. Clean that data first. Build from there. There's a harder conversation underneath all of this, one about the people who hold that institutional knowledge and what they're thinking right now. We'll get into that on my next post.