Thought Partner, Not Thought Leader, Not Thinker
The most dangerous thing I see operators do with AI is hand it the steering wheel. The second most dangerous thing is refuse to let it in the car.
The framework I teach is called Thought Partner, Not Thought Leader, Not Thinker. The name carries the entire lesson: AI is your thought partner, not your brain, and not your thinker. It does exceptional work on the first two-thirds of any problem. The research, the drafting, the data assembly, the pattern recognition, the options generation. That work used to take hours or days. AI compresses it to minutes. The compression is real and it is transformative.
The last third is yours. The judgment call. The decision about what to do with what AI produced. The contextual knowledge about your business, your customers, your market, your values, and your risk tolerance that no model has access to. AI can show you the options. AI cannot know which option is right for you.
I call this the two-thirds rule. AI does the first two-thirds. You do the last third. And the last third is where the value lives, because the judgment is what separates your company from every other company using the same tools.
The men I coach who are behind on AI almost always have the same concern: they are afraid of losing control. They built their businesses on judgment, instinct, and experience, and they see AI as a threat to all three. The reframe I offer is that AI amplifies all three. Your judgment is better when it operates on better inputs. Your instinct is sharper when the background research is already done. Your experience is more valuable when you are applying it to synthesized information rather than spending your time gathering it.
The practical sequence I teach is process before technology. Before you bring AI into any workflow, nail the process. Know what the steps are, know what the inputs and outputs are, know what good looks like. Then bring AI in to accelerate the steps, not to replace the process. If you automate a broken process, you get a broken process that runs faster.
The adoption dimensions I look at with every operator are four: breadth (how many of your workflows use AI), depth (how sophisticated is the use in each one), integration (is AI connected to your data and your systems, or is it a standalone chat window), and ownership (does your team own the AI capability, or does it leave when the consultant does).
Most operators I talk to are at breadth 1 or 2, depth 1, integration zero, and ownership zero. They have tried ChatGPT for a few things and it was interesting but it did not change the business. The gap between that and what I run at OpticWise is two years of deliberate, process-first implementation. I can close that gap for the men I coach because I have already walked the path and I know where the dead ends are.
Where would the two-thirds rule change your week if you applied it tomorrow?
~b