The Role Scorecard Lifecycle: From Before the Hire to Promotion Out of the Role
The role scorecard isn't a document to file. It's an operating instrument that runs from before the hire through promotion out of the role.
I sat down with a CEO last year who was frustrated with one of his senior leaders. The leader wasn't performing. Things weren't getting done. The CEO had been carrying it for months and was at the point of considering a change.
Then I sat down with the senior leader. They walked me through their numbers. They were hitting their targets. They were proud of their work. They felt like they were doing exactly what they had been hired to do.
Both people were right. Both people were wrong. They were measuring different things.
This is what I call Set-and-Forget Scorecards. The pattern is straightforward. A leader thinks about the scorecard as a one-time deliverable rather than an ongoing operating tool. They build it once and stop engaging with it. It shows up in two versions. In the simpler version, no scorecard ever gets built in the first place. In the worse version, a scorecard exists, but it's bloated, unclear, and out of date. It hasn't been touched in months and no longer reflects what the leader actually does. The artifact exists. The system doesn't.
In either version, two things go missing. There are no clearly defined expectations that both sides have agreed to. And there's no real, honest commitment from both sides to those expectations. Without those, performance issues fester. There's no shared standard to ground the conversation in.
The role scorecard is supposed to be the operating instrument that establishes both. It isn't.
This post is about how to actually run a scorecard. The lifecycle, from using the scorecard to define the role through promotion out of it.
What Set-and-Forget Looks Like in Practice
Each version of Set-and-Forget shows up differently in practice. Both are common forms of broken leadership team performance management at the senior level.
The first version is more common than CEOs want to admit. There's no scorecard at all. The senior leader was hired against a job description written quickly when the role opened. The CEO had a sense of what they wanted but never wrote it down with specifics. Six months in, the leader is delivering on the things they think they were hired to do. The CEO is growing impatient with results that aren't materializing on outcomes the leader didn't realize were the priority. Maybe it's a new market entry the CEO mentioned during the interview that the leader assumed was a long-term aspiration. Maybe it's the cross-functional integration the CEO talked about as critical that the leader read as nice-to-have. The miss isn't the leader's effort. It's the misalignment that should have been resolved before the leader started.
The second version is worse in some ways. The scorecard exists, but it's bloated and clearly out of date. There are too many metrics. The thresholds were never updated when the strategy shifted. The priorities listed don't match the priorities the CEO is actually pushing on a day-to-day basis. Both sides agreed to the document at the time, but it got filed. The leader hasn't looked at it since onboarding because it no longer reflects what they actually do. The CEO can't recall the specific metrics without opening the document. The weekly one-on-one is "What are you working on this week?" rather than "How are you doing against your numbers?" The quarterly review either doesn't happen or is based on a different set of expectations than those on the scorecard.
Both versions produce the same outcome. The CEO's frustration grows. The leader feels unfairly judged. Trust erodes between them. And the conversation that needs to happen gets delayed because nobody has a shared frame of reference to start it.
Why It Costs You Your Best Leaders
The root cause is treating the scorecard as a document rather than as a system.
A document gets built, signed, and filed. A system gets run. The work of building the scorecard is significant. It takes hours of careful consideration of outcomes, metrics, decision-making rights, and behavioral expectations. When that work is done, it feels like the project is complete. It isn't. The work of building the scorecard is the smaller half. The work of running it is what produces results.
The cost shows up in three places.
First, performance issues fester. A leader who's missing the mark needs to know quickly, in specific terms, with reference to a shared standard. Without an active scorecard, the manager waits for things to get bad enough to bring it up, then brings it up in vague terms, then the leader pushes back, then nothing changes. The clarity you needed at week three is now a confrontation at month six.
Second, your A-players disengage. High performers want to know how they're doing and what's next. A scorecard that doesn't get reviewed leaves them uncertain. They start asking themselves questions you'd rather they not be asking. They start looking around. By the time they tell you they have another offer, you've already lost them.
Third, the scorecard turns into evidence. When CEOs finally pull the scorecard back out, it's often because they've decided they need to start a paper trail on someone they want to manage out. The scorecard becomes a legal artifact, not a development tool. Both sides feel it. Trust collapses. The instrument meant to drive performance becomes the weapon that ends the relationship.
The Lifecycle of a Working Scorecard
The fix is to treat the role scorecard as the foundation of leadership team performance management, not as a document you file. It has a lifecycle. It runs from defining the role to the moment the leader graduates from it. Six stages.
Stage 1: Use the role scorecard to build the role.
The role scorecard is a practical tool for defining what the role actually is. The scope. The expected outcomes. The responsibilities. The behavioral expectations. The decision-making rights. You write the scorecard first, and the job description gets generated from it. Not the other way around.
This usually happens inside leadership team strategy work, not as an isolated exercise. When I'm helping a CEO build out their senior team, there are usually several scorecards on the table at once. Adding a new role often means reviewing the existing scorecards and deciding what to carve off. If you've got a Head of Business Development who currently owns sales and you're bringing in a marketing leader, you have to decide whether the new role is sales plus marketing or just marketing, and what that means for the existing scorecard. The work of writing a clean scorecard for the new role often surfaces the cleanup work needed on adjacent ones.
You can't recruit for a role you can't define. The scorecard is how you define it.
Stage 2: Implement through a round-trip conversation, not a handoff.
The scorecard is a tool for conversation, not a document to hand over. There are two cases.
For a new hire, the scorecard already exists when you start interviewing. You use it during the interview process as the expectation-setting tool. The candidate walks you through the scorecard and tells you where they're confident they can deliver and where they're not. The goal isn't a candidate who claims they'll be 100% green on day one. That's either a role that isn't challenging enough for them or a candidate who isn't being honest with themselves. The goal is a candidate who's confident enough in enough of the scorecard that you'd hire them, with clear identification of where they'll need coaching, development, or support. That conversation might also surface that you need to supplement the role, or pull certain items off the scorecard for this person, and figure out where those items live instead.
What you get out of this is commitment. The candidate has agreed to the scorecard. Once they're in the role, you can hold them accountable to what they agreed to. Without that conversation, you've hired against vague expectations, and you'll have a difficult performance conversation in 30, 60, or 90 days when reality doesn't match the assumptions.
For an existing role you're formalizing, the move is the parallel draft approach. Both sides write their version of the scorecard simultaneously. You write yours. The leader writes theirs. Then you compare. If one person drafts first and hands it over, the other side can only respond. The conversation gets anchored in the first draft, and the differences in priorities, measurements, and assumptions stay hidden. The parallel draft surfaces them. Where the two scorecards diverge is where the work of the conversation actually is. By writing it together, both sides commit to the version that emerges.
Stage 3: Run it weekly.
The scorecard is the basis of every performance conversation. Weekly. That's the cadence. It's the agenda for the one-on-one.
The high-performance behavior here matters. A high performer arrives at the weekly meeting with the scorecard already marked up. They've done the self-evaluation before walking in the door. They've identified where they're succeeding. They've named where they have issues or questions. They've thought about how they want to address those issues. They know what support and resources they need from you to do it.
That inverts the meeting's cognitive load. Without it, you're driving the agenda, asking questions, pulling information out of the leader, and trying to figure out whether things are on track. With it, the leader is driving the agenda, and you're coaching. You're asking sharper questions. You're allocating support. You're catching the issues that the leader didn't catch themselves. The meeting produces decisions instead of just status updates.
If your senior leader can't show up with their scorecard marked up, that's the first piece of feedback. Either they don't know how, in which case you teach them, or they're not engaging with the scorecard at all, in which case you have a different conversation.
Stage 4: Update the scorecard as part of the 90-day review.
The 90-day review is a broader sit-down with the leader. You go through what's been working, what's not, where the goals and priorities have shifted, where they need to grow, and what performance goals to set for the next 90 days. Updating the scorecard is a core piece of that conversation. The scorecard isn't reviewed in isolation. It gets updated as the broader review surfaces what's changed.
The cadence isn't tied to anything else by default, but it's clean to align it with your quarterly planning rhythm if you have one. Sometimes the review surfaces no changes to the scorecard. That's fine. The discipline is in the act of looking, not in the act of changing. If you go too long, the scorecard drifts from reality, and the next review becomes a complete rewrite, which is a much heavier conversation than a tune-up. If you go too frequently, there's nothing meaningful to change, and the meeting becomes performative.
The full agenda of a 90-day review is broader than the scorecard update alone. The piece that matters here is ensuring the scorecard update happens as part of it every quarter, without fail.
Stage 5: Cascade with line of sight.
The senior leader's scorecard is the input for their direct reports' scorecards. The leader builds out their team using the same approach. Use the scorecard to define each role, run a round-trip conversation, run a weekly cadence, and update as part of the 90-day review. The line-of-sight requirement is that every direct report's outcomes should ladder up to one or more outcomes on the leader's scorecard. If you can't draw the line, the cascade is broken, and the team's work is going to drift away from what the senior leader is actually accountable for.
The same lifecycle applies at every level. The line-of-sight requirement is what holds the layers together.
Stage 6: Promote out of it.
When a leader is consistently green on the majority of the scorecard for at least three months, that's the signal to start building the next role scorecard. Not the entire scorecard. The majority. If you wait until they're 100% green on every metric, you're already too late. They need to be working on the next role before they've fully maxed out the current one. The next scorecard gets built, and the leader starts being evaluated against it for a transition period of up to three months.
The upper bound matters as much as the lower. I don't want to wait more than 6 months from the start of consistent green for the majority of items. A-players want a challenge. They want to grow. They want to take on new roles and responsibilities. If you've got a high performer in a role they've outgrown and you're not feeding them the next thing, they'll find it somewhere else. That timing is more often the cause of A-player turnover than compensation or culture issues.
The scorecard isn't just a performance evaluation tool. It's a development trajectory tool that culminates in either promotion or graduation from the role. When a leader gets promoted out, you don't lose the scorecard. You hand it to whoever takes the role next, who will use it during interviews to evaluate themselves against. The lifecycle starts again.
Diagnostic: Are Your Scorecards Set-and-Forget?
Two underlying questions sit beneath every scorecard system that works. First, were the expectations clearly defined in the role scorecard? Second, was there a real, honest commitment from both sides to those expectations? If either is missing, no amount of cadence or process will save you.
Five questions to test for both. Pick one senior leader and walk through these for that person specifically.
Did the scorecard exist before the person did? Look at the actual artifact. Check the version history if you can. If the scorecard was written after the person was hired, you're managing them against expectations they didn't sign up for. If you couldn't have used the scorecard to interview a different candidate for the same role, it's not actually defining the role. It's describing the person.
When the scorecard was implemented, did both sides write a draft, or did one side hand it down? If you had handed it down, the conversation that should have surfaced priority and measurement differences never happened. The commitment that comes from writing it together is also missing. Those gaps stay hidden until the first time you and the leader disagree about whether something is on track. By then, it's a confrontation, not a conversation.
Does the leader come to the weekly meeting with their scorecard marked up? If you're the one carrying the scorecard into the meeting, or it's not in the meeting at all, the operating cadence isn't there. The leader should arrive with self-evaluation done, issues identified, and questions framed. If they're not, that's either a teaching moment or a signal that they're not engaging with the document.
Has the scorecard been updated as part of a 90-day review? Pull up the file. Check the date of the most recent edit. If the answer is "I'm not sure" or "longer than 90 days," the review cadence has fallen off, and your scorecard is starting to drift from reality. The longer you wait, the bigger the eventual rewrite.
For your top performer, are you already building the next role scorecard? If you have a leader who's consistently green on the majority of their scorecard for three months and you can't point to active work on their next role, you're sliding toward losing them. The signal to act is the green run, not their notice email.
If you got "no" or "I don't know" on three or more of these, your scorecards are likely operating as filed documents rather than running instruments. Pick the most painful one and use the next section as the starting point.
Where to Start This Week
Three actions sized to fit in a single week. Don't try to fix the system across all your senior leaders at once. Pick one leader and run the lifecycle on them. The pattern repeats from there.
First, pick the senior leader you're most frustrated with. If there's no scorecard, build one before your next one-on-one. The scorecard doesn't have to be perfect. It has to exist and it has to capture what you actually want them delivering. If a scorecard exists but it's been filed, run the parallel draft exercise this week. Both of you write your version of the scorecard separately. Compare them in the next one-on-one. Where they diverge is the conversation.
Second, block your next two weekly one-on-ones with the scorecard as the agenda. Tell the leader before the meeting to come with the scorecard marked up. Self-evaluation. Issues identified. Asks framed. The first time will be awkward. They'll show up with a partial markup or no markup at all. Coach them through it. By the second meeting, they should arrive with the full markup. If they're not arriving with it after two weeks, the issue is engagement, not skill.
Third, calendar the next 90-day review now. A different meeting from the weekly. Put it on both calendars with a clear title that names what it is. "90-day review for [name]" or similar. If you don't put it on the calendar in the next 24 hours, it won't happen. The biggest enemy of the scorecard lifecycle isn't disagreement or resistance. It's the absence of a forcing function on the calendar.
Once you've run all three of those actions for one leader, you'll know whether the scorecard system is working in your business. If the leader engages, the conversations sharpen, and you can see the performance discussion change inside two or three weeks, the system works, and you can scale it across the senior team. If the leader resists, the conversations stay vague, and nothing changes, the issue isn't the scorecard. It's somewhere else, and the scorecard has just helped you see that.
Questions for You and Your Team
These questions are worth sitting with on your own before raising them with your senior team. They surface where the pattern is operating right now, on which leader, and at what cost.
Pick the senior leader you're most frustrated with right now. Is there a current scorecard you both reference, or are you each operating from a different definition of success? The frustration is rarely about the person. It's almost always about the missing shared agreement.
Of your A-players who have been performing well for the past quarter, who's at risk of leaving because you haven't given them the next challenge? If they're consistently green on the majority of their current scorecard and you haven't started building their next role scorecard, you're closer to losing them than you think.
In your last weekly meeting with each direct report, who carried the cognitive load of the conversation? If you were the one driving the agenda and asking the questions, the scorecard isn't doing its job. The leader should arrive with it marked up.
The goal isn't to have perfect answers. It's to surface whether Set-and-Forget Scorecards might be affecting your leadership team's performance.
Take the Next Step
If your senior leadership team isn't delivering the way you need them to, the issue is rarely the people. It's usually the system you're using to manage them. The Leadership Team Assessment is a structured way to evaluate whether your current team has the right roles, scorecards, and operating cadence to execute your strategy.
Take the Leadership Team Assessment:
https://www.eckfeldt.com/team-readiness-assessment
Or book a call to talk through what you're seeing on your team: https://www.eckfeldt.com/bookacall
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.
