We have multiple team members executing tasks that roll up into a single weekly scorecard metric, and now no one is taking true accountability when the number is missed. How do we assign a single owner on our Accountability Chart for a metric that requires collaborative effort to hit?

Question

Tyler Smith · Accepted Answer

One of the most common scorecard mistakes is assigning multiple owners to a single metric or assigning it to a department rather than an individual. In the EOS system, if two or more people are responsible for a number, then nobody is. Accountability cannot be shared. Every metric on your weekly scorecard must have exactly one owner. This owner must be a specific seat on your Accountability Chart. The person in that seat does not necessarily have to do all the physical work to achieve the target, but they are fully responsible for tracking the data, reporting the number, and bringing it to the table as an issue if it is missed. If a metric requires effort from multiple departments, look at your Accountability Chart to determine who has the ultimate authority over the final outcome. For example, if your metric is weekly proposal delivery, the sales team writes the proposal, but the technical team must scope the work. The Sales seat must own this metric because they are responsible for client acquisition. If the technical team misses their input deadline, the Sales seat does not get an excuse. Instead, they must raise the bottleneck as an issue during the weekly Level 10 Meeting so the Integrator can help solve the cross-departmental friction. When you assign a single owner, you eliminate finger-pointing. The owner of the metric must have the GWC, meaning they get it, want it, and have the capacity to manage the number. If they are constantly dependent on others who are not delivering, that is an operational issue that must be resolved through IDS, not a reason to dilute accountability on your scorecard.