Your Team Knows the Answer. The Waiting Is Something You Built.

The hand goes up

You ask a question in a meeting. You watch the answer land on someone's face. They have it. They have had it for a while, probably.

And then they wait.

Not because they are timid. Not because they do not care about the outcome. Because the organization taught them that thinking is your job and doing is theirs. They learned it from you, gently, one answered question at a time.

Here is the part most owners miss. That wait is not a personnel problem. You cannot hire your way out of it. You cannot motivate your way out of it. It is a design problem. Your team waits because nothing in the system tells them they are allowed to move.

The wait is not a knowledge gap. Your team is not short on talent. It is short on ownership, permission, and a way to know whether it was right.

The fix is Organizational Independence.

Organizational Independence: building a company that can think without you. A stronger organization. A freer you.

That is not a pep talk. It is an operating system with three parts, a loop, a ground, and a container. And it comes with a bill.

Waiting is the rational move

Before you decide your team is passive, sit inside their seat for a minute.

Nobody has said this call is yours. There is no written vision on the wall to check a decision against. There is no clear line for who owns what thinking, so everything routes up. And there is no way to tell afterward whether the decision was good, because success is whatever you say it is this week.

Inside that system, deferring to you is not cowardice. It is the low-risk play. Waiting is smart. You built a company where the safest thing a competent person can do is stop.

Now flip it. Same person, different system. They know where we are going. They know which decisions are theirs. They know how we decide when it is not obvious. And they know what the scoreboard says. That person does not wait. That person moves, and you hear about it after.

The shape of it

Three questions, asked in order. A loop that returns to the start. The whole thing running inside how the company thinks, and standing on trust.

1 · Alignment. Do we know where we are going and what we own?

Under it: a vision, meaning a clear and compelling future. An org chart that names who owns what thinking, not just who reports to whom. And a focus mechanic, the Theory of Constraints, which says you find the one constraint actually holding the company back and point everyone at the Big 3 instead of the Big 30.

What gets worse first: the org chart. Naming who owns what thinking means taking ownership away from you, in writing, where everyone can see it. And a Big 3 means saying no out loud to the other 27 things, to people who care about them. Week one of alignment looks like an argument about a list, and you lose most of it.

2 · Movement. Can they decide and act without me?

Values, so our principles guide the call when you are not in the room. Frameworks, simple ways to think and act that people can run on their own. Culture, a team that improves together instead of performing for you.

What gets worse first: the first decisions your team makes without you will be worse than the calls you would have made. That is not a bug, it is the tuition. And someone will use a value you wrote to argue with you, in public. Overrule it once and the whole thing is a poster again.

3 · Measurement. Can we tell if we were right?

Start past the end, which means define what success looks like before you map the path to it. And everyone has a KPI, so each person has a signal about whether their call was good.

What gets worse first: nothing, if you get the order right. Get it wrong and you find out fast. Never hand out KPIs before alignment. You will get a team optimizing something that does not matter, faster than before. A scoreboard on the wrong game is worse than no scoreboard at all.

Then the loop closes. What you learn in measurement goes back into alignment, and the questions get sharper the second time.

Gary refused the premise

I used to think the answer was hiring people who already held the answers.

Thirty years ago I was a young software architect running software teams, and I hired the way I judged myself. Random hard technical questions. The answer expected off the top of your head. That was the standard, because holding the answer was what I could do.

Then I interviewed a developer named Gary.

He did not fail the question. He refused it. He looked at me and said, young man, I do not know the answer to that off the top of my head. However, I know the answer is in that book on your bookshelf right now, and so when that question comes up, I am just gonna go pull that book off the bookshelf and look up the answer.

I hired him. We became friends. And the standard I had been screening for turned out to be the wrong one.

On my own rule, I reject Gary. I keep staffing for recall, and I never learn that knowing the route to an answer beats holding the answer. Then I teach my systems the same bad habit: needing to already know instead of being willing to ask.

