Brandon Melchior

Start With the Truth: This Is Uncomfortable.

My team is a mix of people who are excited about AI and people who want nothing to do with it. When we started adopting it, I told them the truth. None of us asked for this. Nobody woke up one morning and said, "You know what would be great? If a machine rewired how I do my job." It showed up. It's powerful. And change is hard. But the key is to understand it. Understanding is empowering.

That honesty changed the conversation. When you acknowledge that this is uncomfortable, people stop performing confidence they don't feel. The reluctant ones relax because you're not pretending this is easy. The enthusiastic ones calm down because you're not asking everyone to match their pace. You create space for the only thing that actually matters. Curiosity.

The coaching framework I use is simple. Before you start any task, ask yourself one question. "How can AI help me with this?" Then try it. See what happens. Maybe it writes a first draft you can react to instead of starting from a blank page. Maybe it synthesizes research notes in thirty seconds that would have taken you an hour. Maybe it produces something useless and you learn where the boundary is. All of those outcomes are valuable. And every day those boundaries move. So, next week, try it again.

What I've found is that the reluctant people aren't afraid of the technology. They're afraid of looking stupid. They're afraid of using it wrong, or producing something that reveals they don't understand it yet. So I normalize the mess. I share my own failed experiments. I show the prompts that didn't work before the ones that did. I make it clear that fumbling with this stuff is the job right now, not a sign you're behind.

The enthusiastic people need different coaching. They tend to over-trust the output and under-invest in evaluating it. They move fast and skip the step where you ask whether the result is actually good. Speed without judgment is just efficient mediocrity. I push them to slow down at the evaluation step and apply the same critical eye they'd bring to any other piece of work.

The goal isn't to make everyone an AI expert. It's to make everyone comfortable enough to experiment. Curiosity compounds. One small win leads to another question, which leads to a better workflow, which leads to someone showing a teammate what they figured out. That's how adoption actually spreads. Not from a policy doc. From one person trying something and telling someone else it worked.