How it worksSupportPricingFAQ
Resources
BlogBest Practices
About
Talk to usLogin
← Back to the blog

How do you get other departments to actually work on a cross-functional program?

November 18, 2026 · 5 min read

In cross-functional programs, almost everyone hopes: the program lead that the others will contribute, the others that it won't be much work, and the department head that the two people she pulled won't matter much. All of these hopes coming true at once is impossible. So people contribute when clear numbers keep the room for hoping small.

All of these hopes coming true at once is impossible.

Why does nobody show up after a few months?

Most program leads will know the picture: at the kick-off every department committed people, a few months later nobody comes to the weekly anymore, and there is always something more urgent. What I have seen fairly often in these cases is that there was never a real commitment. The topic had been raised at some point, everyone was polite, but nobody saw it as their own job.

That often makes it a communication problem. Because nothing was pinned down, everyone understands what they wanted to understand, and that is usually the version with the least work for themselves (a close relative of false clarity, where after long discussions everyone believes everything has been settled).

There is no ill will in that, though, and it is rarely a lack of interest in the project. In large companies people always have a lot on their plate, other, more important topics keep coming up, and the first things to be forgotten are the ones that matter to someone else. The polite commitment from the kick-off is exactly that kind of thing.

What is left is basically hope, on every side: you hope the others will contribute properly, the colleague from the business unit hopes the project won't be too much work for him, and his boss hopes that two people pulled out won't make much of a difference. All of these hopes coming true at once is impossible.

What helps when you have no authority over them?

If everyone understands the most convenient version and all of them are just hoping, the room for hoping has to become as small as possible, and the best way to do that is with clear targets. If you tell someone "we need ten leads a week from you starting in September" and then actually follow up on it, there is little room for interpretation: either the ten leads are there or they aren't. Following up matters just as much as the number itself, otherwise at some point it ends up back among the things that matter to someone else.

With Bayescase, program management software (for innovation, transformation or cost programs, for example), the business case turns into targets like these after approval, and the actual figures show early where a committed number isn't coming in.

Do you need a mandate from the board for this?

The usual advice is that this is a structural problem and that you should get a mandate from the top, ideally with a budget of your own for the team. For someone who is supposed to spend 50 % of their time on a program, that is certainly the right way. For most requests, though, it is overkill, because you usually don't get a mandate for small things, and you don't want to spend the time and political capital on it either.

The short route works fine, you just have to pin down clearly what is expected. The clear number turns the polite commitment into a question with a yes or a no as the answer. The person can still say no, and only then do you go and get the mandate, if the task is important.

Even after a yes, though, people still have a lot on their plate, and what matters to others is the first thing to be forgotten. You have only made it once people see the number they have to deliver as their own problem. It helps to involve them in the project: tell them they are part of the project team, invite them to the kick-off and so on, so that the project's success is also their success and they can use it for themselves.

Is a department allowed to pull its people back?

Yes, always. If a business unit suddenly has problems of its own, it also has the right to pull people, and that is how it has to be in a company. What matters is that everyone involved is clear about what it means, which is why the cost side belongs on the table: with two fewer people we deliver this much less, and that means this much for the NPV (how to put a number on a cut like that is something I described for the cost-cutting round). Then a different decision can be made at a higher management level if needed.

If, on the other hand, all you say is "then our project will be delayed", nobody can do anything concrete with that, and everyone hopes it won't be too bad. Precise numbers prevent that, because then nobody is hoping in the wrong direction anymore.

Frequently asked questions

How do I get other departments to work on a cross-functional program?
With a clear number per department that you follow up on consistently, for example "ten leads a week starting in September". A polite commitment at the kick-off leaves everyone room to understand the most convenient version, while a number is either reached or not. It also helps to explicitly bring people into the project team, so the success is theirs too.
Why do business units stop contributing after the kick-off?
Usually not out of ill will or lack of interest. Often there was never a real commitment, only a polite one, and in large companies more important topics keep coming up. What matters to someone else is then the first thing to be forgotten.
As a program lead without authority, do I need a mandate from the board?
For big requests, such as someone putting half their time into the program, yes. For most smaller contributions a mandate is overkill and costs political capital. First pin down clearly what you expect, and get the mandate if the answer is no and the task is important.
What do I do when a department pulls its people out of the program?
Accept that a department with problems of its own has the right to do so, and show the price in numbers: how much less the program delivers and what that means for the NPV. Nobody can do anything with "then our project will be delayed", but with a concrete number management can decide differently if needed.
Alex Gutzler

Written by

Alex Gutzler

Founder & CEO, Bayescase

What will your strategy deliver?

In a short conversation we take one of your initiatives and show how an idea becomes a business case with targets and tracking.

Talk to usarrow_forward