Picture a manager five years into the role. Her team likes her. The individual contributors on other teams like her. Most of the directors in the building like her. Ask her to name the hardest relationship in her job, though, and she won't point up or down. She'll point sideways, at the other managers she's supposed to be able to lean on.
That's an odd thing to admit out loud, so most managers don't. They'll talk for an hour about a difficult direct report. They'll mention managing up if you ask directly. The relationship with the manager two desks over, the one whose team's missed deadline becomes their problem, the one who seems to be quietly competing for the same promotion, almost never comes up. Not because it's minor. Because nothing in a typical leadership program is built to name it.
Manager training almost always points in the wrong direction
Most leadership development assumes the relationship that needs work is between a manager and their team. It teaches feedback, delegation, running a one-on-one that doesn't feel like an interrogation. All of that matters. None of it touches the manager's relationship with the other managers around them, the people they need to coordinate with daily and were never given a reason to trust.
A workshop can teach someone how to have a hard conversation with a direct report. It rarely gives two managers at the same level a working relationship before the org chart forces one on them under deadline pressure. By the time that pressure hits, whatever goodwill existed has to be built from a standing start, in the middle of a fire.
Most organizations will keep training managers to handle their teams better and keep wondering why cross-team friction never quite goes away. The teams were never the problem.
Peer tension between managers usually gets misdiagnosed as a personality problem
When two managers clash, HR often files it under personality conflict and moves on. Sometimes that's accurate. More often it's a symptom of something structural: two people with overlapping goals, competing resources, and zero shared process for resolving either one, left to figure it out through Slack messages and passive-aggressive meeting comments.
Treating it as a personality issue means the org waits for it to blow up before doing anything. Treating it as a structural gap means building the relationship before the pressure arrives, which is a different project entirely and a much cheaper one.
The cost shows up somewhere else, which is why it gets ignored
A missed handoff between two teams rarely gets logged as "manager peer conflict." It gets logged as a delayed project, a frustrated customer, a good employee who quietly starts job hunting because their manager seems constantly at war with a neighboring team. The root cause stays invisible because nobody's tracking it at the source.
That's the trap. The symptom lands in a dozen different places on the org chart, and the actual cause, two managers who never had a working relationship to begin with, never gets addressed because it never shows up as a single, obvious line item.
How Groveland builds peer support into the program instead of hoping it happens
Groveland's cohorts run thirteen weeks, one hour a week, with managers grouped into peer clusters of three or four from the very first session. That's a deliberate structural choice, not a seating chart. The peer group works through real situations pulled from each manager's actual team, not hypothetical case studies, guided by an expert facilitator through a cycle of learn, apply, reflect, and refine.
By week thirteen, those three or four managers have already had the hard conversations with each other that most peer groups avoid indefinitely. They've watched each other handle a real accountability conversation, a real scheduling conflict, a real moment of disagreement, inside a structure built to make that safe. That relationship doesn't dissolve when the program ends.
It's part of what Groveland calls the Leadership Habit Dividend: the return an organization keeps collecting long after the formal sessions stop, because the habits, and the relationships built while forming them, don't expire on a calendar. For a stretched HR team, that's the difference between hoping managers figure out how to work with each other and building it into the program on purpose.
Frequently Asked Questions
Most leadership training focuses entirely on the manager-to-team relationship and leaves the manager-to-manager relationship to chance. Add competing priorities and shared resources with no process for resolving conflict, and friction is the default outcome, not the exception.
It usually looks personal on the surface and functions structurally underneath. Two managers with overlapping goals and no shared process for coordinating will clash regardless of how well they'd otherwise get along.
Managers are placed into peer groups of three or four from week one of a thirteen-week cohort, working through real situations from their own teams together under expert facilitation rather than meeting each other for the first time under pressure.
It can be built, which is a more accurate way to describe it. Given a structured, low-stakes setting to work through real situations together repeatedly, managers develop trust in each other the same way they'd develop any other habit, through repetition.
It's the ongoing return an organization gets after a Groveland cohort ends: managers who kept the habits, and the peer relationships built while practicing them, instead of the effect fading once the formal sessions stop.