That is how a team ends up waiting on one person. Not because they are slow. Because I built the interview that said the answer lives at the top.

What it costs you

The first weeks after you stop answering will be slower. You will watch somebody make a call you would have made differently. It will cost you something. You will feel a pull to grab the wheel back, and you will tell yourself you are just protecting quality.

What is actually happening is this. Being the answer has been your proof of value. If they can do it without you, what exactly are you for?

That is the real resistance, and it does not live in your team. It lives in you.

Now the honest math on speed. There are only two ways to change a culture. Replace the people, or steer the ones you already have.

If you were building from scratch, you would hire for this and the culture would be right on day one. You are not building from scratch. You are standing on a deck with a crew that is already aboard. They have habits. They have a history of being told what to do, and it has worked for them. A few of them got promoted for waiting well. You cannot turn that by announcing empowerment on a Tuesday.

Twelve months is not a padded timeline. The reporting behavior you are asking for is a culture change, and culture does not respond to a switch. You can replace the crew, or you can steer the ones already aboard. There is no third option, and no faster version of the second one.

So when someone tells you the reporting change will take a year, that is not padding and it is not a stall. Reporting behavior is culture. Culture moves through a thousand small moments where the new way holds and nothing bad happens.

If you are not willing to replace the crew, you already chose the slow path. Being impatient with it now is being impatient with a choice you made.

Shaina asked the wrong person

Even after you fix the hiring, an old rule can keep your team waiting.

Shaina Ballesteros wanted to know whether Athena could tell her, weekly, when the newsletter got no replies. She assumed Athena had no access to that data. So she asked Stephanie instead, and Stephanie sent her to me.

When Shaina finally asked Athena directly, Athena gave her a wrong answer. It said it had no access when the truth was that Shaina had no access.

That wrong answer was the most useful thing in the meeting. It was the only way I could find the missing rule and fix it. I told her: it is good, but that is why I need you to ask her. So that when you ask her and you get this answer, then I can then help her be better to answer you next time, so she can be smarter.

Here is what the detour cost. A broken rule sat undiscovered. Shaina waited two weeks on stale content. Stephanie and I both spent time on a question the tool was built to answer.

That is the loop, and it only turns if somebody hands the mess back. A wrong answer from the system is not a failure. It is the bug report. You take the exact conversation to the person who can change the rule, and the rule gets better for everyone behind you. Route around the system by asking a human, and the rule never changes. The next person hits the same wall.

So the question for you is not whether your team has the answer. It is whether your system makes asking dangerous. Because if a wrong answer costs someone something, they will stop asking, and they will come to you instead. Which is exactly what you said you did not want.

Where to put your energy

Rank these. The org chart question is the one that matters most. Who owns what thinking. Answer that and half the waiting stops on its own, because people stop routing to you decisions that were never yours. Movement is the slow one, and it is the one that decides whether the other two hold. Measurement is the least urgent early and the one owners over-invest in first, usually because a dashboard feels like progress.

When not to do this: if you are genuinely the only person holding the information and the cost of being wrong is existential, you do not have an independence problem. You have a knowledge transfer problem. Fix that first, and be honest about which one you are in. Most owners are not in the second version. They just like being needed.

The choice

You are not going to install your way out of this. No tool makes a team stop waiting, because waiting is not a tool problem. It is a system problem, and you are the system's author.

Two ways to change a culture. Replace the crew, or steer the ones you already have. You already chose the second one, because you are not firing everybody. That means a year, not a quarter. It means watching calls you would have made differently get made anyway, and letting them stand.

And it means giving up the thing that has been quietly paying you. Being the answer. If they can truly do this without you, what are you for? You have to answer that one yourself, and no dashboard will help.

A stronger organization. A freer you. But the order matters: alignment, then movement, then measurement. So start with the org chart this week. Write down who owns what thinking, and be honest about how much of it still says your name.

Your team is not waiting because they are slow. They are waiting because you built a system that pays them to.