The Role Scorecard Is an Agreement, Not a Checklist
A Role Scorecard with a missing section is an agreement with a missing clause. Both fail in predictable ways, and both fail in places you won't see until the performance conversation goes wrong.
The CEO had Role Scorecards for every member of his leadership team. He pulled them up on his laptop to show me. Eight sections each. Filled in. Reviewed at the start of the year. By the book.
He was still having the same performance problems he had before he built them.
His VP of Operations was escalating decisions she should have been making on her own. His CRO was hitting his revenue number but losing two of his best account executives to competitors. His Head of Product was working hard on the wrong things and didn't seem to know it. The scorecards existed. The conversations were not getting easier.
I asked if I could read through them. Twenty minutes in, the pattern was clear. Each scorecard was missing one or two sections, or had a section filled in so vaguely it might as well have been blank. The CRO's scorecard had no Behavioral Expectations that would have surfaced the retention problem. The VP of Operations had no Decision-Making Rights, which is why she kept asking. The Head of Product had a Role Mission that could have applied to any product leader at any company.
This is The Incomplete Agreement. The scorecard exists. It looks complete from a distance. But a section is missing, or thin, or generic. And the gap shows up later as the exact performance problem the scorecard was supposed to prevent.
A Role Scorecard is not a checklist of eight items to fill in. It is an agreement between a CEO and a senior leader about what success looks like, how it will be measured, what authority the leader has, and what behavior is expected along the way. Like any agreement, it works as a system. Skip a clause and the rest of it weakens.
A Role Scorecard Is an Agreement, Not a Checklist
The most useful way to think about a Role Scorecard is to stop thinking about it as a document. It is an operating agreement between two people. The CEO is one party. The senior leader is the other. The scorecard captures what they have agreed to, in writing, before the performance period starts.
Every agreement has parts that have to be present for it to work. A Role Scorecard has eight, and each one corresponds to something an operating agreement needs.
The Role Mission is the purpose of the agreement. Why does this position exist, and what must it ultimately produce? Without it, both parties are working from their own private picture of what the role is for.
The Key Responsibilities are the obligations. The five outcomes the leader has committed to deliver, each with measurable thresholds at three performance levels. Without them, performance becomes a matter of opinion.
The Behavioral Expectations are the terms of engagement. How the leader has agreed to operate. Observable behaviors, not personality traits. Without them, the "how" of the work becomes a source of friction that no one can name clearly.
The Decision-Making Rights are the authority granted under the agreement. What the leader can decide independently and what requires approval. Without this, the leader either escalates everything or oversteps without knowing it.
The Direct Reports and Key Relationships sections name the parties affected by the agreement. The team being led and the cross-functional dependencies that make the role workable. Without them, the structure around the role stays implicit and the dependencies get neglected.
The Resources section names the assets available to perform the agreement. Budget, systems, data, external support. Without it, the leader is held accountable for outcomes they may not actually have the means to drive.
The Other Expectations section captures the special terms. Travel, meeting cadence, external representation. The role-specific requirements that don't fit anywhere else but would create problems if left unstated.
Eight sections. Eight parts of one agreement. Skip one, and you don't have a partial agreement. You have an unworkable one. The other seven sections cannot compensate for what is missing.
This is the shift. A scorecard built as a checklist gets filled in section by section, with each section treated as independent. A scorecard built as an agreement gets stress-tested as a whole, with each section asked to do its specific job in the system.
The Three Load-Bearing Sections
Not every section carries equal weight. Three of them do most of the work, and weakness in any one of them tends to undermine the whole agreement. Mission, Key Responsibilities, and Decision-Making Rights are the load-bearing sections.
Role Mission tells the leader what game they are playing. A strong mission is one to three sentences that make clear why this position exists and what it must produce. It survives a year without becoming outdated. It is specific to your company, not transferable to any other company in your industry.
When Mission is weak, the leader optimizes for the wrong things. They work hard on activities that feel productive but are not connected to what the role is actually for. The CEO sees effort but doesn't see the impact they expected. Neither party can name what is wrong, because the underlying disagreement is about purpose and no one ever made purpose explicit.
Key Responsibilities define how the agreement is measured. Exactly five. Each one with a clear metric and three performance thresholds: Red, Green, and Wow. Red is performance that requires intervention. Green is meeting expectations. Wow is exceptional. The discipline of five forces the CEO to decide what actually matters most, instead of listing everything the role touches.
When Key Responsibilities are vague, performance evaluation becomes subjective. Both parties walk into the review with different stories about how the year went. The conversation turns into a negotiation about what the standard should have been, instead of an honest look at whether it was met. This is the failure mode Post 1 named as The Assumed Standard, and it is the most common reason scorecards exist on paper but don't drive performance in practice.
Decision-Making Rights tell the leader what they can do without asking. Independent authority for some decisions. Required approval for others. Specific thresholds where they apply: budget over a certain amount, hiring above a certain level, pricing changes outside a defined range, vendor commitments above a stated threshold.
When Decision-Making Rights are missing, one of two things happens. The leader escalates everything, slowing the organization down and signaling to the CEO that the leader is not actually operating at the senior level the role requires. Or the leader makes calls they shouldn't have made, and the CEO finds out after the fact, which damages trust on both sides. Neither pattern is the leader's fault. Both are the consequence of authority being assumed instead of agreed.
These three sections do not work in isolation. Mission gives the leader purpose. Key Responsibilities make purpose measurable. Decision-Making Rights make the role executable. If any one of them is missing or weak, the other two cannot do their jobs cleanly, and the remaining five sections cannot patch the gap.
The Sections Most Often Missing
Across the leadership teams I review, two sections are most often missing entirely. Decision-Making Rights and Key Relationships.
Decision-Making Rights gets skipped because most CEOs assume authority is implicit. The leader is a VP. They should know what they can decide. The CEO knows what they would want approved. The leader has a sense of what they should bring forward. Both parties operate from those private assumptions, and the assumptions don't align.
The cost shows up as friction. Decisions that should take a day take a week because the leader is checking in. Decisions that should have been escalated land in the CEO's lap as surprises after the fact. The CEO starts to think the leader doesn't have good judgment. The leader starts to think the CEO is impossible to read. Neither narrative is accurate. The actual problem is that the agreement never specified who decides what.
Writing this section is uncomfortable for some CEOs because it forces them to give up control they didn't realize they were holding onto. That discomfort is the signal that the section is needed. If defining authority feels like loosening a grip, the grip was the problem.
Key Relationships gets skipped for a different reason. Relational work is treated as soft and uncountable, so it doesn't feel like something to put in a performance document. CEOs assume their senior leaders will figure out who to work with and how to work with them.
The cost shows up as silos. The CRO and the Head of Product never align on go-to-market for new releases because no one made that relationship a defined responsibility. The COO and the CFO have parallel conversations about resource allocation that never quite connect. The Head of Customer Success doesn't manage the analyst relationships that affect renewals because no one named that as part of the role. Each gap is small. The accumulated cost is not.
Key Relationships works when it names the relationships that, if neglected, would directly impair the leader's ability to achieve their Mission. Not every interaction. The dependencies that matter. Internal: the peers, direct reports, and leadership relationships that have to function for the role to work. External: the clients, partners, vendors, or analysts that have material impact on outcomes. Naming these relationships explicitly turns them from optional collaboration into accountable work.
The Sections Most Often Misused
Two other sections are usually present but written badly. Behavioral Expectations and Other Expectations.
Behavioral Expectations almost always gets copy-pasted from a job description. The result is a list that describes capabilities, not behaviors. "Strong strategic thinker." "Excellent communicator." "Highly collaborative." These are hiring criteria. They describe the kind of person you would want in the role. They do not describe what you would actually see that person doing day to day, which is what the section is supposed to define.
The fix is to ask one question for each item: if this person were doing this well, what would I see them doing in a typical week? "Demonstrates data-driven decision making while balancing intuition and market feedback" is a behavior. You can observe it. You can give feedback on it. "Has strong analytical skills" is a hiring criterion. You can interview for it. You cannot evaluate it in real time.
This matters because Behavioral Expectations is the section that handles the "how" problems that Key Responsibilities can't capture. A CRO who hits the revenue number but burns out their team is failing on a behavioral dimension that the responsibilities metric doesn't measure. Without observable behaviors written down, the CEO is left raising the issue using language that feels personal because no one has agreed to the standard in advance.
Other Expectations is the section most likely to become a junk drawer. Anything that didn't fit cleanly elsewhere ends up here. The result is a section that is technically present but not really doing anything.
The test is simple: would there be a real problem if this person didn't do this thing, and is this thing actually unique to this role? If both answers are yes, it belongs in Other Expectations. If either is no, it doesn't. Travel requirements for a regional sales VP belong here. "Attends all-hands meetings" does not, because that applies to everyone. "Represents the company at three industry conferences per year" belongs here. "Has good attendance" does not.
Other Expectations works when it captures three to five role-specific items that would create real friction if left unstated. Most scorecards have one or two of those. The rest is filler that should be cut.
Diagnostic: How To Audit Your Current Scorecards
Pull up the scorecards you currently have for your leadership team. Not the templates. The actual filled-in documents. Then run them through these four questions.
Can you tell, from the Role Mission alone, what game this leader is playing in your specific business right now? If the mission would also fit a leader in the same role at three other companies in your industry, it is too generic. The Mission is supposed to be specific to your company, your strategy, and this period of your growth. A generic Mission produces a leader who is optimizing for generic outcomes, which is not the same as your outcomes.
Can you point to a metric in current reporting that maps to each of the five Key Responsibilities? Not "we could pull that data if we needed to." Actually point to where it lives, who pulls it, and how often. If the answer is "we'd have to set that up," the Key Responsibility is unmeasurable in practice, which means it is not really a performance metric. It is a hope.
Can you name a significant decision this leader made in the last 90 days without asking you? Then check whether that type of decision is covered in the Decision-Making Rights section. If it is, the section is doing its job. If it isn't, the leader is operating in the gray zone and getting away with it, which works until it doesn't.
Are the Behavioral Expectations things you would actually observe in a typical week, or things you would test for in an interview? Read each one and ask: "What would I see this person doing if they were doing this well?" If the answer is "they would be a good strategic thinker," it is a hiring criterion. Rewrite it as a behavior.
Each question maps to one of the failure modes from the previous sections. The point of the audit is not to grade the document. It is to predict where the next performance conversation is going to go sideways, and to fix the agreement before it does.
Where To Start: Build In This Order
If you are building Role Scorecards from scratch or rebuilding the ones you have, the order matters. The sections depend on each other, and building out of order produces a document that looks complete but doesn't hold together.
Start with Role Mission. Until you can articulate why the role exists in one to three specific sentences, nothing else has anything to anchor to. Spend more time on this than feels reasonable. Most first drafts are too generic. The test is whether someone outside your company could read the Mission and understand why this role matters to your business specifically.
Build Key Responsibilities second. Five outcomes, each with Red, Green, and Wow thresholds. This is where most of the work lives, and most of the iteration. First drafts are almost always too vague. Post 3 in this series is dedicated to this section because it is the most nuanced part of the scorecard.
Add Decision-Making Rights third. Once the role's purpose and outcomes are clear, you can decide what authority the leader needs to deliver them. Authority should match accountability. If the leader is accountable for revenue, they need real authority on pricing, deal structure, and team composition. If the authority and the accountability don't line up, the agreement is broken at a structural level.
Add Behavioral Expectations fourth. With the what and the authority defined, you can specify the how. Three to five observable behaviors. Each one rewritten until it describes something you would actually see, not something you would test for.
Add the context sections last. Direct Reports, Key Relationships, Resources, and Other Expectations. These provide the structure around the role. They matter, but they are easier to write once the load-bearing sections are clear.
The same logic applies if you are auditing existing scorecards. Fix Mission and Key Responsibilities first. Then Decision-Making Rights. Then Behavioral Expectations. Then the rest. Working in this order prevents the trap of polishing the easy sections while leaving the load-bearing ones weak.
One last point. The scorecard system cascades. The senior leader's Key Responsibilities should ladder down into the responsibilities of the people who report to them, and so on through the organization. The work starts at the leadership team because that is where the highest-stakes ambiguity lives, and because the agreements at that level set the pattern for every level below. Get the leadership team's scorecards right and you have a foundation to build on. Try to push scorecards down through the organization without fixing the leadership layer first and you build on sand.
Summing It Up
The pattern of which sections are missing or weak in your scorecards tells you something about your organization, not just your documents. CEOs who skip Decision-Making Rights are often the same CEOs who hold authority too tightly. CEOs who write Behavioral Expectations as hiring criteria are often the same CEOs who manage by chemistry rather than by clear feedback. CEOs whose scorecards have generic Missions are often running companies where strategy is implicit and assumed.
The Incomplete Agreement is rarely about laziness or lack of effort. It is about which conversations the CEO has been avoiding, and which clarity the CEO has not yet been willing to commit to in writing. Fixing the document is the easy part. The harder work is having the conversations that the missing sections were avoiding.
The next post in this series goes deep on the section that breaks most often: Key Responsibilities, and the Red, Green, and Wow framework that makes them measurable. If you only have time to fix one section in your current scorecards, that is where the highest leverage lives.
Questions for You and Your Team
Before moving on, take a few minutes to reflect on these questions. The goal isn't to have perfect answers. It's to surface whether The Incomplete Agreement might be affecting how your leadership team performs and how clearly you can hold them accountable.
Pull up the scorecard for one of your senior leaders. Which of the eight sections is the weakest, and what is that weakness costing you right now? The weakest section is usually the one connected to the performance issue you've been working around. The connection is rarely visible until you go looking for it.
When was the last time you wrote down the actual decisions one of your senior leaders is allowed to make without asking? If the answer is "never" or "I haven't thought about it that specifically," the Decision-Making Rights section in their scorecard is probably doing nothing useful.
Read your own Behavioral Expectations for one role out loud. Are they things you'd see this person doing in a typical week, or things you'd interview a candidate for? If they sound like a job posting, they are doing the job of a job posting, not the job of a performance management tool.
Take the Next Step
If this post surfaced gaps in how your leadership team's roles are defined, the Leadership Team Assessment is a good starting point. It evaluates the health of your leadership structure, including how clearly expectations, roles, decision rights, and accountability are defined across your team.
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.
