You took out a layer of management.The work didn’t go with it.

The layer came out

Somewhere in the last three years, you took out a layer.

Maybe it was a reduction. Maybe it was a reorg with a better name on it. Maybe you just stopped backfilling and let the spans widen on their own.

Whatever it was called, the chart got flatter, and the reasoning was sound. Fewer handoffs. Faster decisions. Less telephone between the work and the person accountable for it. Most companies that did this would do it again.

Here’s the part that didn’t make it into the memo.

That layer wasn’t only moving information up and down. It was absorbing something. Deciding the dozen small things a week that weren’t worth escalating. Noticing that someone had gone quiet, about three weeks before it showed up in their work. Saying the thing that needed saying while it was still a small thing. Telling someone their work mattered, and being specific about why.

None of that was in the job description. It’s just what that layer did.

The layer came out. The work it was doing stayed.

Everyone inherited a piece of a job nobody trained them for

So it got distributed.

Now the senior engineer makes the call that used to get escalated. The designer runs the review. The PM has to tell a peer, directly, that the work isn’t landing. The tech lead is the one who notices someone is struggling.

A lot of that redistribution is genuinely good. People closer to the work making the decisions about the work is most of the reason delayering made sense in the first place. Decisions can be pushed down. Planning can be templated. Review can be a checklist.

One piece didn’t distribute cleanly.

The conversation part. The part where you sit across from another human being and say a true thing in a way they can actually hear — honest about the work and generous about the person, in the same breath.

That part is an art. A small fraction of people want to practice it, are naturally good at it, or have the life experience it takes. It doesn’t template, it doesn’t fit in a checklist, and there’s no version of it you can put in a document and hand off.

Everyone inherited the hardest part of the manager’s job. Nobody handed them the part of the training that was supposed to come with it.

And the relationships that used to carry it are gone too

Here’s what makes this harder than a training gap.

The model everyone still has in their head is a manager with six direct reports on a team that mostly works with itself. Stable membership. Same people, same room, for years.

That team is close to extinct.

What replaced it is countless small groups that form for a project, ship, and dissolve. Matrixed reporting. Cross-functional pods. Three overlapping working groups where you’re the most senior person in one, the newest person in another, and a peer in the third. Most of the people your work genuinely depends on do not report to you, and never will.

And the thing that used to make a hard conversation survivable was history. Three years of banked goodwill. You could say the direct thing to someone because you’d earned the right to, and they knew you well enough to hear it as care instead of as an attack.

That three-year relationship almost never happens anymore.

So the question isn’t only who gives the feedback now that the layer is gone. It’s how two people who met six weeks ago get to the point where either of them can.

What actually goes missing

Ask people what breaks and they’ll describe the friction. The thing nobody said. The pattern that hardened into a reputation. The handoff that’s been quietly broken for two quarters because raising it would be awkward and nobody owns the relationship enough to be the one.

That’s the visible half, and it’s expensive. It shows up eventually as a slipped launch, a regretted exit, or a performance case that surprises everyone but the four people who saw it coming.

The other half is quieter and probably costs more.

So the next time those two people need something from each other, they start from zero. Again.

Both halves are the same problem. Two people who have to work together have no reliable way to build the relationship that would let them.

The friction is the part everyone talks about. The relationships that never got built are the part that costs more.

Why “train your managers to coach” can’t fix this

For twenty-five years the answer to all of this has been the same. Make managers into coaches. Books, workshops, LMS modules, 1:1 templates, quarterly cycles, a competency framework with “develops others” in it.

I wrote one of those books. I spent ten years in rooms teaching it, and I’ve watched the methodology work — at Panasonic, and at a few hundred other companies before it.

The methodology isn’t the problem. The delivery model is, for two reasons.

It was always a single point of failure. One person, per person, expected to be reliably good at an art most people never wanted to practice. When your manager is one of the good ones, it’s the best thing that happens to you at work. When they’re not — and most of the time they’re not, through no fault of their own, because they were promoted for being excellent at something else entirely — you simply don’t get it. There’s no second copy. Nothing catches it.

And now the arithmetic doesn’t work. There are fewer managers than there were three years ago and the spans are wider. A manager who is genuinely, unusually good at this cannot do it for fourteen people and still do the job they were actually hired for. Ask them to and you’ll lose them, which is a bad trade in any org and a terrible one in a flat one.

Manager-as-coach didn’t become a bad idea. It became unavailable.

The skill is still the right skill. Routing it through one person, per person, is the part that stopped working.

Stop routing it through one person

If development can’t run through a single manager anymore, the answer isn’t to find better managers. It’s to stop making one person the only path.

That means everyone gets the tools directly. Not a course. Not a workshop they’ll forget by Tuesday. Something in the actual flow of the actual work, that knows the context, that shows up at the moment the conversation is live.

That’s what we built Ren to be. It works in Slack and Teams, where the work already is. It’s built on the Accountability Dial™ — the five-stage framework from Good Authority, the thing 100,000+ managers have already been trained on.

And it runs in every direction. Down to someone you manage. Up to your boss. Across to a peer you have no authority over and never will.

Most of what it coaches isn’t conflict.

It’s telling someone specifically why their work mattered, in a way that actually lands, instead of a thumbs-up react. It’s asking for what you need from someone before the work starts rather than after it’s gone sideways. It’s saying the small thing early, while it’s still small and while it’s still kind.

The Accountability Dial has five stages, and the first one is called Mention: say it once, lightly, early. Most situations never need to go past it. The stages exist so that the small conversation happens at the small stage, which is the only time it’s cheap for everyone involved.

And the same five stages work on the good stuff. You can Mention a win. You can Invite someone to look at what made it work. That’s not a workaround; it’s what the framework was built for.

One more thing worth saying plainly: Ren works on you, too. Whatever seat you’re in, you’re on the other side of somebody’s difficult conversation this week.

This isn’t anti-manager. It’s anti-bottleneck.

I want to be careful here, because this argument gets misread in a predictable way.

This is not an argument against managers. The good ones are among the most valuable people in any company, and that was true before the delayering and it’s more true now. If you have managers who are genuinely good at developing people, protect them. They’re rarer than they were and you have fewer of them.

It’s an argument against making them the only path.

And there’s something in it for them, too. A manager who isn’t the sole carrier of every person’s growth gets some of their first job back — the one they were hired for, the one they’re great at, the one that’s currently getting squeezed into the margins of a calendar full of check-ins.

The Accountability Dial was never a discipline ladder. It’s not a process for building a case against somebody. Most of it resolves in the first thirty seconds of the first stage, and a good share of it is praise. The goal at every stage is the same: get to a shared picture of what’s actually happening, and hand the other person ownership of what they do about it.

That was the goal when it was a book for managers. It’s the same goal now that it belongs to everybody.