Reporting Line

At ten people there's no need to define reporting lines. Everyone asks the founder and the founder answers. With one path, nobody is confused about where to take a question.

Past thirty the path clogs. One person can't hold thirty people's work in their head, so answers arrive late, and work stops while it waits for them. That's when someone gets placed in the middle — and the thing that has to be settled at that moment is who checks with whom.

Leave it unsettled and it fails in two directions. One is a seat where nobody answers. That happened to Noa at Pagedeck. She was checking design direction with Mia, while the person who wrote her half-year evaluation was someone else. On a screen where the two of them disagreed, Noa had no way to know which one to follow, and that decision slipped two weeks.

The other failure is two people handing the same person different priorities. Told today to do A first and B first, the person receiving both has to refuse one of them. A structure that leaves that refusal to the junior person ends up as a structure where the loudest request wins.

A reporting line exists to prevent both, which is why each person gets exactly one. Having several people to collaborate with and having several paths of accountability are different things, and conflating them is what produces the two failures above.

Each person gets one solid line, and that single line settles three things.

1. Authority over priority. When requests collide, this is the person who says what comes first. If a request from another team runs into work already committed, the call doesn't get made alone — it gets made with this person, which is also what keeps a junior engineer from having to say no to a director.
2. Authority to propose evaluation and pay. This is who writes the half-year evaluation and proposes the raise. When the person you check direction with isn't the person who evaluates you, you end up calculating which of them to work toward every time.
3. Approval authority. Leave, equipment purchases and outside spend all route through here. Larger amounts continue one level up, but the starting point is the same, and the routing is usually configured in software rather than agreed verbally.

How many people one manager takes on is called span of control — the headcount a single manager carries, commonly five to eight. Past twelve, holding a 30-minute private conversation every other week consumes six hours a week on its own, and the conversations survive while their content turns into status reporting. A manager at that size stops having time to read anyone's work closely, which is the part that makes the evaluation authority in point two hollow.

The depth of the hierarchy falls out of headcount divided by span. Forty-five people at six per manager produces two or three levels. Add a level and information from the ground passes through one more person on its way to the founder; remove one and each manager carries more people. The two numbers trade against each other, so they can't both be improved at once.

Four places. The first is the org chart — the diagram of teams and reporting relationships — where the solid lines are exactly these. A new hire reads that picture in their first week to work out who to ask about what, which makes an out-of-date chart actively misleading rather than merely untidy.

The second is evaluation. This line decides who writes the write-up, and by extension who sits in the meeting where managers align their standards. Anyone whose line changed mid-period needs a specific exception; a manager who has worked with someone for two months evaluating six leaves the first four months with no record behind them.

The third is system permissions. Document access, release approvals and spending sign-off get configured along this line. Change the line without changing the systems and people keep getting approvals from their former manager.

The fourth is reorganization. Lines are the first thing drawn in one. Rename the teams and leave the lines alone and the decision path hasn't moved, which produces exactly the speed the company had before. Drawing them, on the other hand, is where the manager with twelve reports and the work nobody owns become visible.

"Send that request through my reporting line so we can look at priority together."

Not a refusal — a statement that the trade-off won't be decided alone.

"The line changed, so move the approval settings over this week too."

Changing lines without changing systems leaves the old path running, often for months before anyone notices.

"Right now I check direction with Mia but someone else writes my review."

Reporting that two roles have split apart and need resolving, before the next disagreement forces the issue.

Pagedeck consolidated the line after what happened to Noa. The person she checks design direction with and the person who writes her evaluation became the same person, and her collaboration with Mia stayed as a per-project relationship rather than a line on the chart.

The same situation came up once more afterward. Two people disagreed about a screen flow, and this time the decision took a day. Noa didn't deliberate about whose view to follow; she took the question to her manager. The disagreement itself remained. What changed was who resolves it, and how long the person in the middle had to sit with it.

The most common reading is that a reporting line is a channel for issuing instructions — a pipe carrying work downward. What the line actually fixes is where accountability sits. Most work doesn't travel along it at all; it travels sideways. An engineer asks a designer, a salesperson asks an engineer, directly. In organizations that read the line as an instruction channel, conversations that could have gone sideways climb up and come back down, and each round trip costs a day. Managers there stop being people who divide work and become relays for every conversation, and that seat is the first thing to clog as headcount grows.

The other misreading is that two reporting relationships make things more flexible. Reporting formally to two managers looks like a way to honor both perspectives. But on the day their judgments differ, that structure resolves nothing. Two places to escalate a decision is the same as no place to escalate it. Where several working relationships genuinely are needed, the formal line stays single and the rest get marked separately, so that the obligation to stay aligned is visible without the authority being duplicated.