The Keeper Test: A Framework for Performance and Talent Decisions

Most organizations manage performance reactively. Someone is clearly underperforming, so the organization responds: a performance improvement plan, a difficult conversation, eventually a separation. The process is backward-looking, slow, and usually painful for everyone involved.

The keeper test is a different framing. Instead of asking "is this person performing well enough to stay?", it asks a forward-looking question: "if this person told me tomorrow they were leaving, would I work hard to keep them?"

That question reorients performance management from reaction to intention. And the answer, applied honestly across a team, often reveals things that are uncomfortable but useful.

The Logic of the Keeper Test

The keeper test concept has circulated in management literature and practice for years, associated with a high-density, high-accountability approach to talent management. The core premise is that a team of genuinely excellent people, each of whom is well-suited for their current role, performs significantly better than a team where several seats are occupied by people who are "fine" but not genuinely strong in their position.

This sounds obvious. But most organizations accumulate a substantial number of "fine but not great" team members, for reasons that are entirely understandable: performance problems are uncomfortable to address, departures are disruptive, and a known quantity (even a mediocre one) often feels safer than the uncertainty of a hiring process.

The keeper test creates a forcing function. It asks managers to make an honest assessment before the discomfort of a performance conversation or the urgency of a departure forces the issue. And it asks them to act on that assessment proactively rather than reactively.

How to Apply the Keeper Test

The keeper test is a diagnostic, not a verdict. It is a question a manager asks themselves, privately, about each member of their team. The question itself: "If this person gave me their notice tomorrow, would I fight to keep them?"

A clear yes means the person is performing well in the role and is a genuine asset. A clear no, honestly acknowledged, opens a different conversation: if you would not fight to keep them, what are you actually doing in the role by keeping them? You are not serving the organization, which would be better served by someone stronger in that seat. And you may not be serving the individual, who might be better matched to a different role or a different environment.

The harder case is the "probably not" or "I am not sure." These are often the most important cases, because they tend to persist without being addressed. The manager is not alarmed enough to act, but not satisfied enough to be confident. The seat stays filled with someone who is neither thriving nor failing, and both sides of that relationship often know it.

Questions That Sharpen the Assessment

The keeper test works best when accompanied by sharper diagnostic questions:

Is this person in the right role, or just in a role? Some people are not underperforming because they lack capability. They are in a role that does not match their strengths or interests. Moving them might be a service to both parties.

Have I given this person what they need to perform? A fair keeper test assessment requires that the manager has been clear about expectations, has given direct feedback, and has provided the resources and support the person needs. Assessing someone as not-keep-worthy without doing those things first is not a performance management discipline. It is management failure.

Is the bar I am applying consistent? If a manager would accept a level of performance from a long-tenured employee that they would not accept from a new hire, the keeper test is being applied inconsistently. The test should ask about the standard for the role, not about tenure or relationship history.

What is the actual cost of staying passive? The default option when a manager is unsure about a team member is usually to stay passive. The keeper test forces the question: what does staying passive actually cost? It costs the performance the team could be getting if the seat were held by someone better matched. It often costs the team member clarity about their situation. And it costs the manager time and energy that could go into coaching someone who will benefit from it.

What the Keeper Test Is Not

The keeper test is sometimes misunderstood as a license for constant churn or as a framework that treats people as disposable. It is neither.

It is not a quota. The keeper test does not imply that a certain percentage of the team should be replaced each year. If every member of a team genuinely meets the "I would fight to keep them" bar, no action is required. The test is a diagnostic, not a mandate.

It is not a substitute for investment. A manager who applies the keeper test without having invested in a team member's development, without having given direct feedback, and without having clearly communicated expectations is using it as a rationalization, not a discipline. The test only means something after genuine effort to support and develop the person.

It is not a test for perfection. The question is not "is this person the best possible hire we could find for this role?" It is whether, if they left, you would actively try to retain them. That is a realistic and achievable bar for good, effective performers.

