Great Leadership Isn’t Having All the Answers

Rob Cramer · 3 min read

Here’s something I believe, and it’s shaped every team I’ve run: great leadership isn’t about having all the answers. It’s about empowering others to find them. The leaders who need to be the smartest person in the room eventually become the ceiling on their own team.

“I don’t know yet” is a leadership skill

Early on, a lot of new leaders treat questions as tests — as if admitting a gap costs them authority. It’s the opposite. A leader who says “I don’t know yet, here’s how we’ll find out” gives the team permission to think. A leader who bluffs teaches the team to hide problems until they’re too big to hide.

That takes emotional intelligence more than it takes expertise. Knowing when someone needs an answer, when they need a sounding board, and when they need you to get out of the way — that’s judgement, and it’s most of the job once you’re leading people instead of doing the work yourself.

What you owe people instead of answers

Empowering people doesn’t mean abdicating. What a team needs from its leader isn’t an answer key — it’s clear expectations. What good looks like. Where the boundaries are. How they’ll be measured, and how often you’ll sit down and talk about it. Get that right, and capable people will surprise you with the answers they find. Get it wrong — vague targets, shifting standards — and even strong people stall, because they’re guessing at what you want.

And when the answer is the process

Sometimes the honest answer to “why is this failing?” is that the process is broken, and no amount of effort will outwork it. Leaders earn their pay by hearing that.

At Rogers, I built the Attendance Manager role from scratch during the Shaw–Rogers integration — a function that coordinated HR, Payroll, Scheduling and Team Leads, without direct authority over any of them. The leave-case ticketing process took 8 steps. We cut it to 2. Return-to-full-duties timelines got an average of 4 business days faster, and Team Leads saved about 2 days per case. Nobody worked harder. The process stopped wasting their effort.

Same pattern at Shaw: I helped establish the QA protocols and created the QA documents used to evaluate interactions, so feedback ran on a shared standard instead of whoever happened to be listening. When the metrics or the floor point at a broken process, the leader’s answer is to fix the process — and to know the difference between a people problem and a process problem in the first place.