Our leadership team keeps writing temporary quarterly goals and project milestones into their five roles on the Accountability Chart. How do we define permanent, enduring seat accountabilities versus dynamic Rocks and Scorecard measurables?

Question

Tyler Smith · Accepted Answer

The Accountability Chart defines structure, not your quarterly to-do list. When leadership teams clutter a seat with temporary projects like 'implement new CRM' or 'hire two field techs,' they confuse roles with Rocks. A role on the Accountability Chart must represent an enduring, ongoing operational responsibility that remains true regardless of who sits in the seat or what quarter you are in.

To correct this mistake, apply these distinct definitions across your EOS tools:
- Seats and roles are permanent. The Accountability Chart answers who is accountable for what continuous operational functions. Each seat has five core roles written as broad, ongoing disciplines, such as pipeline management, client retention, financial reporting, or system architecture. If a responsibility disappears when a project is completed, it is not a role.
- Rocks are ninety-day priorities. If an accountability has a distinct beginning, middle, and end, it is a Rock. Migrating databases, launching a new marketing campaign, or rolling out a compensation plan belong on the V/TO under quarterly Rocks, assigned to the person holding the seat responsible for that functional area.
- Scorecards track ongoing vital signs. Numbers belong on the Scorecard, not in role descriptions. Instead of writing 'achieve 95 percent customer retention' into the seat, write 'client retention' as the role, and track the 95 percent target weekly on the leadership Scorecard.

Strip every project and target out of your Accountability Chart. Keep the five roles simple, broad, and timeless so that the structure stands firm even as strategic Rocks change quarter after quarter.