Most companies don't have a cross-departmental leadership problem. They have a promotion problem dressed up as a leadership problem.
Here's my position, and it's not a popular one in the L&D world: you cannot train alignment into people who were promoted for the wrong reasons in the first place. If someone was made a team lead because they hit their numbers, and nobody ever checked whether they could think past their own function, no workshop fixes that. You're not building a shared leadership language. You're patching over a selection failure with a curriculum.
So when a client asks me "how do we get our rising managers to stop fighting each other across departments," I don't start with training design. I start by asking who chose these people, and why. Nine times out of ten, the answer reveals the actual problem: leadership potential was never assessed. Only output was.
This article is my actual view — not a neutral survey of best practice — on what training and alignment across departments really requires, why most programmes fail at it, and what I do differently with the leaders I work with directly.
The Real Reason Emerging Leaders Work Against Each Other, Not With Each Other
Silos aren't a communication failure. They're an incentive failure that gets rebranded as a communication failure because that's easier to fix with a workshop than a comp structure.
When a marketing lead and an operations lead are both promoted, trained, and measured entirely within their own function, you have built two people who are structurally rewarded for defending their patch. Put them in a room and call it "cross-functional leadership training" and you'll get polite nodding and zero behaviour change, because nothing about how they're evaluated has moved.
I've sat in enough of these rooms to recognise the tell: everyone agrees in the workshop, then reverts within a fortnight. That's not a learning-retention problem. That's the system telling them the workshop wasn't real.
There's a particular pattern I see over and over in mid-size organisations: the leadership team commissions a training programme after a visible, embarrassing failure — a launch that stalled because sales and product weren't reading from the same page, a re-org that generated three months of turf war. The training gets commissioned to fix the symptom. Nobody goes back and asks why the incentive structure made that turf war rational behaviour for the people involved. Until that question gets asked, and answered honestly, every subsequent programme is treating the same wound with a different bandage.
I'd go further. I think most organisations quietly prefer the training-as-bandage approach, because it doesn't require anyone senior to admit that the way they measure and reward people is actively working against the alignment they say they want. That's an uncomfortable admission for a leadership team to make about itself, and training budgets are a much more comfortable place to put the effort than a compensation review.
Where Identification Actually Goes Wrong
Most organisations identify "emerging leaders" by asking department heads to nominate their best people. This sounds sensible and is, in my experience, one of the most reliable ways to promote the wrong cohort.
A department head nominates the person who makes their own life easier — the strong deputy, the reliable operator, the one who never causes friction. None of that predicts whether someone can hold two departments' competing priorities in their head at once and make a call that isn't purely self-serving. I've watched organisations run entire leadership pipelines built on this nomination process and then wonder, eighteen months later, why their emerging leaders still think like individual contributors with bigger titles.
What I actually look for isn't performance. It's whether someone, unprompted, describes a problem from more than one department's vantage point. That's rare, and it's teachable — but only if you're looking for it before you put someone through training, not after.
I also pay close attention to how someone talks about a colleague from another department when that colleague isn't in the room. Do they describe the other department's constraints with any accuracy, or only their own frustration with it? Most people, including talented operators, default to the second. The ones worth investing development budget in can usually explain, reasonably fairly, why the other department is doing what it's doing — even when they disagree with it. That's a habit of mind, not a skill you install in a two-day course, and it's far more predictive of cross-departmental success than any competency matrix I've seen an HR team produce.
Stuart's Lens for Evaluating Emerging Leaders (Not the Standard One)
- Vantage-point test: Can they describe a live problem from another department's point of view, unprompted, without being asked to? If not, they're leading their function, not the organisation.
- Cost of saying no: Have they ever pushed back on their own department's ask because it damaged a peer team? If it's never happened, you haven't seen their real ceiling yet.
- Silence under ambiguity: Watch what they do when there's no playbook and no one above them to defer to. Most default to control. The ones worth developing default to inquiry.
- Peer pull, not manager push: Do people from OTHER departments seek them out for judgement, or only their own team? Cross-functional trust can't be trained in eight weeks if it doesn't already exist in some form.
- Language discipline: Do they translate their function's jargon for outsiders, or expect everyone else to learn it? This single habit predicts alignment more than any competency framework I've used.
Why the 'Shared Framework' Everyone Builds Doesn't Actually Align Anyone
Most organisations respond to misalignment by writing a leadership framework — a document defining values, behaviours, decision rights. I've reviewed dozens of these documents. They are almost always accurate, well-intentioned, and completely inert.
A framework only aligns behaviour if it changes what gets rewarded and what gets challenged. If the framework says "collaborative decision-making" but the operations director still gets promoted for hitting departmental targets regardless of the friction he causes elsewhere, the document is decoration. Emerging leaders read incentives, not laminated posters. They will copy what gets rewarded and quietly ignore what gets written down.
The frameworks that actually change behaviour are the ones tied to something that costs a leader something if they ignore it — a peer review process with teeth, a promotion gate that includes cross-functional testimony, a coaching relationship that surfaces the gap between stated values and actual decisions. Absent that, you have produced a well-worded piece of paper.
I've also noticed that the organisations most proud of their leadership framework are often the ones where it's been least tested. A framework that's never had to override a popular decision, or block a promotion for someone who missed the collaborative bar, hasn't actually been used yet — it's been published. The real test of whether a framework means anything is whether it has ever cost someone a promotion, a bonus, or a project they wanted. If it hasn't, in an organisation of any size, that's not evidence the culture is already aligned. It's evidence the document has never been asked to do its job.
Structured Training: What Actually Transfers and What's Theatre
I'll say something unfashionable here: most leadership training for emerging leaders is built for the trainer's convenience, not the leader's development. It's modular, it's scenario-based in the abstract, and it hands people frameworks they'll forget within a month because nothing in their actual job forced them to use it.
What transfers is training that's anchored to a live decision the leader is currently facing — not a hypothetical case study about a fictional company. When I work with emerging leaders, I ask them to bring an actual unresolved cross-departmental tension into the room. We don't role-play. We work the real problem, in real time, with real stakes. That's uncomfortable, and it's also the only version of this that sticks, because the leader has skin in the outcome.
Ambiguity training is the other piece nobody does properly. Most programmes teach decision-making models — frameworks, matrices, decision trees — as if the problem is a lack of process. It rarely is. The problem is that emerging leaders haven't yet built the tolerance to sit with an unresolved, contested decision without either forcing a premature answer or escalating it upward to avoid owning it. That's a nervous-system skill as much as a cognitive one, and it's the thing coaching builds that a workshop cannot.
What I Actually Structure Into Cross-Departmental Development
- Real live case, not hypothetical — Every session works an actual unresolved tension between departments that a participant is currently navigating — never a generic scenario.
- Named accountability, not shared credit — Cross-functional initiatives fail when nobody owns the outcome. I insist on one named owner per initiative, even when the work is genuinely joint.
- Coaching alongside, not after — Training installs the concept. Coaching is where the behaviour either survives contact with the leader's actual team or quietly dies. Running them separately, sequentially, is why most of this doesn't stick.
- Language audit before content — Before teaching anything new, I make leaders translate their own department's core terms into plain English a stranger could understand. Most can't, on the first attempt. That gap is the real starting point.
Coaching Is Where Alignment Either Sticks or Quietly Dies
Training gives people a concept. Coaching is what happens when that concept meets the leader's actual team, actual politics, and actual Tuesday-morning meeting where someone from another department is blocking their project for reasons that feel, to them, completely unreasonable.
I don't coach people towards a generic "leadership style." I coach them towards recognising the specific moment they default back into departmental thinking — because that moment is always the same for a given person, and once they can see it coming, they can choose differently. That's a personal, individual pattern. No framework document captures it, and no group workshop surfaces it reliably, because people don't expose their actual blind spots in front of six peers from other departments.
The leaders who genuinely become more aligned across departments are the ones who get uncomfortable, individual feedback on a repeated pattern — not the ones who complete the most modules.
The Distinction I'd Actually Put My Name To
If you take one thing from this article, take this: alignment across departments is not a communication outcome. It's a selection and incentive outcome that training can support but never substitute for.
Most leadership development spend in this space goes toward the wrong end of the problem. Organisations build beautiful frameworks and thoughtful workshops for people who were never assessed for cross-functional judgement in the first place, and then wonder why the training "didn't take." It didn't take because the person wasn't wrong for the training — the training was wrong for what actually needed fixing upstream, at the point of identification and incentive design.
My real position, stated plainly: fix who you're developing and what you're rewarding before you fix how you're training them. Get the identification right — genuine cross-functional judgement, not departmental output — and get the incentives pointing the same direction as the framework you've written. Do that, and the training becomes the multiplier it was always meant to be, instead of the thing you blame when the real problem was never touched.
That's the distinction most consultancies won't make, because it implicates the promotion committee, not just the training budget. I make it anyway, because it's the only version of this that actually changes how departments work together — not just how they talk about working together.