How to Raise the Floor, Not Just the Ceiling
Why developing your middle performers matters more than investing in your best ones
Megan was the best sorter I’d ever had.
Consistent, fast, almost never wrong. On nights when the volume came in heavy and the floor was stretched, Megan could carry the outbound sort in a way that made the whole thing look more manageable than it was. New managers who shadowed me would watch her work and ask who she was. Senior managers would notice her numbers in the daily report and ask what we were doing right over there.
What we were doing right was Megan.
Then Megan went on maternity leave for six weeks.
The floor didn’t collapse. We managed. But I watched something instructive happen in those six weeks: the shift’s true capability revealed itself. Without Megan absorbing the hard volume and compensating for the slower pacing around her, every gap in the team’s middle became visible. Decisions that Megan had been quietly mopping up now stalled. Quality holds that Megan’s pace had been masking started showing up in the data.
The team hadn’t gotten worse. They’d always been that team. I just hadn’t been seeing it clearly, because I’d been watching Megan.
That six-week absence gave me a more honest picture of what I’d actually built—and what I hadn’t.
Why We Invest in Stars Without Meaning To
It’s not a calculated decision. It’s gravity.
Your top performers produce moments worth noticing. When something goes well, they’re usually involved. When you need to fill a capability gap, they’re the first names that come to mind. When you have a stretch assignment to give, they’re the obvious choice, partly because they’ll succeed and partly because you trust them with something that matters.
This feels like good management. It is, in the immediate sense; putting your best people on your hardest problems produces the best immediate outcomes. But over time, it also means your investment in people is concentrated in the performers who are already performing well, which has a specific effect that most managers don’t connect to this cause.
Your best performers are already close to their ceiling. The upside of investing in someone who’s already at 90% of their potential is real but limited. The upside of investing in someone at 65% is considerably larger. Not because that person is more talented, but because there’s more room to grow.
Meanwhile, your middle performers—solid, reliable, not failing visibly—drift. Not because they’re not capable of developing. Because nobody is specifically investing in them.
Your Floor Runs at Your Average, Not Your Best
If you’ve spent any time in operations, you’ve probably encountered Eliyahu Goldratt’s Theory of Constraints. The idea at the heart of his book The Goal is that the throughput of any system is determined by its bottleneck, not by its fastest component.
He illustrated it with an analogy that’s stuck with generations of operations managers: a hiking troop moving through the woods. The speed of the troop isn’t determined by the fastest hiker at the front. It’s determined by the slowest hiker in the middle. The fast hikers reach camp early, but the troop doesn’t arrive until the last person does. To speed up the troop, you don’t make the fast hikers faster. You close the gap between the fastest and the slowest.
The application to a warehouse or production floor is direct. Your best performer’s rate isn’t the rate your floor delivers. Your average performer’s rate—your floor, not your ceiling—is what determines your actual throughput. When your middle is stuck, the whole operation is stuck, regardless of how fast your Megan is sorting.
This reframes the question that managers usually ask. Most managers ask: how do I get more out of my best people? The question with more leverage is: how do I raise what my average people can do?
Your floor runs at its average, not its best. Raising what average looks like on your team is the highest-leverage development work most managers aren’t doing.
The People Who Never Ask for Development
The challenge with investing in your middle performers is that they don’t ask for it.
Your stars create pull. They achieve things, they get noticed, they get offered opportunities partly because they’ve demonstrated they can handle them. Your struggling performers create urgency. They need conversations, intervention, attention. Both groups are visible to you in active ways.
Your middle performers are visible mostly through their absence from your attention. They show up. They hit the numbers. They don’t cause problems. And because they don’t cause problems, they don’t register on the radar in the same way.
What’s actually happening in that group, underneath the acceptable performance, is often more interesting than the surface suggests. In my experience, the middle of most teams contains people who are capable of significantly more, but haven’t been given a clear signal that more is possible or expected. They’ve calibrated to what gets rewarded here, and what gets rewarded here is hitting the standard. So they hit the standard.
The associate who’s consistently at 100% productivity but never initiates anything isn’t necessarily someone without initiative. She might be someone who tried once, got no response, and filed the experience away. The team lead who handles his zone competently but never expands his thinking beyond it might not have a limited ceiling; he might have never been asked what’s beyond it.
I wrote in The Culture You’re Building Without Knowing It about how recognition patterns teach your team what gets noticed here. The same principle operates in development: who you invest in teaches your team who development is for. When development consistently goes to the same high-profile performers, your middle performers learn (accurately) that development on this floor isn’t something they need to expect.
What Developing the Middle Actually Looks Like
This isn’t the same conversation you’d have with a high performer. Your stars often need challenge and visibility; they’re already engaged and looking for the next thing. Your middle performers often need something different: a signal that you’ve noticed them specifically, a question about where they want to go, and a concrete next thing that’s slightly beyond what they currently do.
The signal matters more than most managers realize. The associate who has been competently doing the same job for eighteen months without a developmental conversation has learned a specific thing: this is the ceiling for people like me here. The first time you sit down with her and ask where she wants to develop—not as a performance conversation, not tied to a problem, just as a genuine question about what she wants—you’re interrupting that belief. That interruption is often what unlocks the engagement that was already there but had no channel.
From there, the mechanics are similar to what I explored in From Average to Excellent: a stretch assignment that’s slightly beyond the current comfort zone, specific feedback on what you’re observing, and consistency over time. The piece that’s different with middle performers is the patience required. Where a high performer might take on a stretch assignment and run with it immediately, a middle performer often needs more time to trust that the invitation is real, that raising her hand won’t just create more scrutiny or more work without any corresponding recognition or development.
Two practical things that tend to work well with this group:
Invisible contribution, made visible. Most middle performers are doing things quietly that nobody has named. The team lead who catches quality issues before they escalate. The associate who shows up early and orients the new hire without being asked. These behaviors matter, and the act of naming them specifically is itself a development conversation. It tells the person what good looks like from your vantage point, which is information they often genuinely don’t have.
Small scope, real responsibility. A stretch assignment doesn’t need to be large. Asking a solid team lead to own a specific process improvement for thirty days—something bounded, something with a clear success metric, something she’ll present the outcome of—gives her a development experience without overextending her. The key is that the responsibility is genuine, not cosmetic. People can tell when they’ve been given a task versus given an opportunity.
What Changes When the Average Goes Up
The most obvious thing: throughput improves. Not because your stars got better, but because the work that was previously sitting on their shoulders—compensating for the slower pace around them, absorbing the quality gaps, carrying the decisions that stalled—gets more evenly distributed. When your middle performers are more capable, your best performers stop being load-bearing walls.
Your delegation options expand too. If you’ve read the Strategic Delegation series, you’ll know that one of the real constraints on effective delegation is having people ready to receive what you’re trying to hand off. A team where development has concentrated at the top has a very thin bench beneath it. A team where you’ve deliberately invested across the middle has multiple people ready for the next responsibility. That breadth is what makes genuine delegation, not just task assignment, possible.
And then there’s the cultural signal, which takes longest to show up but matters most. When middle performers start receiving development attention, two things happen. The people receiving it become more engaged; they’re being seen, invested in, asked about their future. And the people around them observe that development on this floor isn’t reserved for the same two names. That signal, over time, changes who sees themselves as having a future here.
I watched this play out during my time as a pack manager in Reno. The team I inherited was quietly segmented: a handful of visible high performers and a larger group who kept their heads down and hit their numbers. Once I got intentional about where my development conversations were going, things started to shift. Slowly, nothing dramatic in the first few months. But by the time I’d been there nine months, the team had a depth it hadn’t had before. More people could run more things. The stars were still stars, but they were stars on a team, not islands surrounded by average.
Summary
Your floor runs at its average. The question to ask isn’t how to get more from your best performers. They’re already delivering. The question is what’s holding your average performers at the level they’re at, and what it would take to move it.
Most of the time, the answer isn’t skill. It’s investment. The signal that someone specific is expected to grow, delivered consistently, through genuine development conversations and real stretch assignments, with patience for the time it takes to trust that the invitation is real.
That’s the work. It’s less visible than developing a star. The returns take longer to appear. But the floor you’re building, the one where your operation runs at a genuinely higher average, is a more durable thing than the floor where everything depends on who showed up today.
You can build a team with a few exceptional performers and a mediocre average, or you can build a team where exceptional is what the average looks like. Only one of those travels without you.
From Theory to Action
Do the Megan exercise. Think about the one or two people on your floor who are quietly compensating for gaps in everyone around them. Now ask: what does the shift look like in their absence? That picture is a more honest read of your team’s true capability than the daily numbers while they’re present. Start there.
Map where your development attention actually went last quarter. Not where you intended it to go. Where it actually went. Which team leads got stretch assignments? Who had genuine developmental conversations in their one-on-ones? If the list skews toward the top of your performance distribution, that’s not a failure of intention. It’s gravity. The question is whether you’re going to counteract it deliberately.
Pick two middle performers and have a non-performance conversation with each of them this month. Not a feedback session. Not a review. A genuine question: “I’ve been thinking about where I’m investing development time, and I want to ask—where do you want to go? What do you want to be able to do that you can’t yet?” Then listen. What you hear will probably surprise you.
Name one invisible contribution, specifically and publicly. This week, catch someone in your middle doing something quietly good, something that prevents a problem rather than solving one visibly, and name it out loud in front of the team. Not generically (”good work today”) but specifically (”I noticed you flagged that equipment noise before the shift started, That’s exactly the kind of thing that prevents us from losing two hours mid-shift”). One specific recognition tells that person more about what you value than a year of vague positive feedback.
Design one genuine stretch assignment for a middle performer. Not a task. An opportunity. Something with a real outcome, a defined scope, and a clear moment where she’ll present what she learned. Use the Team Capability Mapping process to identify the right person and the right stretch. Build in a debrief using the framework from The Debrief That Builds Leaders when it’s done.
Watch what happens to your stars when your average goes up. As your middle improves, pay attention to your best performers. When they stop quietly compensating for the gaps around them, something changes. Some of them relax and start performing better. Some of them, unexpectedly, start stretching into new responsibilities now that the old ones don’t need them as much. That shift—when your stars start growing because your floor finally gave them room to—is the return on the investment you made in your middle.
This post builds on The Culture You’re Building Without Knowing It and connects directly to last year’s article From Average to Excellent and the Strategic Delegation series.
Next in this arc: When Your Best Player Makes Your Team Worse — the counterintuitive problem of high performers who unintentionally prevent the people around them from developing.