Why cross-functional work falls apart
Cross-functional work fails for boring reasons. Not because people don't collaborate, or because the strategy was wrong, or because the technology didn't work. It fails because nobody set it up properly.
Most organisations treat cross-functional initiatives like regular projects with more people in the room. They aren't. I've watched the same failure mode play out in every sector I've worked in: nobody owns it, nobody has time for it, and nobody agreed how decisions get made. The work drifts, people get frustrated, and six months later someone asks "whatever happened to that initiative?"
The fixes aren't complicated. They're just unglamorous.
Name an owner
One person accountable for the outcome. Not a committee, not a shared inbox, not "the team." The owner doesn't do everything. They make sure everything gets done: decisions are made, blockers are cleared, progress is visible. If nobody owns it, it drifts. Every time.
Agree the deal in the first session
Who's in, what each person is responsible for, how decisions get made, and what "done" looks like. Write it down. This sounds obvious, but most cross-functional teams skip it because it feels bureaucratic. Then three months in, nobody can remember who was supposed to do what, and everyone assumes someone else is handling the hard bit.
Agree resource, not just attendance
This is the single biggest killer. People get assigned to cross-functional work on top of their day job with no conversation about what they're stepping back from. They show up to meetings but can't do the work between them. Get explicit: hours per week, what gives, and what happens when there's a conflict. If a line manager can't commit the time, you need to know that before you start, not after the initiative has stalled.
Set the cadence from day one
Put standing time in the diary before things get urgent. Working sessions where actual work progresses and blockers get cleared. Lighter steering check-ins focused on decisions needed. Match the rhythm to the pace of the work. The point is simple: if you wait until something is urgent to get people together, you've already lost weeks.
Keep one action list
One list, one place, reviewed every session. Every action has a description, an owner (one person, not a team), and a due date. No side lists, no actions buried in emails. If it's not on the list, it doesn't exist.
None of this is revolutionary. That's rather the point. Cross-functional work doesn't need better frameworks or more sophisticated collaboration tools. It needs someone to do the setup work that everyone wants to skip. The structural boring bits are what make the interesting work possible.