Our head of finance updates their Scorecard numbers cleanly but never brings an issue to the Level 10 Meeting, insisting everything is fine even when other departments face billing delays and slow reporting. How do you get hidden departmental issues onto the list without sparking a defensive standoff?

Question

Tyler Smith · Accepted Answer

In an EOS company, nobody owns an exclusive right to an issue. If finance will not post the bottleneck, the affected peer must post it. The head of sales or operations simply adds 'Client onboarding billing delays' to the Issues List before the Level 10 Meeting starts.

When you reach that item during IDS, the Integrator must frame the conversation around process and company health, never personal competence. You are not putting the finance leader on trial. You are examining a breakdown in the Accountability Chart where work transfers between seats.

The Integrator should open by asking the reporting leader to describe the operational symptom in one sentence. Then, turn to the finance leader and ask what variables inside their workflow are causing the delay. This removes the personal shield and redirects energy toward root cause analysis.

Make it culturally clear that bringing zero issues to the meeting is not a badge of honor. It is usually evidence of denial or fear. Healthy departments generate operational friction constantly because they are growing. When a leader consistently reports that everything is fine while peers absorb friction downstream, the Integrator must challenge that behavior during quarterly check-ins. If the leader cannot embrace open transparency, they do not match the core value of open and honest collaboration.