Nobody Can Tell You If Last Quarter Worked, So They Wait to Be Told
By Atiba de Souza

The room turns to you
End of quarter. Someone walks the team through the numbers. Real numbers. The ones you asked for.
Then the room turns and looks at you.
Not because they can't read a slide. Because they don't know which number counts, what would have made the quarter good, or whether what happened was a win or a wobble. That part has always come from you.
Nobody in that room will say "I don't know if last quarter worked." They'll say "we'll see how next quarter goes," or "that's a great question," and then they wait for you.
If that scene is familiar, don't fix the deck. You have a system problem, and the system is you.
The name for it
Organizational Independence: building a company that can think without you. A stronger organization. A freer you.
That's the definition and the outcome in the same sentence. Not "the founder delegates more." Not "the team feels empowered." Building a company that can think without you.
It runs as three questions, in order, and then a loop.
- Alignment. Do we know where we're going and what we own? Vision, the org chart, the Big 3.
- Movement. Can they decide and act without me? Values, frameworks, culture.
- Measurement. Can we tell if we were right? Start past the end, and everyone has a KPI.
Then a learning loop that returns into alignment, so the organization gets smarter on its own. All of it inside the Brain. All of it standing on Trust.
Waiting to be told looks like a Measurement failure. It gets created in Alignment. That's the most important sentence in this piece, and everything else here is a variation on it.
Waiting is not a personality trait
Nobody joins a company hoping to sit in a meeting and look at the founder for answers. That behavior got installed.
Somewhere back there, someone made a call, and then you remade it in the room. Someone called a win a win. You asked three questions that made it clear it wasn't. It didn't take many rounds. People learn fast when the lesson stays consistent.
So understand what's actually happening when the room turns to you: they're being efficient. They've learned the verdict comes out of your mouth, and building an argument they're going to lose costs them a week they don't get back. Waiting is the smart move inside a system you designed.
The price shows up later. The learning loop can't run. It's supposed to carry measurement back into alignment so next quarter starts smarter. If only you can produce the measurement, that loop runs through your calendar instead of through the company. Your calendar is a terrible place to keep a loop.
What it cost me to be the only instrument
I run Big 3 planning. Quarterly, for myself and with clients.
Internally, it took two days. That was the number I built the process around. With clients I got it down to a day, and it was still hard, because when do I have a full day to give anyone?
Then the arithmetic catches up with you. At a day per client, how many clients can ever get quarterly planning? As many as fit in my calendar. Not as many as wanted it. Most of them simply never got it, and that was never a demand problem. Demand was not on the table. My hours were.
Then Athena started running it. Internal quarterly planning now takes four hours.
2 days. 1 day. 4 hours. Planning ran two days internally. A day per client, and a full day of my attention was still hard to give anyone. With Athena running it, internal planning lands in four hours. The thing being rationed was never demand. It was me.
Same work. Same rigor. Nothing about the thinking got easier. What changed is that the thing which had been rationed stopped being rationed.
Now sit with that, because the same arithmetic is running inside your quarterly review. A service is being rationed: the service of knowing whether the work worked. It's priced in your attention, so it gets handed out in the small quantities your calendar allows. The team isn't hoarding the answer. You are. Not on purpose, and not maliciously. By design.
Before you try to get more honesty out of the team, measure what the truth costs in your own hours. Then take yourself out of the delivery.
One question changed the whole room
I run a two-day pharmacy AI workshop. Halfway through day one, I could feel people starting to fall behind.
Not because the work was hard. Because no adult, sitting in a room full of their peers, will raise a hand and say "I'm stuck."
So I changed one question. I had been asking, "is everyone here yet?" I started asking, "who hasn't done this yet?"
Same room. Same people. Same work. The people who were behind began identifying themselves.
Think about why that worked, because it's the whole lesson. "Is everyone here yet?" asks the room to confirm something. In a room of peers, the honest answer is also the expensive answer, so you get a silent yes. "Who hasn't done this yet?" turns not-there-yet into a normal place to stand. It's a description instead of a confession. You made the honest answer the easy answer.
Now put that question inside your quarterly review. "Did the quarter work?" behaves exactly like "is everyone here yet?" You get a silent yes and a room full of people looking at you.
Try: "Whose number didn't move, and what do we think stopped it?"
You don't have to fix the people in the room. You have to fix the question.
You never had enough signal to divide
Here's the version of this I use all the time. One sign-up cannot tell you which marketing channel works. Not because the channel is bad. Because one sign-up is one sign-up. You cannot divide up an audience you never had. If you want to know where the leads came from, you need leads first.
Your quarter has the same shape. If your company produces one verdict per quarter, and the verdict is you, you have one data point. You can't attribute the quarter to anything. You can't separate the new hire from the price change from the market. Not because you're bad at analysis. Because there was never enough signal to divide.
Attribution without volume measures nothing.
And here's the sharper half of that idea. A good idea aimed at a non-constraint is still waste. Test every idea by asking what actually changes in the system if it works.
Which brings us to the dashboard, the metrics meeting, and the analyst you're thinking about hiring.
If the honest answer to "what changes in the system if this works?" is "I still declare the verdict," then nothing changed. You bought a nicer-looking version of waiting.
So the decision on Monday is this: don't build the analytics layer yet. Not because dashboards are bad, and not because the analyst wouldn't help. Because you'd be aiming a good idea at a non-constraint. One verdict per quarter is one verdict per quarter, no matter how beautifully it's rendered. Get the number into more than one pair of hands first. Then the dashboard has something to divide, and Volume, Cod and Automation can do their job instead of decorating a bottleneck.
The part nobody writes down
Now the resistance, because a clean process handed to you as if you'll simply adopt it is a lie.
There's a part of you that likes being the one who knows. It isn't vanity. It's survival. There was a stretch where you were the only person who could see around the corner, and that is part of why the company still exists. Your read of the room is a real advantage.
So when I say "let someone else declare whether the quarter worked," here's what it sounds like in your body: become unnecessary.
That's the fear. Sit with it for a second. I'm not going to hand you a sentence that makes it go away, because I don't have one. You spent years becoming the person who knows, and the thing being asked of you now is to become the person who doesn't have to. Those two people want different things from the same meeting.
Here's the bill, and there's no version of this where you skip it. You will sit in a review, hear a number you disagree with, and not correct it in the room. You'll take it to that person afterward. You will let someone be wrong for a full quarter, on purpose, because being wrong out loud is how a person learns to be right without you. Before the quarter starts, you'll spend real time defining what "worked" means, at the exact moment defining anything feels like a luxury.
Also expect the first KPI you hand out to be wrong. Not a little off. Wrong. That matters less than it feels like it does, because a wrong number in someone else's hands can be fixed, and a perfect number in your head can't be seen by anyone.
And here's the part I can't resolve for you. You won't know whether it worked until after you've already paid for it. There is no pilot quarter. You hand over the verdict, you find out later whether they were ready, and you live with the answer either way.
Fix Alignment first, and yes, that costs you too
I'm about to hand you a sequence, and I want to be honest about its price before I do, because "just fix Alignment first" sounds free and it is not.
Look at what Alignment actually asks: write down what winning looks like, before the quarter starts, with the people who will be graded on it. That means committing to a definition in front of your team, in writing, early enough that being wrong about it will be visible. That's the sting. A fuzzy quarter lets you be right in hindsight. A written definition takes that away from you permanently.
Alignment also deletes something you've been enjoying: the late save. When a quarter goes sideways and you redefine what mattered, right there in the room, that feels like leadership. It's a rescue. Written alignment takes the rescue away before you need it.
That's the cost. Now the sequence.
If you only fix one layer, fix Alignment. Start past the end. The waiting nearly always traces back to a quarter that began without anyone writing down what winning would look like.
Measurement is where the problem shows. Movement is what carries it. The tool is minor. The cadence is minor. The dashboard is minor. One sentence, written before the quarter starts, is not minor.
And here's when not to do this. If your team can't tell you the company's Big 3, don't hand out KPIs yet. You'll be putting numbers into people's hands that don't connect to anything, and they'll learn that numbers are noise. Fix the alignment first, then hand out the numbers.
Wait to be told vs. tell each other
| Wait to be told | Tell each other | |
|---|---|---|
| Who declares the verdict | You, in the room | The person who owns the number |
| Where the quarter's meaning comes from | Your read of the room | A definition written before the quarter started |
| What "I'm not there yet" costs | A confession in front of peers | A description of where someone stands |
| What happens when someone is wrong | You correct it live | They find out afterward and fix it themselves |
| When the disagreement gets handled | In the meeting, from the front | Afterward, one to one |
| What next quarter starts from | Your memory | The last measurement, carried back into Alignment |
| Whether the company gets smarter | Only as fast as your calendar | Every quarter, without you |
The loop closes when you're not standing on it
The learning loop is the whole point, and it's the part most leaders never finish. Alignment sets the direction. Movement gives people the ability to act. Measurement tells you whether you were right. Then the measurement has to travel back into Alignment and change something: the Big 3, the org chart, who owns what thinking. That round trip is what makes a company smarter. Without it, you're just running quarters in a circle.
When you're the only one who can declare the verdict, the loop still runs. It just runs through you. Measurement enters your head, gets metabolized privately, and comes back out as a new direction you announce. The organization never touches the middle of it. That's why the room waits. They're downstream of a loop they can't see.
Here's what the loop looks like when it runs without you. Someone owns a number. The quarter ends. They read their own number against a definition that was written down before they started. They say, in the room, what they think it means and what they think should change. Someone else disagrees, and the two of them work it out. You hear about it afterward, maybe. The change goes back into Alignment, which is to say the Big 3 shift, or an owner changes, or a piece of thinking moves to a different desk.
Look back at the diagram. That arrow running from Measurement back into Alignment is the entire article. If you're standing on that arrow, the loop has a bottleneck, and the bottleneck is a person. Take yourself off it, and the same loop runs a little faster every quarter, because now it's a system learning instead of a founder learning.
That's the payoff. Not a dashboard. Not a meeting. The verdict shows up in the room before it shows up in your head.
What to do Monday
The first quarter you do this won't feel like freedom. It'll feel like a loss of control, because it is one, and because you're giving up the thing that made you valuable in the first place. Some of that feeling is accurate. Expect it and don't let it talk you out of the decision.
What waits on the other side is the outcome the definition promised. A stronger organization. A freer you.
Pick one number. Write down what it would have to be for the quarter to count. Hand the verdict to whoever owns it. Then sit in the room, keep your mouth shut, and watch what the company does when it thinks without you.