The Wrong Tool for the Job: Why Job Descriptions Can't Define Leadership Expectations
The real cause of most leadership performance problems isn't the leader. It's that no one ever wrote down what success looked like.
I was sitting across from a CEO who was done. Done with his VP of Sales. Done making excuses for missed numbers. Done having the same conversation quarter after quarter. He wanted to talk about a performance improvement plan.
I asked him one question before we went there. "What exactly did you expect him to deliver this year?"
He paused. He talked about revenue targets. He talked about building the team. He talked about the pipeline and the process. And the more he talked, the more I could hear it: nothing he was saying had ever been written down. Nothing had been agreed to in a clear, measurable way. His VP of Sales was being held to a standard that existed only in the CEO's head.
This is The Assumed Standard. It is one of the most common and most costly problems I see in leadership teams at growing companies. The CEO has a clear internal picture of what "good" looks like for every senior role. The leader in the role does not have that picture. And no one has noticed the gap until the performance conversation goes sideways.
The problem is not always the person. More often, it is the architecture. And the most common culprit is a tool that was never designed for the job it is being asked to do.
When The Assumed Standard Is Running Your Leadership Team
The symptoms show up in predictable ways.
Performance conversations get contentious. The CEO comes in with a clear view that the leader has underdelivered. The leader comes in feeling like they worked hard and hit most of their goals. Both are operating from different definitions of success, and neither is entirely wrong. The conversation turns into a negotiation about what the standard should have been, rather than an honest look at whether it was met.
Reviews produce surprises. A leader who thought they were having a good year finds out, at the annual review, that the CEO has been disappointed for months. It wasn't malicious. The CEO just never had a clear anchor for the feedback, so it stayed vague until review time forced it into the open. When both sides are operating from different internal models of success, disappointment accumulates silently until it erupts in a formal setting.
Talented people leave. Not because the role was wrong for them, but because they never had a clear enough picture of what winning looked like. The ambiguity becomes exhausting. They find a role somewhere else where expectations are clearer, where they can actually know whether they are doing well without waiting for someone to tell them they are not.
The CEO starts to wonder if anyone on the team is really stepping up. The narrative becomes about the people rather than the system. And that framing makes the real problem harder to see, because the solution looks like finding better people rather than building better architecture.
Spencer Stuart's research on leadership teams confirms the pattern: CEOs consistently underestimate how much of their frustration traces back to expectations they never clearly set. And Gallup's meta-analysis of more than 100,000 teams found that knowing what is expected at work is one of the strongest predictors of performance, engagement, and retention. It is foundational. And yet most growing companies treat expectation-setting as an informal process, something that happens in conversation rather than in writing.
The person is rarely the whole problem. The system is almost always part of it.
The Job Description Was Designed for a Different Job
Most leadership teams are managed against job descriptions. This is understandable. Job descriptions are the tool most organizations have when someone steps into a role. They were designed for recruiting. They describe qualifications, responsibilities, and activities. They help candidates self-select and help hiring managers screen. They do their job at the moment of hire.
After that, they are almost useless for managing performance.
A job description for a VP of Sales might say something like: "Responsible for managing the sales team and achieving revenue targets." That sentence is technically accurate. It tells you almost nothing about what success actually looks like. It does not tell you which revenue target. It does not tell you what "managing" means in practice. It does not tell you how you would know, six months in, whether the role is being performed well or poorly.
The CEO fills in those gaps from their own internal model. The leader fills them in from their own interpretation. Both assume the other is operating from the same picture. No one checks. The job description becomes a shared fiction: a document that both sides have technically seen, creating the illusion of shared understanding without actually producing it.
Job descriptions also go stale immediately. The moment someone starts in a role, the business context begins to shift. Priorities change. The company grows. New challenges emerge. The job description, filed away after the first week, does not change. The CEO's expectations evolve. The leader's understanding of those expectations does not. The gap between them widens, quietly, until something forces it into the open.
Then there is the communication illusion. The hardest thing about communication is believing it has already occurred. A CEO mentions expectations in a kickoff meeting, or during onboarding, or in a one-on-one three months into the role. The leader hears something. Both walk away thinking the conversation happened. But a brief exchange is not a shared operating contract. It is a starting point that needs to be confirmed, documented, and reinforced consistently.
This problem compounds as companies grow. The CEO's expectations for each role get more specific and more demanding as the business scales. What was acceptable performance at $5 million in revenue is not acceptable at $20 million. But those updated expectations rarely get written down. The job description does not change. The assumed standard keeps shifting. The leader is playing a game where the rules keep changing, and no one announces them.
The Price of Operating Without Clear Leadership Expectations
The immediate cost is obvious. Missed results. Difficult conversations. Wasted performance review cycles where both sides spend more energy arguing about what was expected than discussing how to improve.
The deeper cost is harder to see.
When expectations are unclear, CEOs default to gut-feel evaluations. They use relational signals, impressions from meetings, and stories they tell themselves about whether a leader "gets it" or is "really operating at the right level." Harvard's corporate governance research surfaces something most CEOs don't want to hear: many of them realize midway through a formal performance process that they never actually set clear, measurable expectations with the executive in the first place. By then, both sides have dug in. The CEO is frustrated. The leader is defensive. The conversation is about justifying a conclusion rather than solving a problem.
The people cost is significant. Leaders without a clear definition of success can't operate with real autonomy. They are either guessing what the CEO wants and hoping they are right, or constantly checking in to calibrate. Neither is a good use of a senior leader's time or capacity. And the psychological toll is real. Operating without a clear scoreboard is stressful. It produces anxiety rather than confidence. Leaders who could be driving results spend energy trying to figure out whether they are on the right track.
Good leaders leave. Not the ones comfortable with ambiguity, but the ones who want to know exactly what they are accountable for and want the space to deliver it. They are the leaders who, given a clear target and the authority to pursue it, will outperform. They are also the ones most likely to find a better situation when the current one never quite gives them that clarity. Losing them is expensive in ways that rarely get connected back to the expectation-setting failure that caused the problem.
The organizational cost compounds too. When senior leaders don't have clear expectations, the ambiguity cascades downward. Their direct reports operate with even less clarity. Teams are misaligned because their leaders are misaligned. The cost of the original gap multiplies at every level of the organization.
A Better Tool for the Job
The fix is not a better job description. It is a different tool entirely.
A Role Scorecard is a performance management document. It is not a hiring document. It is built around one question: what does success look like for this role, at this company, right now? And it answers that question in writing, with specific metrics, before the performance period begins.
Where a job description lists activities, a Role Scorecard defines outcomes. Where a job description describes qualifications, a Role Scorecard defines what measurable results look like at three performance levels: underperforming, meeting expectations, and exceeding expectations. It replaces the assumed standard with a written standard. Both sides know exactly what they are agreeing to before the work begins.
A complete Role Scorecard has eight sections. Each one solves a specific problem that creates ambiguity in leadership roles.
The Role Mission defines why the position exists and what it must ultimately deliver. Not a list of duties. A statement of strategic impact. If this person accomplishes nothing else, what must they produce?
Key Responsibilities define the five most important areas of ownership, each with a specific metric and clear performance thresholds. Exactly five. Not four, not ten. The discipline of five forces the CEO to be clear about what actually matters most. If a leader has ten things they are accountable for, they are not really accountable for anything.
Behavioral Expectations make the "how" observable, not just the "what." Not personality traits or skills. Observable behaviors that can be evaluated in day-to-day interactions and given as specific feedback.
Decision-Making Rights define what the leader can decide independently and what requires approval. This section alone eliminates an enormous amount of friction. Leaders without defined authority either escalate everything or overstep without realizing it. Both patterns are expensive.
Other Expectations, Direct Reports, Key Relationships, and Resources round out the picture. They provide the context that makes everything else work.
The scorecard is not a one-time document. It is reviewed and updated every 90 days, so as the business evolves, the expectations evolve with it. The standard is always current. The assumed standard does not get a chance to drift.
This is the shift from activity-based management to outcome-based management. It changes the performance conversation from "here is what I think you should have been doing" to "here is what we agreed you would deliver and here is what happened." One of those conversations is productive. The other one is a disagreement.
How To Tell If The Assumed Standard Is Running Your Team
Before moving on, it is worth testing whether this pattern is operating in your organization right now. Most CEOs who are living with it do not realize it until they try to answer a few specific questions.
For each of your senior leaders, try to write down, right now, exactly what you expect them to deliver over the next 12 months. Not activities. Not responsibilities. Outcomes. Specific, measurable results that you could point to at the end of the period and say clearly whether they were achieved. If you struggle to get past a sentence or two for any of them, the standard is still assumed.
Now imagine asking each of those leaders to do the same exercise independently. Write down their top five priorities. Specific and measurable. Then compare the two lists. In organizations where The Assumed Standard is running, the lists will diverge in ways that would surprise both sides. Not on everything, but on enough to explain the friction that shows up in performance conversations.
Think about the last difficult performance conversation you had with a senior leader. Did both of you walk into that conversation with a shared document that defined what success was supposed to look like? Or did the standard get constructed in the room during the conversation? If the latter, that is not a performance management problem. That is a role clarity problem. The conversation was never going to go well because the foundational work had not been done.
Finally, ask whether your leadership team's job descriptions have been updated in the last 12 months. Not reviewed or glanced at. Actually revised to reflect current expectations. If the answer is no, the documents governing performance are describing a role that no longer exists.
Where To Start
The first move is not to build a scorecard. It is to get your own expectations out of your head and onto paper.
You cannot communicate what you have not yet defined. And you cannot hold someone accountable to a standard you cannot articulate. Before anything else, work through what you actually expect from each senior leadership role: what outcomes matter most, what strong performance looks like, and how you would know if it were happening. This exercise is harder than it sounds. Most CEOs find out, once they try to write it down, that what felt clear in their head is a lot vaguer on paper.
Once that clarity exists, the second step is proper communication. Saying it once is not enough. Expectations need to be documented and confirmed in a round-trip conversation. Share the written expectations with the leader. Have them reflect on what they heard. Test whether the picture matches. Ask where they have questions or where the expectations feel unrealistic given current resources and priorities. That conversation will surface misalignments that would otherwise show up as conflict six months from now.
The third step is reinforcement. Expectations that are set once and never revisited will drift. The CEO's priorities shift. The business context changes. New information arrives. The Role Scorecard is reviewed every 90 days specifically to capture those changes before they become sources of confusion. It takes less than an hour per leader per quarter. It prevents far more than an hour of friction and lost productivity.
The next post in this series walks through all eight sections of a Role Scorecard and explains why each one exists. If you want to start building before then, the place to begin is the Role Mission and the five Key Responsibilities. Get those two sections right, and the rest of the scorecard has a solid foundation to build on.
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 Assumed Standard might be affecting your leadership team's ability to perform and your ability to hold them accountable fairly.
For each of your senior leaders, can you write down right now exactly what you expect them to deliver? Not activities, outcomes. If you struggle to get past a sentence or two, that gap is where The Assumed Standard lives. The vaguer your answer, the more room there is for misalignment.
If you asked your leaders to independently write down their top five priorities, how closely would their answers match yours? In most teams I work with, the overlap is lower than anyone expects. The divergence usually explains the friction that shows up in performance conversations.
Think about your most recent difficult performance conversation. Did both sides walk in with a shared written standard? If the standard got constructed during the conversation itself, that is not a performance problem. It is a role clarity problem. The conversation was set up to fail before it started.
Take the Next Step
If this post surfaced a gap 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, 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 team.
