Direct Reports: What They Are and How to Manage Them

The first time I had direct reports, nobody told me. There was no announcement and no title change. We hired a fourth person, and at some point I realized that four people were waiting on me to tell them what mattered this week, and that I had no system for doing it.

What I did have was a lot of advice written for managers at companies with an HR department, a career ladder, and a performance management cycle. None of it addressed the actual situation: that I was doing the managing between everything else, that the people reporting to me were often better at their jobs than I would have been, and that the reporting structure had happened by accident rather than design.

This guide covers what the term actually means, how direct reports differ from indirect ones, how many one person can realistically have, and what to do when the answer is more than you should. The management sections assume a founder or team lead doing this alongside another full-time job, because at 5 to 50 employees that is who is doing it.

What Is a Direct Report?

A direct report is an employee who reports directly to a manager, with no other person in the reporting line between them. That manager sets their goals, holds their one-on-ones, gives them feedback, approves their time off, and is accountable for how they perform. If four people come to you when they need a decision about their work, you have four direct reports.

The term is used as a noun for the person: she has six direct reports, or he is a direct report of the operations lead. The singular and plural mean the same thing, and phrases like direct report meaning or what does direct report mean all point at this same definition. It is one of those pieces of workplace vocabulary that everyone is assumed to know and nobody explains.

Two things the term does not mean. It does not indicate anything about a person's value, expertise, or standing. And it is not the same as someone whose work you are involved in. If you review a designer's output but their manager decides their goals and their raise, they are not your direct report regardless of how much you interact.

Direct Report vs Indirect Report

An indirect report is someone who sits below you in the organization but reports to somebody else who reports to you. The distinction is about where accountability sits, and it becomes practically important the moment a company grows past one management layer.

In the structure above, the founder has four direct reports and seven indirect reports, for a total organization of twelve people. This is what an organizational chart represents visually: each solid line running downward marks a direct reporting relationship. The operations lead has three direct reports of their own. When a coordinator underperforms, that is the operations lead's responsibility to address, not the founder's. When the operations lead underperforms, that belongs to the founder.

The row that causes the most trouble at small companies is the last one about involvement. Founders who appointed their first manager often continue giving instructions directly to that manager's team, because it is faster and because they know the work. Every time this happens the reporting line weakens, and eventually the manager has a title without authority. The organizational structure guide covers how reporting lines fit into the wider design.

What Having a Direct Report Actually Means

The reporting line is not an administrative fact. It carries a specific set of responsibilities, and most first-time managers at small companies are aware of two or three of them and unaware of the rest.

The first one is the one that gets skipped. Setting expectations feels unnecessary when everyone sits in the same room and the work is obvious, so it does not get written down. Then a capable person underperforms for three months, and the diagnosis on inspection is almost always that they were doing what they thought the job was rather than what you thought it was. The roles and responsibilities guide covers how to define this without turning it into a corporate exercise.

Why the Reporting Line Matters More Than It Looks

At a fifteen-person company it can feel like formalizing who reports to whom is unnecessary bureaucracy. Everyone knows everyone, the founder is available, and things get done. That works until it does not, and the failure mode is specific: nobody owns the problem.

When reporting lines are undefined, three things happen predictably. Performance problems go unaddressed because it is not clearly anyone's job to raise them. Good people leave without warning because nobody was having the conversation that would have surfaced the issue. And decisions stall because the person who could make them is not sure they have the authority.

There is also a practical reason that has nothing to do with management philosophy. Reporting lines determine who approves time off, who signs off on hours, who conducts the performance review, and who makes the call in a termination. When those are undefined, the administrative work either does not happen or defaults to the founder, and both outcomes create problems that show up later.

How Many Direct Reports Should You Have?

The research consensus lands in the range of five to ten, with something around seven often cited as the practical sweet spot. That number moves depending on how complex the work is, how experienced the people are, and how much of the manager's time is actually available for managing.

The real-world numbers run higher than the recommendations. Gallup found the average number of people reporting to a manager rose from 10.9 in 2024 to 12.1 in 2025, close to a 50 percent increase since it first measured in 2013. But the median has held steady at about five to six, meaning a minority of very large teams pulls the average upward while most managers still lead small groups. Gallup also cites Bureau of Labor Statistics data showing roughly one manager for every 11.5 employees.

For a founder specifically, the honest number is lower than most articles suggest, because the comparison is not against a full-time manager. If you have eight direct reports and you are also selling, handling finance, and doing the work you are best at, then in practice each of those eight has a part-time manager. The span of control guide covers the calculation and the benchmarks by team type in more depth.

Six Traps Founders Fall Into

These are the patterns that show up repeatedly at companies between five and fifty people. None of them come from bad intent. They come from a founder doing something that worked at five employees and continuing past the point where it stopped working.

The fourth one is the most common and the hardest to stop. You appointed someone to lead operations, and then a question came up on a Tuesday and you answered it directly because the lead was busy and you knew the answer. Reasonable in isolation, corrosive when repeated. The people management guide covers what changes when you stop doing the work and start managing the people doing it.

Running One-on-Ones With Direct Reports

The one-on-one is the mechanism that makes a reporting line real. Without it, the relationship exists on an org chart and nowhere else. The research is consistent that regular manager conversations are strongly associated with engagement, and the practical experience at small companies matches it: the problems you find out about early are the ones that were raised in a recurring conversation.

The single most useful question to ask is what is getting in your way, followed by actually removing the obstacle. If the same thing comes up twice and nothing has changed, the person will stop raising it, and you will have converted a working feedback channel into a status meeting. The one-on-one meeting guide has the full agenda structure and question sets.

When to Add a Management Layer

Most founders add their first management layer later than they should, because adding one means giving up direct contact with people whose work they care about. The signals below are the ones worth watching for, and any two of them appearing together is usually enough.

The headcount trigger is roughly ten to twelve direct reports for a full-time manager, and lower for a founder who is also doing other jobs. But the count is a proxy rather than the actual criterion. The real question is whether each person has a manager who knows what they are working on, notices when something is wrong, and has time to do something about it. When the answer stops being yes for two or three people, the structure has already outgrown itself.

Adding a layer has a cost worth naming. You lose direct visibility into work you previously saw firsthand, decisions get made you would have made differently, and information reaches you later. All of that is real and none of it is a reason to keep fifteen direct reports. The flat organizational structure guide covers the tradeoffs when a company deliberately delays adding layers.

Appointing Your First Manager

The most common way this goes wrong is promoting the strongest individual contributor as a reward and assuming the skill transfers. It does not. Managing is a different job with a different set of abilities, and a great technician who becomes a mediocre manager has usually been made worse at both.

Give the new manager training if you possibly can. Even a short course on running one-on-ones and giving feedback produces a better outcome than learning by trial on real people. The leadership training guide covers what to prioritize, and the new manager onboarding guide covers the first ninety days in the role.

The Direct Report Management Template

A working document covering the reporting map, the expectations conversation, the one-on-one structure, and the quarterly review of whether the structure still fits.

Part 1 is the one to do first. Almost every founder who fills it in finds at least one person with no clear manager or one with two, and both situations tend to have existed for months without anyone noticing.

Edge Cases That Come Up at Small Companies

The classification question is the one with real financial exposure attached. The employee versus contractor guide covers the tests, and getting it wrong is considerably more expensive than getting the org chart wrong.

The administrative side of reporting lines is where a business without an HR department loses time repeatedly: who approves time off, who signs off on the review, where the org chart lives, and whether it reflects reality. FirstHR holds the employee records, reporting structure, and review cycles in one place so the answers do not depend on whoever remembers.

Frequently Asked Questions