Dotted Line

When an org chart had only one kind of line, every person sat under exactly one other person. The same manager assigned the work, approved the time off, and wrote the review, so nobody had to work out whose instruction came first. At twenty people that arrangement was enough.

It broke as soon as people from the same craft got spread across several teams. Pagedeck had been organized by function — designers with designers, engineers with engineers — and when it recut the company by product, its four designers ended up one per team.

The cost showed up a few months later, when it turned out nobody was looking at design as a whole. Noa spent three months on the document editing team without once reviewing a screen with the person who had been doing design the longest, and in that time the four teams drifted to four different corner radii on their buttons. Moving Noa back under design would have fixed the drift and broken something else: the product team would no longer control its own designer's schedule and would have to file a request for every screen.

A dotted line puts both demands on one person without picking a winner. The line that hands out daily work stays exactly where it is, and a second line is drawn toward whoever owns quality for the craft — with no authority over pay or ratings attached to it. On the chart the first line is solid and the second one is dotted, which is where the name comes from.

It works by writing down, in advance, what each of the two lines holds.

The solid line — the reporting line — holds four things.

1. It writes the review. Whoever puts the final rating on the half-year or annual form is on the solid line.
2. It proposes pay and promotion. The same person takes the case to human resources on the strength of that rating.
3. It approves vacation and expenses. It's the name on the approval screen.
4. It sets priority. Which screen Noa draws this week comes off the product team's schedule.

The dotted line holds three.

1. It sets standards. Color, spacing, rules for using shared components — the agreements that apply to everyone in the craft.
2. It reviews output. Before release it opens the screens and points out where they left the standard.
3. It contributes to the review. In prose, not in a score. Noa's dotted-line manager writes a few paragraphs on the judgment calls she made over six months, and the solid-line manager folds that into the form.

Three things decide whether it holds up, and each one has to be written down with a number or a name on it.

The first is time. Pagedeck reserves eight of Noa's forty weekly hours for craft work. Without a reserved block, dotted-line work slides to Friday evening every week, because the urgent requests always arrive from the solid side.

The second is veto scope. At Pagedeck the dotted line can block a screen that breaks the color and spacing rules, but how many steps a flow is split into belongs to the product team. Skip this boundary and the dotted-line manager assumes everything is blockable while the product team assumes everything is a suggestion.

The third is who breaks a tie. The usual answer is the nearest manager the two lines share, named in advance. Without a name, the person in the middle ends up carrying arguments back and forth, and that time appears on nobody's plan.

The most common home is the matrix organization, which cuts the company by product and by function at the same time. Everyone belongs to two places by construction, and one of the two is drawn as a dotted line.

The second is any function where one person covers the whole company. Legal, security, and data often look like this at 45 people: one specialist, maybe two. Put that person on any single team and the other teams lose access, so the solid line goes to one team and dotted lines go to the rest. These functions have one seat of headcount to begin with, so the problem gets solved by adding lines instead of people.

The third is time-boxed work. Putting two engineers on a four-month enterprise rollout doesn't require moving their reporting lines — a dotted line to the project owner does it, and the line is erased when the project ends. If the arrangement will be gone within six months, it is cheaper than a reorg.

Every added line is another person to keep track of, though, and counting span of control without the dotted ones understates the load. A manager with eight direct reports and five dotted lines has thirteen people to talk to; at a half-hour every two weeks, that alone is thirteen hours a month.

"Noa's solid line is the document editing team and mine to her is dotted. Ask them about her schedule first."

I can't assign this person work, so go through the manager who can.

"The dotted side sends me a paragraph and I'll attach it to the review."

The solid line writes the evaluation; the dotted line participates only in writing.

"We drew the dotted lines and never reserved any time against them. That's why nothing is happening."

The relationship exists on the chart but no capacity was taken out of anyone's plan, so it doesn't run.

At Pagedeck the phrase comes up most often in quarterly planning. When Grace says security review should cover every team next quarter, the immediate proposal is dotted lines from the one security specialist to all four teams. Mia's questions are always the same two: what percentage of that person's time each team gets, and whether that person can block a schedule the team has already committed to.

Start the quarter without answers and the reviews keep getting pushed, or the specialist appears the day before release and stops the launch. Neither failure comes from drawing the line wrong; both come from drawing it without conditions.

The most common mistake is reading a dotted line as half a boss. There's a line on the chart, so surely the person on the other end can direct some portion of the work — which is a fair reading of the picture. What the dotted line actually holds is standards, review, and an opinion, and none of those is an instruction. Once it gets read as half authority, the dotted-line manager starts touching schedules and the person in the middle is taking orders from two directions. A quarter of that and they start listening to whichever side pushes harder.

The second mistake is using dotted lines as a substitute for restructuring. Changing the structure costs time and goodwill, so adding one more line looks like the cheap move. It mostly defers the problem. If a single person has three or more dotted lines running to them, the shortage is in seats, not in lines, and leaving it alone puts that person last in every team's queue.