Skip to Content

What does your team think when you're not in the room?

Мислил ли си някога какво си говорят хората за твоя бизнес? Вероятно не си, и това е най-голямата грешка
April 16, 2026 by
Tsvetelina Stoyanova

A few days ago, someone I respect said something about my work that I hadn't been able to articulate myself. Not a client. Not a partner. Just someone who listens carefully and speaks rarely. He said: "The thing that struck me most is that you answer a very important question — what does your team think about the business when you're not in the room?"

That was it. One sentence. And it held everything I do, everything I've been trying to explain for months, everything this diagnostic exists for. Not an elegant methodology. Not a clever framework. One question that no business owner knows the answer to — and that very not-knowing is the reason they work harder than anyone else in their own company.

I thought long and hard about whether to write this piece. Not because I had nothing to say, but because I know how easily the subject slips. Another article about leadership. Another explanation of why you should listen to your people. Another text you nod along to and then do nothing about. I don't want to write that kind of text. I want to tell you what actually happens when you stand in front of the two versions of your business for the first time — and they don't match.

Every owner I've worked with has their own version of the business. It's orderly, logical and hard-won. They know who does what, where the weaknesses are, who needs replacing and who's worth keeping. They tell it convincingly. Sometimes even beautifully. And almost always — incompletely.

Not because they're lying. Because they see from one single vantage point — the top. And from the top, things look a certain way. You see the decisions you make. You see the tasks you check. You see the emails you rewrite at two in the morning because this time it's an important client. You see the version where you're at the centre of everything — and you accept that this is the business.

And then you go down.

Not you. I go down. Because you can't. Not physically — structurally. You're the boss. When you walk into the room, the conversations stop. Not because people hate you. Because they've learned it's safer to stay quiet. You didn't teach them that. The system taught them. The system you built yourself, without realising you were building it.

When I walk into a business, I don't bring a questionnaire. I don't bring a framework. I don't bring a theory about the five levels of delegation or somebody's matrix. I bring one thing — silence. I sit with every member of the team individually. Two to three hours each. Anonymously. Without the owner knowing what they said. And I ask questions that sound so ordinary most people don't understand why I'm asking.

What does a normal Tuesday look like? What do you do from morning to evening? The last time something got delayed — what happened? If the boss didn't show up tomorrow — what stops?

Ordinary questions. Extraordinary answers.

Because when someone describes their day to a person who isn't evaluating them, isn't checking up on them and can't fire them — they say things they would never say to the boss. Not scandalous things. Not complaints. The truth. The quiet, everyday, invisible truth about how the business actually runs when the owner isn't in the room.

Let me give you an example. Not from a specific client — from the pattern that repeats so predictably it no longer surprises me.

The owner says: "I delegated it to him. He won't take responsibility."

The employee says: "I suggested it three times. Three times he said no. The third time — in front of everyone. I don't suggest things any more."

The same moment. Two different stories. And neither one is a lie. The owner genuinely believes he delegated. The employee genuinely stopped suggesting. Both are right from where they stand. But the two places can't see each other.

That gap is the delta. Not a metaphor, not an abstraction — a concrete, measurable, documented discrepancy between the owner's version and the team's version. And it explains nearly everything: why the phone calls never stop, why decisions keep travelling upward, why people wait instead of act, why the owner works seventy hours a week and wonders whether he's simply surrounded by the wrong people.

He isn't surrounded by the wrong people. He's surrounded by a system designed to make him indispensable. Not deliberately. It just happened that way while he was building.

I know what you're thinking. You're thinking yours is different. That you really did delegate. That your people genuinely lack initiative. That your manager genuinely won't step up. Maybe so. But I've spoken to enough teams to know that in eighty per cent of cases the owner is certain they know — and the document shows otherwise.

Not because they're blind. Because they're at the top. And the problems are at the bottom. The only way to see them is to go down. And the only way to go down is for someone else to do it for you. Because when you go down — the conversations stop.

There is one moment that repeats with every client. Not at the beginning — at the end. When they receive the document. When for the first time they see the two versions side by side. Their own and the team's.

The first two or three minutes they're silent. Not because they're shocked. Because they recognise it. They see things they suspected but never heard said aloud. They see people they thought were weak who had simply stopped trying. They see decisions they thought were theirs that had long been made by someone else — only no one told them, because no one had permission.

And then comes the sentence I hear every time, in different words but with the same meaning: "So the problem isn't them. The problem is how I built it."

Yes. Exactly. And that's not a verdict. It's a diagnosis. Because if the problem were the people, you'd have no solution — you'd need to replace everyone. But if the problem is the architecture — architecture can be changed. Without replacing the people. Without replacing yourself. You simply change the way decisions, information and responsibilities flow inside.

I'm not writing this to sell you something. I'm writing it because the question "what does your team think when you're not in the room" deserves to exist outside the context of my service. Even if you never work with me — think about it. Not in the abstract. Concretely. Tomorrow, when you walk into the office, notice how people stop talking. Not because you're paranoid. Because it's true. They stop. Not out of fear. Out of habit. The habit is called "the boss is here, so he decides."

And you don't want to decide. It's just that no one else has permission.

The person who said the question isn't my client. He hasn't paid a penny. He was simply listening, and he saw something I'd been searching for for months. He saw it because he was on the outside. Just as your team sees things you don't — because they're underneath. Different vantage points. Different versions. The same company.

The gap between those versions isn't a problem that should frighten you. It's information you need to have. On paper. With specific names and specific actions. Not "improve your communication." But: stop reviewing Ivan's emails to clients, hand Maria the budget up to two thousand, replace six daily phone calls with a fifteen-minute weekly meeting with the foreman.

Concrete. Measurable. Actionable tomorrow morning.

What does your team think when you're not in the room?

You don't know. And that's exactly where it begins.

in News
Tsvetelina Stoyanova April 16, 2026
Share this post
Tags
Archive