The Cross-Functional Meeting

When to bring gatekeepers together vs. when to work with them separately is a sequencing decision that most initiative teams get wrong. The default — bring everyone to one meeting to align all stakeholders simultaneously — creates a coalition-of-objectors dynamic. In a joint meeting where individual concerns have not been pre-addressed, each gatekeeper's concern validates the others'. IT raises a security issue. Legal raises a liability issue. HR raises a workforce issue. Finance raises an ROI issue. Each concern makes the others seem more credible. The group leaves the meeting aligned — on their concerns, not on the initiative. Individual alignment first. Joint meeting second.

1. Phase 1: Individual Engagement Work with each gatekeeper function separately to address their specific concerns, present their tailored brief, and reach a preliminary position — not approval, but an understanding of what approval would require. Document each function's outstanding concerns and the responses that address them.
2. Phase 2: Cross-Validation Before the joint meeting, share relevant gatekeeper inputs across functions where there is intersection. IT security requirements inform Legal's data governance analysis. Legal's regulatory mapping informs HR's training content requirements. Finance's ROI model incorporates IT and HR cost inputs. Surface the cross-function dependencies before they surface in the joint meeting as surprises.
3. Phase 3: Joint Confirmation Meeting The joint cross-functional meeting has one purpose: confirm the positions that were reached individually, identify any cross-function conflicts that need resolution, and establish the ongoing governance structure. It is not a first meeting. It is a confirmation meeting. This framing changes the dynamic from objection-raising to final-alignment.