Run the Business or Build the Business: What Belongs on a Role Scorecard, And What Doesn't
Senior leader scorecards work when they capture the durable, run-the-business work of the role. They stop working when they become a dumping ground for everything else.
I was in a session with a CEO recently, reviewing a draft Role Scorecard his Head of Product had just sent over. The leader had clearly put real effort into it. Eight pages, lots of detail, careful thought about the next year. We started reading through it together.
Halfway down, the CEO looked up. "Where is the actual product work? The roadmap. Quality. Customer satisfaction. None of this is on here."
He was right. The scorecard had a long list of items. Lead the AI integration project. Stand up the new design system. Restructure the product team for the European launch. Build out the analytics platform. They were all important. They were all things the CEO wanted done. They were also all projects with finish lines.
The actual run-the-business work, the durable accountabilities of being Head of Product, was nowhere to be found.
This is The Catch-All. It is what happens when a Role Scorecard, which should be a clean agreement about how a leader runs their function, becomes the default location for everything important the leader is expected to do. Strategic priorities, change initiatives, special assignments, and transformation projects. They all end up on the scorecard because there is nowhere else obvious to put them. And the document stops working as an executive performance management tool.
What a Role Scorecard Is For
A Role Scorecard is the agreement between a CEO and a senior leader about what success in the role looks like. It captures what the leader is accountable for, how that accountability is measured, and how decisions get made within their scope of authority. It is one of the most important documents in a company, and one of the most commonly misused.
If you have not seen a well-built Role Scorecard before, the eight sections are Role Mission, Key Responsibilities, Behavioral Expectations, Decision-Making Rights, Other Expectations, Direct Reports, Key Relationships, and Resources. Together they answer a simple question. What does it mean for this leader to do their job well, week in and week out, across the year, when nothing exceptional is happening, and nothing is on fire?
That last clause matters. The scorecard is built for the steady state. It describes how the function operates when the business model is intact, the strategy is set, and the team is doing the work it was hired to do. It is not built for transformation. It is not built for a crisis. It is not built for the special project the board wants done by Q3. Those are different kinds of work, and they need different kinds of documents.
When the scorecard does its job, it produces three things. Clarity about what the leader owns. A shared baseline for assessing performance. And a stable reference point that holds across reviews, across quarters, and across the noise of any given week. That stability is what makes executive performance management actually work at the leadership team level.
The moment the scorecard starts mixing run-the-business accountabilities with project work, strategic change, and special assignments, that stability disappears. The document becomes a rolling list of whatever happens to be on the leader's plate this quarter. And the conversation the scorecard was supposed to enable stops happening.
What Run-the-Business Work Looks Like
Run-the-business work has a specific signature. It is durable. It is continuous. It defines the role, not the moment.
Think about it this way. If you took a senior leader on your team and erased every special initiative, every strategic priority, every transformation project from their plate, what would be left? The thing that is left is run-the-business work. It is what the leader would still be doing five years from now if the business model did not change.
For a VP of Sales, that is pipeline management. Sales team performance. Deal velocity. Forecast accuracy. The cadence of one-on-ones with reps. The rhythm of pipeline reviews and sales operations meetings. Hiring. Coaching. Holding the team accountable to the sales process. None of that ends. It just keeps happening, week after week, quarter after quarter, year after year, with the leader making it work.
For a COO, it is operational throughput. Quality metrics. Supplier relationships. Cost control. The performance of the operations team. The production rhythm. The systems and processes that move the business through the work it has been built to do.
For a Head of Product, it is the roadmap. Product quality. Customer satisfaction with the product. The performance of the product team. The cadence of product reviews. The relationship between product, engineering, and go-to-market.
These accountabilities have a cadence. Daily, weekly, monthly, quarterly. They run on a steady rhythm, and they hold across years. They are not "complete" next quarter. There is no finish line. The leader does the work, and then they do it again, and the function runs.
This is what a Role Scorecard is built to capture. The durable, ongoing, role-defining work. When you read a scorecard a year from now, the same items should still be on it, assuming the business model has not changed. If most of the items have rolled off, then what you wrote down was not the role. It was a project list dressed up as a scorecard.
What Strategic Change Looks Like
Strategic change work is the opposite of run-the-business work in almost every dimension that matters.
It has a beginning, middle, and end. It is bounded by start and finish dates. It runs on a cadence shaped by the work itself, not by the steady rhythm of the business. And when it is done, it is done. The leader moves on to the next thing.
There are three categories where this work belongs.
Strategic goals or quarterly priorities. These are the major initiatives that align with your strategic plan. Whatever system you use, OKRs, Rocks, quarterly priorities, 3HAGs, the format is less important than the discipline. They are time-bound, tied to the strategy, and live in a document built for them. When you set quarterly priorities, you are saying, "Here are the most important things we need to make happen in the next 90 days that go beyond running the business." That document has its own cadence and its own review rhythm.
Special initiatives or ongoing initiatives. These are named change efforts currently in flight. They might run for a quarter, or two quarters, or a year. They have an owner, a milestone plan, and a finish line. "Stand up the new sales channel." "Migrate to the new ERP." "Establish the AI-native delivery model." All of these are initiatives. They belong on an initiative tracker, not on a Role Scorecard.
Special assignments and one-off projects. These are smaller asks. Board commitments. Owner agendas. Ad hoc pushes. The CEO asks the COO to lead the response to a specific customer issue. The board wants the CFO to put together a particular analysis. These show up, they get done, they go away. They are real work, but they do not define the role. They live in whatever owner-and-team task system you use.
A quick distinction worth making explicitly. An ongoing initiative is not the same as an ongoing accountability. An initiative is in flight. It has a finish line, even if that finish line is six quarters away. Accountability is durable. It does not finish. The same word "ongoing" is doing two different jobs there, and the difference matters.
The same senior leader has both kinds of work. Run-the-business accountabilities and strategic change work. That is healthy and correct. The question is which document each belongs in.
How Role Scorecards Become Catch-Alls
This drift happens to good CEOs running good companies. It is rarely a decision. It is a default.
The pattern looks like this. The strategic plan calls for a new initiative. Someone needs to own it. The senior leader closest to the work is the natural choice. The CEO writes it into their scorecard because the scorecard is the document where accountability lives, and it feels right to put it there. Then the next quarter, a special priority comes up. Same thing. Then a change effort gets launched. Same thing. Over time, the scorecard accumulates everything important the leader is doing, because there is no other document doing the job.
The CEO is not mistaken about what the leader should be doing. They are making a mistake about which document the work belongs in. The work itself is right. The home is wrong.
A few things accelerate the drift.
There is no other obvious home. If the company does not have a clean strategic priorities document, or an initiative tracker, or a special-assignments process, then the scorecard becomes the default by elimination. CEOs do not deliberately choose to overload it. They run out of other places to put things.
Items get added but rarely removed. When a new strategic priority shows up, it goes on the scorecard. When the priority finishes, the line item often stays, sometimes for quarters, because no one has a process for cleaning up. The scorecard keeps growing.
Compensation triggers tend to find their way onto scorecards, too, and that creates a different set of problems. We will cover that in a separate post. For now, just note that the same drift dynamic applies. The bonus structure goes on the scorecard because there is nowhere else to put it, and the scorecard takes on yet another job it was not built for.
The result is the same regardless of which kind of work has crept in. The scorecard becomes a catch-all. The original executive accountabilities, the things that actually define how the leader runs their function, get harder to see. And the document that was supposed to be a stable agreement starts shifting every quarter.
Why Executive Performance Management Breaks Down
When run-the-business work and strategic change work mix on the same document, three things break.
The leader cannot tell what they are being measured on. The scorecard reads as a list of things the leader is doing this quarter, but the items have completely different shelf lives. Some are enduring responsibilities that they will do forever. Some projects will be completed in eight weeks. Some are one-off pushes that will not exist next quarter. The leader has to figure out, on their own, which is which. Most do not bother. They just try to get through the list.
Performance reviews stop being useful. A review is supposed to assess whether the leader is doing the role well. But if the document keeps changing, there is no stable baseline to assess against. Was the leader operating their function well this year? Hard to say. Half the items on the January scorecard are not on the December scorecard. The conversation drifts toward "what did you get done" rather than "are you running this function the way we agreed you would run it."
Drift goes unnoticed. Because the scorecard is a moving target, the CEO and the leader cannot easily see when a durable accountability has slipped. The pipeline numbers softened over the year. The product team's output dropped. The supplier quality issues piled up. Those signs are buried under the project work that has been crowded onto the document. By the time the CEO notices, the slip has been happening for two or three quarters.
This is the cost of The Catch-All. The scorecard ceases to be a tool for executive performance management and becomes a status update. Senior leaders cannot use it to anchor their work. CEOs cannot use it to assess their team. And the leadership team's accountability, which the scorecard was supposed to enable, starts eroding.
The Run-the-Business Test for Your Scorecards
Use these five questions to audit each Role Scorecard on your senior team. The questions test whether the items on the document belong there, not whether the items themselves are good or bad.
Does this scorecard describe how the leader runs their function, or how they will change it? This is the frame-level test. Read the document end-to-end and ask what kind of work it captures. If most of the items are about transformation, restructuring, building, launching, or migrating, the document is a project plan, not a Role Scorecard. The two have different jobs and need different homes.
Does any responsibility have a foreseeable completion date? Ongoing accountabilities do not finish. If you can imagine writing "complete" next to an item in 12 or 24 months, that item is a project. It belongs on an initiative tracker, not on the scorecard. The simple question to ask is "What does this leader do once this is done?" If the answer is "moves on to the next thing," it was a project all along.
Has any strategic initiative been written as a responsibility? This is the recognition test. "Build the new sales channel" is a strategic initiative. "Manage the sales pipeline" is a responsibility. They look similar in a document, but they are different kinds of work. Run each item on the scorecard against this distinction. If it has a finish line, no matter how far out, it does not belong here.
Would the same items be on this scorecard a year from now if the business model did not change? This is the durability test. Ongoing accountabilities should be stable across years. If most of the items would be different a year from now, you are managing a project portfolio, not a role. Stability is what makes the scorecard work as a baseline for performance assessment.
Could you cut the scorecard in half by removing transient items? This is the drift test. Scorecards accumulate special priorities, change initiatives, and one-time pushes over time. If half the document is transient, it has lost its function as a stable agreement. The fix is not to reset the scorecard from scratch. It is to extract the transient items and put them in their proper documents.
If you read your scorecards through these five questions and feel uncomfortable about what you find, that discomfort is the diagnosis. The fix is not complicated. It is the work of putting executive accountability back into the document built to hold it.
Where to Start: Sorting What Is on Your Scorecards Today
Pick one Role Scorecard. Probably the one you have the most concern about. Open it. Read each item one at a time, and apply the run-the-business test.
If the item describes how the leader runs their function, leave it on the scorecard. These are the durable accountabilities that define the role. Most well-built scorecards have between five and eight of these in the Key Responsibilities section, plus the related elements in Other Expectations.
If the item is a strategic priority that ladders up to the strategic plan, move it to your strategic priorities document, your OKR system, your Rocks, or whatever you use to track quarterly strategic work. The work does not go away. The home changes.
If the item is a named change initiative in flight, move it to your initiative tracker. If you do not have one, create one. It does not need to be elaborate. A simple list of named initiatives, owners, milestones, and target completion dates is enough to start.
If the item is a one-off assignment, move it to wherever your owner-and-team task tracking lives. Special assignments need to be visible somewhere, but that somewhere is not a Role Scorecard.
After you have sorted the items, look at what remains. The remaining list should describe how this leader runs their function, week in and week out, across the year. If it does, the scorecard is doing its job again.
Then put a cadence in place to keep it that way. A quarterly check on every scorecard, looking for transient items that have crept in and durable items that may have slipped. Ninety days is roughly the right interval. The Role Scorecard is built for the steady state, but keeping it that way requires a small amount of ongoing maintenance.
Summing It Up
A Role Scorecard works when it does one job well. It captures the durable, run-the-business accountabilities of a senior leader, and it leaves the rest to the documents built for the rest. Strategic priorities live in the strategic plan. Initiatives live on the initiative tracker. Special assignments live in the task system. The scorecard holds the line on what it means for this leader to run their function.
When the scorecard becomes The Catch-All, it stops doing that job. It becomes a status update. The CEOs who treat the scorecard as a clean instrument get usable executive performance management. The ones who let it become a catch-all get a confused document and a confused leader. The choice is entirely upstream of the scorecard itself.
Questions for You and Your Team
Pick one Role Scorecard from your senior leadership team. If you erased every project, every strategic priority, and every special initiative from it, what would be left? That residual list is the run-the-business work. The shorter and clearer it is, the better your scorecard is doing its job. The longer or vaguer it is, the more The Catch-All has set in.
Where do strategic initiatives, change efforts, and special assignments actually live in your company today? If the honest answer is "on the role scorecards," that is the source of the drift. Naming the proper home for each kind of work is the first move toward fixing it.
When you read your senior leaders' scorecards a year from now, will the same items still be on them, assuming the business model has not changed? Durability is what makes a scorecard function as a performance management tool. If most of the items will roll off, the document is tracking the project portfolio, not the role.
The goal isn't to have perfect answers. It's to surface whether The Catch-All might be affecting your team.
Take the Next Step
Wondering whether your leadership team has the structure, clarity, and accountability to scale your business? Take the Leadership Team Assessment to see where your team is strong and where it needs work.
Take the Leadership Team Assessment
Ready to go deeper? Book a call to talk through what Role Scorecards would look like for your leadership team.
The Exit Planning Book for Founder-CEOs
Why do 75% of founders regret their exit within a year—even when they hit their number? Because most exit planning ignores what actually matters: personal readiness, life after the transaction, and building a business that sells on your terms.
SPRINGBOARD: A Founder's Guide to Selling Your Company With Purpose, Clarity, and a Vision for What's Next provides a comprehensive framework for planning exits that serve your life goals, not just your financial targets. It covers the four phases most founders miss: preparing yourself, preparing your business, executing the transaction, and navigating what comes next.
The first three chapters are available now.
About the Author
Bruce Eckfeldt is a strategic business coach and exit planning advisor who helps founder-CEOs of growth-stage companies scale systematically and exit successfully. A former Inc. 500 CEO who built and sold his own company, he brings real-world operational experience to strategic planning and leadership development. He's a certified ScalingUp and 3HAG/Metronomics coach, Certified Exit Planning Advisor (CEPA), an Inc. Magazine contributor, and host of the "From Angel to Exit" podcast. Bruce works with growth companies in complex industries, guiding leadership teams through growth challenges and exit preparation. Reach him at bruce@eckfeldt.com with any questions or if you want more information or to book a call with him.
