Why "It Can All Be Done" Is Terrifying

Tell a room full of executives that AI can do something they've wanted for years, do it quickly, and do it cheaply — and they don't get excited. They go quiet. Then someone says, "We'll look into it sometime," and the meeting moves on.

I've had this conversation dozens of times. The pattern never changes. "Can this be done?" Yes. "What about that?" Yes. "Does it take long?" No. Everyone nods. Someone says the world really has improved. And then comes the question that changes the room: "So why aren't we doing it?"

I used to answer: "Because you've been fine without it." But that's not quite right. The real answer is closer to this: It shouldn't be possible. But it seems like it actually might be. And that's frightening.

Look at the face of someone asking "can this be done?" and you'll see anxiety before expectation. They're not asking because they want to hear yes. They're asking because they want to hear "not yet" — and feel reassured.

The ideas they bring up are almost never new. Wouldn't it be great if we could do this. If this were possible, everything would change. But these are ideas that only felt safe because they seemed impossible. Then the answer comes back: "Yes, you can. Quickly." And the next question turns inward. If it can be done — why haven't we done it? What were all those people, all that time, all that budget for? What have I been doing?

"It can all be done" isn't a confirmation of possibility. It's the elimination of excuses.

That's why the questions stop. You'd expect momentum — more questions, more energy. Instead, the room deflates. "Oh, I see. We'll look into it sometime." This isn't lack of interest. It's too much interest, and it's frightening. Confirming the possibility means the next step is a decision. A decision carries responsibility. And that responsibility might start with admitting that everything done until now was the wrong call. That chain of consequences hits all at once, so it gets shut down with "sometime."

Then come the objections. "The depth differs by domain." "Our industry is special." "Our data structure is too complex for simple application." All fair points. Not one of them is wrong. So I ask: "Are you waiting for better technology to come along?" The room goes quiet again.

"It may be wrong now, but it was right before." That's a real comfort — and not an incorrect one. Nobody is unaware it was right before. The problem is that it's wrong now. Organizations accustomed to change don't linger there. They acknowledge it, let it go, and move on.

The sharp executive opens the conference room door and says: "Want to step out and grab a coffee, just the two of us?"