Role Scorecards: The Performance Management Tool That Replaces Job Descriptions
Job descriptions tell you who to hire. Role Scorecards tell you what success looks like once they are in the seat.
Most founder-CEOs I work with describe the same scene. A senior leader is six or twelve months into a role. Performance is off. Nobody is quite sure what off means, exactly. The CEO is frustrated. The leader feels blindsided when the conversation finally happens. The job description is buried in a folder somewhere from the hiring process, written in qualifications language, and nobody has looked at it since the offer letter went out. The reviewer and the reviewed are working from completely different mental models of what good looks like. That gap is the actual problem. Role Scorecards close it.
The scorecard concept has roots in the Topgrading methodology and is widely used in the Scaling Up tradition, primarily as a hiring tool. The version below adapts it for ongoing performance management, with the structure tuned to the clarity gaps I most often see in growth-stage leadership teams.
What Unclear Expectations Actually Cost
When expectations on a leadership team are vague, accountability becomes subjective. Subjective accountability is the engine that powers most of the dysfunction I see in growth-stage companies.
The cost shows up in specific places. Performance reviews often come as a surprise to at least one party. Top performers leave because they cannot tell whether they are crushing it or barely meeting expectations. Underperformers stay too long because no one can make a clear case for moving them out. Decisions get escalated unnecessarily because authority boundaries are fuzzy, or, worse, decisions that should have been escalated are made unilaterally. Cross-functional friction grows because nobody has agreed on what each role provides to the others.
I see this pattern crystallize at different points. When a founder takes a company to market, due diligence often reveals that key roles lack measurable accountability. Buyers discount the multiple. Sometimes they walk. The leadership team that looked impressive in pitch meetings cannot demonstrate that the business runs on systems instead of personalities. Vague roles cap enterprise value, even when revenue does not.
The fix is not more meetings, more reporting, or more management hand-holding. The fix is clarity. Role Scorecards are how you create it.
The Eight Parts of a Role Scorecard
A Role Scorecard is a performance management tool that defines what success looks like for a specific role once someone is in it. It is a living document, used in one-on-ones, monthly reviews, quarterly check-ins, and annual evaluations. It is not a hiring document. The distinction matters.
Job descriptions describe who you are looking for. Qualifications, background, experience, the kind of person who could plausibly do the job. Role Scorecards describe what the person who lands in the role must deliver. Outcomes, behaviors, decisions, relationships, resources. Different documents, different purposes, different lifespans. The job description gets filed after the hire. The scorecard gets used every week.
A complete Role Scorecard has eight sections. Each section answers a different question about the role, and together they create a full picture of what success looks like.
Role Mission. The primary outcome this role exists to achieve, stated in one to three sentences. The North Star. If this person accomplishes nothing else, what must they deliver? A strong mission focuses on outcomes rather than activities, distinguishes this role from adjacent roles, and remains stable as specific targets evolve year to year. The mission prevents role creep and makes trade-offs clear when competing demands arise.
Key Responsibilities. The five most critical areas of ownership for the role, each with Red, Green, and Wow performance thresholds. This is the heart of the scorecard. The discipline of having exactly five responsibilities forces clarity on what truly matters and prevents dilution of focus. Together, these five should account for at least 80% of the role's impact on the business. The Red, Green, and Wow construct makes performance conversations objective rather than subjective.
Behavioral Expectations. Three to five observable behaviors are required for success in this role within your culture. While Key Responsibilities define what must be delivered, Behavioral Expectations define how someone must work to be successful here. These are not personality traits or skills. They are specific, observable actions you can give feedback on after a single interaction. This is where culture stops being aspirational and becomes coachable.
Decision Authority. What this role can decide independently versus what requires approval, and from whom. Most CEOs underbuild this section. Skipping it does not make decisions go away. It just routes everything through escalation by default. Done well, this section gives the role holder room to operate and returns the CEO's calendar.
Other Expectations. Three to five role-specific requirements beyond standard company policy. Travel, reporting cadence, board presentations, on-call rotations, external representation, and industry engagement. The discipline is to capture what is unique to this role, not what applies to every employee. If it belongs in the employee handbook, it does not belong here.
Direct Reports. The titles, not names, of positions reporting into this role. Vacancies noted. Matrixed or shared reporting clarified, as appropriate. Simple to fill out, but worth getting right because gaps in reporting structure tend to surface here before they surface anywhere else.
Key Relationships. Critical internal and external working relationships, with the nature of each interface described. Strong performance in most senior roles depends on effective collaboration across organizational boundaries. This section makes explicit who the role works with, what gets exchanged in each direction, and where the handoffs sit. Cross-functional dysfunction usually traces back to a Key Relationship that was never explicitly defined.
Resources. Budget, systems, data access, and external support are formally allocated to this role. Be specific where it matters. This section answers what the role has access to. It pairs with Key Relationships, which answer who the role needs to work with. Together, the two describe the position's operating environment.
The engine inside the scorecard is the Red, Green, and Wow construct in the Key Responsibilities section. For each of the five responsibilities, you define three thresholds. Red means Houston, we have a problem, and intervention is required. Green is the target, the budget number, what meeting expectations actually means. Wow is stretch performance, exceptional, exceeding expectations significantly. Three levels force honesty. They also remove drama from review conversations because both sides agreed in advance on what good means.
The fundamental insight underneath Role Scorecards is that most performance problems are not people problems. They are clarity problems. People generally rise to the level of explicit, measurable expectations. They drift in the absence of them. The scorecard forces the conversation upstream, before the work, instead of downstream during a review.
Building Your First Scorecard
Role Scorecards work best when built collaboratively, not imposed. Use them when you are scaling a leadership team, transitioning a role, onboarding a new hire, or trying to break a pattern of unclear accountability. They also work for established roles. In fact, an established role with no scorecard is usually the highest-leverage place to start.
Block ninety minutes for the first draft. Solo or with the role holder if they exist.
Start with the Role Mission. Get crystal clear on the one outcome this role exists to produce. If you cannot say it in three sentences or fewer, the role itself is probably trying to do too much. Watch for activity language. If your draft starts with "responsible for" or "manages," rewrite it as an outcome.
Identify the Five Key Responsibilities. The constraint of exactly five is doing real work here. If you have eight, you are diluting focus and usually duplicating ownership. Look for balance across dimensions, not all financial, not all operational, not all people. These five together should account for at least 80% of the role's impact.
Define Red, Green, and Wow for each responsibility. Be specific. Numbers when possible, observable qualitative criteria when not. Watch for vagueness. Bad, good, and great are not Red, Green, and Wow. They are placeholders for the work you have not done yet.
Add Behavioral Expectations. Three to five observable behaviors, stated positively, specific to this role. Not personality traits, not skills, not aspirations. Things you could give feedback on next Tuesday after a specific interaction.
Map Decision Authority. List four to seven categories of decisions. State what this role can decide independently and what requires approval, and from whom. Watch for two failure modes. Too vague creates escalation chaos. Too restrictive creates a bottleneck at the level above.
Capture Other Expectations. Three to five role-specific requirements beyond standard company policy. Travel, reporting cadence, board presentations, and on-call rotations. Skip anything that applies to every employee.
Document Direct Reports. Note vacancies. Distinguish primary reports from matrixed ones if relevant.
Build Key Relationships. Internal and external. For each, name the role and describe the nature of the interface, what gets exchanged, and where the handoff sits. Cross-functional roles need this section to be built carefully. It is the most underdone section in scorecards I review.
Document Resources. Budget, systems, data access, and external support. Be specific where it matters.
Once the draft exists, share it with the role holder and the next layer of leadership. Refine it. Then put it on a review cadence. Spot-check progress in weekly one-on-ones. Review the full scorecard monthly. Update the scorecard structure quarterly. Refresh annually.
The value is not in the document. The value is in the conversation that produces it and the conversations the document enables for the next twelve months. A scorecard that lives on a shared drive but never gets opened in a one-on-one is just a longer version of the job description it was supposed to replace.
What a Scorecard Actually Looks Like
The framework only goes so far in the abstract. Here is a complete sample, anchored to a Chief Operating Officer role at a B2B SaaS company. Use it as a reference for length, specificity, and how the eight sections work together.
Role Mission
Build and optimize the operational infrastructure (systems, processes, and delivery capabilities) required to support the company's revenue growth targets without sacrificing quality, customer experience, or gross margin.
Key Responsibilities
Gross margin protection. Gross margin percentage. Red below 70%, Green 75-78%, Wow above 80%.
Customer onboarding velocity. Average days from contract signed to customer live. Red above 90, Green 45-60, Wow below 30.
Delivery quality. CSAT for implementation and onboarding. Red below 80%, Green 88-92%, Wow above 95%.
Operational scalability. ARR per operations FTE. Red below $250K, Green $350K-$450K, Wow above $500K.
Process maturity. Percentage of core processes documented with SLAs and owners. Red below 50%, Green 75-85%, Wow above 90%.
Behavioral Expectations
Demonstrates systems thinking. Identifies root causes and builds repeatable solutions rather than firefighting individual incidents.
Maintains disciplined focus on process documentation and standardization even when speed feels more urgent.
Shows proactive cross-functional collaboration with the CRO on customer handoffs and with the CTO on product and delivery integration.
Communicates operational constraints and capacity limits clearly and early so leadership can make informed growth decisions.
Decision Authority
Independent authority. Operational process design, SOP creation, and quality standard changes within the existing org structure. Vendor selection for operational tools and services within the approved budget. Staff scheduling and resource allocation within approved headcount.
Requires approval. Changes to customer-facing SLAs or delivery timelines require CRO and CEO sign-off. Outsourcing or offshoring decisions require CEO and Board approval.
Other Expectations
Present the monthly operational dashboard at the executive team meeting (capacity, margins, delivery metrics, customer satisfaction).
Conduct quarterly operational reviews with each delivery team lead.
Maintain and update business continuity and disaster recovery plans annually.
Participate in customer QBRs as needed for strategic accounts.
Deliver quarterly capacity planning forecast to the CEO and CFO aligned with revenue growth projections.
Direct Reports
Director of Professional Services and Implementation. Director of Customer Support. Director of Operations and Process Excellence. IT Manager, if no separate IT function exists.
Key Relationships
Internal. CRO for customer handoff process, onboarding expectations, and the customer feedback loop. CTO and CPO for product and delivery integration, technical escalations, and infrastructure dependencies. CFO for operational cost management, margin analysis, and capacity planning financials. CEO for operational strategy, scalability planning, and resource allocation decisions. CHRO for operational hiring needs, team development, and workforce planning.
External. Key customers for implementation, relationship management, and QBR participation. Implementation and consulting partners for overflow capacity and specialized expertise. Technology vendors for operational tools and infrastructure services.
Resources
Operations department budget for compensation, tools, and vendors within the approved annual plan. Project management, customer support, knowledge base, and BI/reporting platforms. Full access to operational and delivery data. Read access to CRM and financial data. Process improvement consulting and an implementation partner network, as needed.
Where I'd Flag Your Draft
If I were sitting next to you while you built your first scorecard, here is what I would flag.
Treating it like a job description. This is the most common thing I see in first drafts, by a wide margin. The page comes back with a full list of qualifications, activities, and duties. "Responsible for managing the sales organization. Five years of B2B sales leadership experience required." That is a hiring document, not a scorecard. Go through every responsibility and rewrite it as an outcome. If the sentence does not name a measurable result, it is not a scorecard line.
Bad, good, and great labeled as Red, Green, and Wow. If your thresholds read like vague labels, the work has not been done yet. The scorecard technically has Red, Green, and Wow, but practically has nothing measurable. Push every threshold to a number or a specific qualitative criterion. If you cannot define Green specifically, you do not yet know what you are managing toward.
Listing more than five Key Responsibilities. If you find yourself at eight, ten, or twelve responsibilities, the argument for keeping each one will sound reasonable in the moment. This one matters too. We cannot leave that out. The cumulative effect is a scorecard that prioritizes nothing because it claims to prioritize everything. Exactly five is doing real work. If a sixth item is genuinely critical, something already on your list is probably less critical than it looked.
Activity metrics for senior roles. If your senior leader scorecards are full of activities, that is a tell. It usually means you are uncomfortable holding the role accountable for outcomes they cannot fully control, so you have fallen back on tracking effort instead. Push the metrics to lagging indicators. A CFO is responsible for forecast accuracy, cash management, and capital efficiency. Those are the outcomes. Specific activities like running monthly close sit in Other Expectations, if they need to be there at all.
Skipping Decision Authority. If your draft has nothing in this section, you are in the same place most first drafts are. Skipping it does not make the question go away. It just routes every decision through escalation by default. The role holder cannot tell what they own. You keep getting asked to approve things you do not need to approve. Friction grows on both sides. Build this section even if it feels uncomfortable. Especially if it feels uncomfortable.
Drafting Yours
Pick one role on your leadership team and build a Role Scorecard for it. Start with the role where the lack of clarity is costing you the most.
The Role Scorecard Reference Guide includes the full eight-section methodology, sample scorecards for executive roles, and evaluation criteria for each section.
After the draft, share it with the role holder and refine together. The first version is never the final version. The conversation is the value.
If you build a scorecard for a role on your team, I want to hear what surfaced. The most common response I get is some version of "I had no idea we were that unclear." Tell me what you found.
What to Read Next
The Wrong Tool for the Job: Why Job Descriptions Can't Define Leadership Expectations
Red, Green, Wow: How to Set Performance Metrics for Senior Leaders That Actually Work
How to Measure Any Leadership Responsibility (Even the Ones That Feel Unmeasurable)
Run the Business or Build the Business: What Belongs on a Role Scorecard, And What Doesn't
Where Role Scorecards Go Wrong: A Field Guide to Four Common Mistakes
The Role Scorecard Lifecycle: From Before the Hire to Promotion Out of the Role
LEADERSHIP360: Aligning Leadership Teams for Growth
LEADERSHIP360 is my program for assessing and aligning leadership teams in high-growth companies. Role Scorecards are a core deliverable in the program because most of the dysfunction I see at the leadership team level traces back to roles that were never clearly defined. If your team is working hard but not converting effort into measurable outcomes, or if you cannot tell whether the people in seats are the right people for the strategy ahead, LEADERSHIP360 may be the right next step. To learn more, visit below or email programs@eckfeldt.com.
LEADERSHIP360 Program Overview: http://www.eckfeldt.com/team
