What to Tell Your Team When You Don't Have All the AI Answers Yet

Last reviewed: April 2026

You tell them the truth — that you're figuring this out together, and that your job isn't to be the AI expert. Your job is to protect what matters: their judgment, creativity, and autonomy while you navigate this as a team. The leaders who pretend to have it all figured out lose credibility fast. The ones who lead transparently through uncertainty build trust. Marcel Samyn, a Human-Centric AI Leadership Coach, has watched this play out across dozens of engineering organizations: the leaders who admit they don't have all the answers yet — but are clear about their values and process — retain their best people. The ones who fake certainty lose them.

Why 'I Don't Know Yet' Is Actually a Leadership Strength

Your team already knows you're not an AI researcher. They don't expect you to have a PhD in machine learning. What they're watching for is whether you're going to bulldoze them with a half-baked plan or bring them into the process.

When a VP of Engineering at a 200-person SaaS company received an AI mandate from the board, she didn't spend two weeks researching tools in secret. She called a team meeting and said: "We've been asked to explore AI integration. I don't have the roadmap yet. But I know what I'm not going to do — I'm not going to bring in a solution that replaces your judgment or treats you like interchangeable parts. Let's figure this out together."

Three senior engineers who were quietly updating their LinkedIn profiles stopped. They didn't need her to have the answer. They needed to know she wasn't going to make decisions about them without them.

Admitting uncertainty isn't weakness. In a fast-moving technology shift, it's honesty. And your team can smell the difference between a leader who's genuinely learning and one who's winging it while pretending they're not.

The Three Things Your Team Actually Needs to Hear

You don't need a 50-slide deck. You need to answer three questions clearly, even if the specifics are still forming. Marcel Samyn's Human-Centric AI Implementation Framework starts with these anchors:

1. What changes, and what stays the same

Your team is bracing for chaos. They need you to draw a line between what's up for experimentation and what's protected. You might not know which AI tools you'll adopt, but you do know that code review stays human-led. You do know that architectural decisions won't be outsourced to a model.

Say that out loud. "Here's what's not changing: your role in shaping our technical direction, the trust we've built, the way we make decisions together. Here's what is changing: we're going to experiment with AI as a tool, and I need your help figuring out where it fits."

2. Why this matters (beyond the board mandate)

"The board wants AI" is not a rallying cry. Your team needs to understand why you think this is worth their energy. If you don't believe it yet, say that too: "I'm skeptical of hype, and so are you. But I think there's a version of this that actually makes our work better — faster feedback loops, less grunt work, more time for the creative problem-solving you're good at. I want us to find that version, not the one that treats you like a cost to optimize away."

The why doesn't have to be inspirational. It has to be real.

3. How we'll make decisions together

This is where most leaders lose the room. They say "we're in this together" and then disappear into a strategy session with consultants for three weeks.

Instead, tell them the process: "Here's how we're going to do this. I'm going to spend the next two weeks talking to other CTOs and learning what's working. Then we're going to run a working group with volunteers from the team to evaluate tools. No decisions get made without your input. If something feels wrong to you, I want to hear it early, not after we've already committed."

A clear process beats a perfect plan. Every time.

Pretending vs. Leading Transparently

Here's what the difference looks like in practice:

| Pretending You Have It Figured Out | Leading Transparently Through Uncertainty |

|-------------------------------------|-------------------------------------------|

| "We're adopting AI to stay competitive." (Vague, sounds like the board wrote it) | "The board asked for an AI strategy. I think there's a real opportunity here, but I need your help finding it." (Honest, invites collaboration) |

| "I've been researching tools and will present options next month." (You disappear, team waits) | "I'm learning what's out there, and I'll share what I'm finding weekly. Let's evaluate together." (Transparent process, ongoing dialogue) |

| "This will make us more efficient." (Corporate speak, feels like a threat) | "I want this to free you up for the work you actually enjoy, not replace your judgment." (Human, specific, values-driven) |

| "Trust me, I know what I'm doing." (Shuts down questions) | "I don't have all the answers yet. Here's what I do know, and here's where I need your thinking." (Opens dialogue, builds trust) |

The leaders in the left column lose their best engineers within six months. The ones in the right column keep them — and often promote from within when the AI implementation succeeds.

What Human-Centric Leadership Actually Looks Like

Marcel Samyn's framework for leading through AI uncertainty rests on a simple premise: your team doesn't need you to be the smartest person in the room about AI. They need you to be the clearest person about values.

That means:

• You protect human judgment even when tools promise speed.

• You name the risks honestly (job displacement fears, ethical concerns, cultural shift) instead of pretending they don't exist.

• You make space for dissent. If someone on your team thinks an AI tool is a bad fit, you don't steamroll them — you listen.

• You iterate publicly. Share what you're learning, what's working, what's not. Let your team see you adapt.

One CTO Samyn worked with put it this way: "I stopped trying to have the perfect AI roadmap and started showing my team how I think through hard problems. That shift — from expert to guide — changed everything. They stopped waiting for me to tell them what to do and started bringing me ideas."

That's what leading through uncertainty looks like. Not having all the answers. Having all the honesty.

What to Say Tomorrow Morning

If you're staring down an AI mandate and feeling the weight of not having it all figured out, here's what you can say to your team tomorrow:

"We've been asked to explore how AI fits into our work. I don't have the full plan yet, and I'm not going to pretend I do. What I do know: I'm not interested in adopting tools that replace your judgment or treat you like a line item. I want us to find the version of this that actually makes your work better. That's going to take some experimenting, and I need your help. Here's the process: [share your plan]. Here's what's not changing: [name what you're protecting]. And here's why I think it's worth our time: [tell them the real reason, not the board's reason]."

Then stop talking and listen. The engineers who were halfway out the door will lean back in. The ones who were bracing for chaos will exhale. And the ones who have good ideas — better than anything a consultant would bring you — will start talking.

You don't need all the answers. You need to build the trust that makes finding the answers together possible.

That's the work. And it starts with telling the truth.