strategy and transformation delivery
Why cross-functional projects get stuck between teams
The work loses momentum when the outcome matters to everyone but the whole route belongs to nobody.
The outcome is fragmented
Each function completes its contribution while customer, commercial or operating success depends on how the pieces work together. This matters because cross-functional project management decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Name one end-to-end outcome and one accountable senior owner. Record the choice, the evidence still required and the person who will return with it. Keep the mechanism proportionate: the purpose is better judgement and follow-through, not additional ceremony.
Dependencies remain conversational
Teams discuss what they need from one another but do not make sequence, due dates and consequences visible. This matters because cross-functional project management decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Track the few dependencies capable of stopping or reshaping the whole route. Record the choice, the evidence still required and the person who will return with it. Bring specialist judgement into the decision where required while retaining business ownership of the outcome.
Decision rights are ambiguous
Questions circulate through meetings because nobody knows who can accept a trade-off across cost, pace, risk and quality. This matters because cross-functional project management decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Define the decision-maker and the minimum evidence before the issue appears. Record the choice, the evidence still required and the person who will return with it. Keep the mechanism proportionate: the purpose is better judgement and follow-through, not additional ceremony.
Status replaces problem-solving
Reporting describes activity and traffic-light colour while the underlying constraint remains unnamed or politically difficult. This matters because cross-functional project management decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Require each escalation to state the decision, options, recommendation and consequence of delay. Record the choice, the evidence still required and the person who will return with it. Bring specialist judgement into the decision where required while retaining business ownership of the outcome.
Functional incentives pull apart
A locally sensible target can create delay or cost elsewhere, especially when no shared measure represents the final outcome. This matters because cross-functional project management decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Use a small set of cross-functional success measures alongside functional accountability. Record the choice, the evidence still required and the person who will return with it. Keep the mechanism proportionate: the purpose is better judgement and follow-through, not additional ceremony.
Nobody stays with the gaps
Handoffs, assumptions, follow-ups and unresolved details accumulate between formal roles until an executive personally intervenes. This matters because cross-functional project management decisions rarely fail through a lack of possible technology. They fail when the business problem, operating context and responsibility for the outcome remain implicit. Bring evidence from the people doing the work, the systems supporting it and the leaders accountable for the result. Test assumptions about time, behaviour, data quality and implementation effort before treating them as facts. Assign integrative capacity with authority to connect the route and close loops. Record the choice, the evidence still required and the person who will return with it. Bring specialist judgement into the decision where required while retaining business ownership of the outcome.
What to carry into the work
- Name one end-to-end outcome and one accountable senior owner.
- Track the few dependencies capable of stopping or reshaping the whole route.
- Define the decision-maker and the minimum evidence before the issue appears.
- Require each escalation to state the decision, options, recommendation and consequence of delay.