We have cross-functional project teams that do not fit neatly under a single seat on our Accountability Chart, but they need the discipline of a weekly pulse. How do we structure departmental Level 10 Meetings for cross-functional teams without muddying accountability?

Question

Tyler Smith · Accepted Answer

Cross-functional teams often struggle with the weekly pulse because they do not have a single head on the Accountability Chart to drive the meeting. To run successful departmental Level 10 Meetings™ for these groups, you must first establish clear operational boundaries.

Do not allow the absence of a single department head to create a leadership vacuum. Every Level 10 Meeting™ requires one designated leader to own the pulse. For a cross-functional project team, you must assign one person to the seat of the meeting leader, regardless of their standard functional role. This individual is responsible for keeping the team on schedule, starting and ending on time, and enforcing the structure of the agenda.

Next, ensure the team's Scorecard and Issues List are tightly focused only on the scope of that specific cross-functional initiative. Do not let general departmental noise bleed into this specialized meeting. If an issue arises that falls outside the charter of the project, it must be immediately tabled and escalated to the appropriate functional department's Level 10 Meeting™ or the leadership team's list.

By maintaining a strict separation of issues, you prevent the meeting from turning into an endless status update. The goal of this cross-functional pulse is to IDS® problems that block the project's milestones, not to negotiate daily department tasks. Keep the focus narrow, assign clear accountability for the meeting flow, and hold every member to the ninety percent To-Do completion rate.