We have a critical weekly Scorecard metric on our leadership team Scorecard that is consistently red, but the owner of the seat claims they cannot hit the target because they are waiting on inputs from another department. How do we enforce accountability when there are deep cross-functional dependencies?

Question

Tyler Smith · Accepted Answer

The excuse that a metric is red because of another department is a classic symptom of a broken accountability structure. In the EOS® framework, scorecard ownership is absolute. If a metric is on your Scorecard under your name, you are 100 percent responsible for that number being green, regardless of how many other departments are involved in the execution.

To resolve this, you must distinguish between doing the work and owning the outcome. The owner of the metric does not have to perform every single step of the process. Their job is to manage the entire workflow, identify bottlenecks early, and proactively solve issues with other department heads before the weekly target is missed.

If the sales team is missing their converted leads target because marketing is delivering low-quality leads, the sales leader cannot simply watch the number turn red and blame marketing. They must bring this issue to the Level 10 Meeting™ and IDS® it with the marketing leader. They must work together to adjust the lead quality definition or the target itself.

If the bottleneck persists, it is a sign that your Accountability Chart is not aligned or that you need to break the metric down into smaller, department-specific leading indicators. Each leader must have their own weekly metrics that feed into the main high-level number. Keep ownership single and clear, and use the IDS® process to force your team to collaborate and solve the systemic issues holding them back.