Cross-Functional Alignment Is a Lie at Scale
Shared ambitions can stall when functional targets, capacity and rewards remain unchanged. Agreement needs to reach the decisions made after the meeting.
Working Across the Organisation · Alignment · Managing Sideways · Influence
This article is inspired by real workplace and leadership experiences. I do not use real names, company names or identifying details. Roles, teams, organisational structures, projects and business context may be removed, generalised or combined to protect the people and organisations involved while preserving the underlying leadership reflection. Where conversations are referenced, wording may be edited for clarity and anonymity.
I think a fair amount of what we call cross-functional alignment is agreement that has never been asked to compete with anyone's actual priorities. Senior leaders support a shared ambition. Everyone recognises the value of working together. Then the request reaches a team whose objectives, capacity and performance measures have not changed at all.
That is the version of alignment I distrust. The title is deliberately provocative, but I am not suggesting that every organisation above a certain size is incapable of collaboration. I am questioning how confidently we use the word when the agreement has changed so little about the decisions people will make afterwards.
It is easy to interpret the lack of movement as hypocrisy. People said the right things in the meeting, then returned to protecting their own departments. Sometimes that may be a fair assessment. I think we should also examine what those people are being asked to protect and what will happen to them if they do not.
If a manager is accountable for their team's delivery, measured against functional targets and given no additional capacity, deprioritising another team's request may be entirely consistent with the job we have set them. They can understand the wider ambition and still struggle to justify sacrificing a commitment for which they will be held personally responsible.
That does not make every refusal reasonable. Managers can be territorial, and a difficult trade-off is not permission to stop thinking about the organisation. But calling for a more collaborative mindset does very little if we leave the trade-off exactly where it was and decline to help resolve it.
At scale, those trade-offs can be difficult to see from the meeting where the agreement was made. A commitment crosses several teams, each with its own deadlines and obligations. By the time someone asks for actual work, the senior-level enthusiasm may be the only thing that travelled with the request.
I think this is where alignment can become a performance. We have evidence that people endorsed the direction, so we behave as though the practical choices have also been settled. The team trying to move the work forward then has to negotiate decisions that the original conversation appeared to have made already.
More meetings may make the frustration increasingly visible without changing its cause. A recurring update can establish that the same request remains unresolved. It cannot, by itself, decide which existing priority should move, whose capacity should be used or who has the authority to accept the consequence.
I would want those questions closer to the agreement itself. If something matters across functions, what are we prepared to change inside those functions to make it possible? An honest answer might be that we support the idea but cannot resource it yet. I would find that more useful than wholehearted endorsement followed by several months of politely discovering the same constraint.
Shared accountability also needs to reach the way contribution is recognised. If helping another team makes my own numbers worse and nobody takes that contribution into account, the organisation is sending competing messages. I can choose to absorb that cost occasionally, but I don't think a dependable way of working should require people to repeatedly disregard the incentives we designed for them.
Equally, a shared goal cannot mean nobody owns the decision. Some conflicts will remain even after priorities are discussed. Someone needs to be able to resolve them, explain the choice and accept that one team may now deliver less of something it was previously expected to do. That is a leadership responsibility, not a failure of enthusiasm further down the organisation.
The part I want to pay more attention to is what happens after people agree. I want to know which commitment changed, what capacity became available and how the people doing the work understand the decision. Those answers would tell me much more than another confirmation that everybody supports the vision.
I could be persuaded to be less cynical about the word alignment. I would start with a situation where a cross-functional priority caused a real, acknowledged change in a functional plan, and the people making that change were supported rather than penalised for it. That would give me something concrete to believe in after the meeting ended.
