Who Should Actually Report to You
By VICKY BROWN
Look at your calendar for a second. Not your org chart, your calendar. Count how many people came to you last week for a decision, a sign off, or just a little reassurance that they were doing the right thing. Was it seven? Nine? Twelve? That number tells you something your org chart never will. If that many people are still routing every decision through you, you’re not running the company anymore. You’re running the switchboard, and figuring out who should report to the CEO is exactly what gets you off it.
Here’s where most founders go wrong before they even start untangling this. They ask themselves whether someone is important enough to report to them. But that’s the wrong question, and honestly, it’s not even a real question, because of course they’re important. You hired good people. That was never up for debate. The question that actually matters is whether a role needs your direction, your authority, and your accountability specifically, or whether it belongs under someone else who has more context to manage that person well day to day.
Those are two completely different questions, and almost nobody separates them on purpose. Instead, reporting lines tend to form by accident, out of habit, out of history, or out of something that feels like loyalty but is actually just inertia.
Why reporting lines quietly turn into rewards
It usually starts innocently enough. She’s always reported to you. He knows this business better than anyone else in the building. You trust her to tell you what’s really going on. All of that can be true, and all of it can matter, and none of it actually answers the organizational question underneath it, which is what this role owns, what decisions it should be making without you, and who else on your team has the context to support that person well.
A reporting line is supposed to serve the work. It’s not supposed to be a badge of honor. But that’s exactly what happens in a lot of growing companies. Someone performs well, so you pull them closer. You make them a direct report almost as a way of saying you see them, you value them, you trust them. And everyone else on the team is watching. They start to believe that proximity to you is the actual promotion, that reporting to the founder is the ceiling everyone’s supposed to be reaching for.
Which means the day you need to restructure, and at some point you will need to restructure, that employee feels it as a demotion. Even if their title stays exactly the same. Even if their pay doesn’t move an inch. Even if their day to day job doesn’t change at all. In their head, and in the heads of everyone watching, moving off your direct line reads as moving down, because you trained the whole team to read it that way without ever meaning to.
“…Access and reporting are not the same thing. An employee doesn’t need a direct line to you in order to be heard by you.“
Recognition and reporting are not the same thing
This is the distinction that untangles most of this mess. Recognition is compensation, title, visibility, real investment in someone’s growth. It is not automatically a reporting relationship, and treating it like one is where founders get stuck. You can absolutely tell someone they matter to this company without also making them your problem to manage forever.
And be careful with the promises you make in the moment. Telling someone “you’ll always report to me” feels generous when you’re saying it. But it’s also a promise you may not be able to keep if you actually want this company to grow past the size it is today.
So who genuinely belongs reporting to a CEO? Generally, it’s leaders who own real pieces of the business. People who bring you decisions, risks, recommendations, and results, not people who bring you a steady stream of tasks that need your direction to move forward. A useful test here is simple. If this role didn’t report to you, would their ability to actually get things done fall apart? If the honest answer is no, you’re probably managing them out of habit rather than necessity.
Access is not the same thing as reporting
I want to be really clear about this one, because founders get it backwards constantly. Access and reporting are not the same thing. An employee doesn’t need a direct line to you in order to be heard by you. You can build that access through leadership meetings, skip levels, project briefings, or a standing one on one that isn’t about running their day to day work. You stay informed without personally owning their workload.
This matters most with your longest tenured people and your subject matter experts. Their history is valuable. Their instincts are valuable. Neither of those things means you need to be the one approving their time off.
Whether you’re an entrepreneur jumping into a leadership role, a seasoned business pro with new HR responsibilities, or just starting your HR career – we’ve got the right path to guide you through your HR hurdles.
Check out the Leaders Journey Experience.
The three shapes this usually takes
The first is the early employee who’s been with you since the beginning, back when everyone wore five hats because the company was small enough to require it. The business has grown around them. Most of what they touch now actually lives inside someone else’s department. But they still report to you, because that’s simply how it’s always been. Honoring someone’s history is good leadership. Letting that history run your org chart indefinitely is not.
The second is the strong leader you finally hired to run a department, except you kept one or two favorites reporting straight to you anyway. Now that leader is accountable for results in a function they don’t fully control, and the employees still reporting to you know exactly where the real power sits. The moment they don’t love a decision, they know whose door to knock on. You didn’t set out to undercut your new leader. The structure did it for you.
The third is the specialist whose work is genuinely high stakes, so you assumed high stakes automatically meant they needed to report to you. Usually what they actually need is scheduled access, a seat at certain tables, and a clear escalation path, not you managing their Tuesday.
Making the change without pretending it’s small
If any of that sounds familiar, ask yourself honestly what’s really holding your current setup in place. Is it the work itself? Or is it history, or trust, or the fact that the other leader isn’t quite ready yet, or, and it’s worth just saying it plainly, the fact that you don’t want to have the conversation.
A reporting line should never be the thing you hide a harder problem behind. When you do make the change, don’t pretend it isn’t a big deal to the person on the other side of it. It might be, even when nothing about their title or pay changes. Explain the why. What business need this serves, what they still own, how their access to you works going forward. Let them ask questions. That doesn’t mean the decision is up for a vote.
And then actually let go of it. If you’re still quietly approving decisions behind the new manager’s back, still hearing the complaints directly, still making the exceptions, you haven’t actually changed anything. You’ve just made it look changed on paper.
A company can’t build real leadership beneath you if every trusted person and every sensitive issue keeps finding its way back to your desk. At some point, deciding who should report to the CEO comes down to being honest about what genuinely needs to sit at the top, and what belongs with the capable people you hired to carry it. If you built this company today, for the business you’re actually becoming, would this role still report to you? If the answer’s no, that’s not a failure. That’s just information, and what you do with it is up to you.
Spread the word
MORE HUMAN, MORE RESOURCES
310.308.7680 option 1
hello@idomeneoinc.com