It is not incompatible with psychological safety. A team where people know that performance genuinely matters is not necessarily an anxious team. Teams that trust their leader to be honest with them, including about performance, often have higher psychological safety than teams where performance problems are ignored until they become irreversible. Honesty, delivered with genuine care for the person, is compatible with a culture where people feel safe to take risks and speak up.

The Conversation That Follows

When a manager concludes that a team member does not pass the keeper test, there are generally three paths:

Direct conversation about expectations and fit. This is often the most respectful and productive path. The manager is honest with the team member about the gap between their current performance and the standard the role requires. This conversation, done well, gives the individual the information they need to make their own decisions and the opportunity to close the gap if they choose.

Role redesign or movement. Sometimes the gap is not about the person's capability but about the match between the person and the role. Moving someone to a different role where their strengths are better utilized is a positive outcome for everyone, if the organization has that option.

Managed separation. Sometimes the honest conclusion is that the organization and the individual are not the right fit, and a respectful, well-managed separation serves both parties better than an indefinite continuation of a situation that is not working.

The common thread is that all three paths require honesty, and the keeper test creates the discipline to arrive at that honesty before a crisis forces it.

Keeper Test at the Leadership Level

The keeper test applies at every level of an organization, including the senior leadership team. In fact, the consequences of a weak link in a leadership team are often larger than a weak link at the individual contributor level, because leaders shape the performance of everyone below them.

Leaders who apply the keeper test rigorously to their own direct reports, and who encourage their direct reports to do the same across the organization, create a culture where talent quality is a genuine operating priority rather than a stated value that gets little actual attention.

This also means leaders must be willing to apply the test to themselves. Would the board fight to keep this CEO? Would the CEO fight to keep this division president? Those are uncomfortable questions, but honest organizations ask them.

Key Facts

Organizations where managers proactively manage team composition, rather than reacting only to obvious performance failures, report higher team satisfaction scores among the remaining team members, not lower.
The cost of a poor performer in a key role typically includes both direct output deficits and indirect costs: the morale impact on high performers who see inadequate performance tolerated.
Proactive performance conversations, conducted early and with genuine care for the individual, have higher rates of positive outcomes (performance improvement or respectful separation) than reactive conversations triggered by a performance crisis.
The most common reason managers give for not applying the keeper test honestly is the discomfort of the subsequent conversation, not uncertainty about the assessment itself.

Frequently Asked Questions

How often should I apply the keeper test? It works best as a regular, low-key discipline rather than a formal annual exercise. Many managers do a quiet version of this at each one-on-one: are things trending in the right direction? Is this person growing into the role? A more formal review quarterly or before performance cycles can also be useful.

What if a team member I would not fight to keep is also performing adequately by all formal metrics? This is the most important case. Formal metrics often measure what is easy to measure, not what matters most. If your honest assessment is that the person is not someone you would fight to keep, and the formal metrics are saying they are fine, the metrics may not be capturing what you actually care about. This is worth examining: what would it take to make you feel confident about this person's contribution?

Is it fair to hold team members to a bar that is not spelled out in their job description? Yes, if the bar is about genuine contribution and fit, and if you have communicated your expectations clearly. Job descriptions capture the minimum requirements of a role. The keeper test asks about something beyond the minimum: is this person a genuine asset to the team?

How do you apply the keeper test to someone who is excellent at their current role but not growing? This depends on what the role requires. Some roles primarily require excellent, consistent execution, not growth. Others require continuous development. Be clear about which applies. If the role requires growth and the person is not growing, that is a genuine issue to address directly.

Does a transparent keeper test culture create anxiety? It can, if it is applied without genuine care for individuals or without the supporting practices of clear expectations and direct feedback. Applied in a context where managers genuinely invest in their people, communicate clearly, and give honest feedback, it tends to produce clarity rather than anxiety. People generally know, at some level, where they stand. Making that explicit, and treating people with respect in the conversation, is usually less damaging than prolonged ambiguity.

Leadership