Skip to content
Ryan James
Menu

← Newsletter7 min read

When the Low-Hanging Fruit Runs Out

The longer you lead, the harder it gets to point to a win. That's not the same as doing less.

When you step into a leadership role, you arrive with a gift you don’t realize you have: outside eyes. You haven’t been slowly boiled like the frog in the pot. You can see the gaps — the broken process, the workaround everyone stopped noticing, the thing that should have been fixed three years ago. And you can see them fast.

So you start picking. Not necessarily the most important things — the visible things, the fixable things. The low-hanging fruit. And it feels good. You fix something in week two that had been quietly annoying people for years, and you get that hit of accomplishment.

I’ll be honest about part of what’s happening there, at least for me. Some of that fruit-picking is about validation. When you’re new to a role — new to the title, new to the promotion — you’re carrying imposter syndrome around with you, and knocking out quick wins is how you quiet it. It’s proof you belong.

I don’t think that instinct is a character flaw. I think it’s what happens to humble, generous, decent people when they’re handed authority. When I was asked to become Director of Technology, there was no ego rush, no yes, finally, the title. It was closer to nausea — the weight of what I was now responsible for. You spend the early days quietly asking whether you’re doing the right thing, wishing someone would just hand you the manual. That’s the water most new leaders are swimming in. Quick wins are how you keep your head above it.

There’s also just gravity. We’re wired toward the quick fix. Watch how any leadership meeting builds its agenda: the tactical, operational stuff goes first. Let’s knock this out. It’s discussable, it’s solvable, it closes. Everyone leaves feeling like the meeting did something.

And then, at some point, the fruit runs out.

Maybe you picked it all. Maybe the easy problems were always finite. Either way, you reach up one day and the branch is bare. What’s left is higher, harder, and it doesn’t come loose when you pull. These are the problems that need new systems, new money, new people — the ones you can’t close in a single meeting or a single fiscal year.

This is the part nobody warns you about. You start leaving planning meetings — even good ones, with good people — feeling like you accomplished nothing. You talked for an hour about how hard a problem is, threw everything you had at it, and the problem is still sitting there when you walk out. That’s not an illusion. The problem really is still there.

I’ve come to believe this is where a huge amount of leadership burnout actually lives. Not in overwork, exactly. In the widening gap between the work you’re doing and the wins you can point to. It starts to feel like you’re spinning your wheels, like there’s no traction, like you stopped mattering somewhere back when the easy fixes ran out.

Here’s the reframe I keep coming back to.

Nobody is paying me for the number of solutions I produce. No one has ever looked at a salary line and thought, the ROI here is solution count. That’s not the deal. The deal is that over a day, a week, a month, a year, you take your position, your department, and your organization and move them to a level they weren’t at before. Sometimes that move is visible. Often it isn’t. And not visible is not the same as not happening.

Take a concrete one from my world. Somewhere on campus, people say the Wi-Fi is bad. I can’t wave that away, and I probably can’t just fix it this week either. So I validate the complaint. I investigate. I take measurements, run the analysis, figure out what an actual fix would require. And it turns out the fix needs money I don’t have this fiscal year, or expertise I have to go find. So I don’t solve it. From the outside, nothing happened. The Wi-Fi is still bad. Why haven’t you fixed this?

But look at what actually happened. We went from “someone’s complaining” to “we know exactly what the problem is, we’ve measured it, we know what solving it costs in dollars and people, and we’re ready to implement the moment we have the resources.” That’s not nothing. That’s the difference between walking into next year’s strategic planning with a vague gripe versus walking in ready to execute. The visible fix comes later — but the work that makes the visible fix possible happened now, quietly, while it looked like I was ignoring the problem.

Part of leadership is absorbing that. Taking the questions from the nosebleed seats — why aren’t you fixing anything? — while knowing you’re throwing everything you’ve got at it. You have to hold both at once: the people who can’t see the work, and the work itself.

Which means you have to learn to validate yourself, because on this timeline the outside won’t do it for you. And I think we lean on the outside too much — on the thank-yous, the visible wins, the pat on the back — for our sense of whether the job is going well. When the easy wins dry up, that external supply dries up with them. If it’s your only source of value, you’re in trouble.

So the scorecard has to move inside. Not what did I close this week, but what did I move. What’s further along than it was on Monday. What problem is better understood, better scoped, better positioned than it was before I touched it. Because the person who inherits that problem next — and honestly, it might be me — will find less work waiting for them than there would have been if I’d done nothing. The solution, when it finally comes, will cost less because of the invisible work I did now.

But I’ve come to believe something else just as strongly: you shouldn’t have to do this alone, and the best leadership teams don’t make each other. Moving the scorecard inside your own head is survival. Building it into how the team operates is the actual fix — and it’s the kind of systematic change that keeps good people from burning out on the long, invisible problems.

The first move is changing what counts as progress in the room. If every status update is really asking what did you close, you’ve built a machine that rewards low-hanging fruit and quietly punishes anyone three months deep in a two-year problem. So change the unit. Track the hard problems by stage — identified, measured, scoped, resourced, implemented — and treat movement between stages as a real step. Getting a problem from “someone’s complaining” to “we know exactly what it costs to fix” should get named out loud, in the meeting, the way a closed ticket would. When the team agrees that movement counts, the person doing invisible work stops feeling invisible.

The second is owning the hard problems collectively instead of individually. The slow, expensive ones shouldn’t sit on a single plate with a single name attached to the guilt. Keep them on a shared register — the known hard things the team is carrying, out in the open, revisited on a regular cadence. When it’s the team’s multi-year effort, no one leader lies awake as “the person who still hasn’t fixed the Wi-Fi.” Shared ownership is also shared cover.

The third is deliberately building the pat on the back into your rhythm. External validation dries up exactly when the work gets hardest — nobody outside thanks you for scoping a problem they can’t see. So the team has to become its own source of it. Not empty praise: a standing moment where people report what they moved and the room actually acknowledges it. You are, plainly, giving each other the validation the nosebleed seats can’t.

The fourth is protecting the time and refusing to judge it by the wrong metric. Gravity pulls every agenda toward the quick wins at the top, and the slow work gets whatever minutes are left — usually none. Reserve time for it on purpose. Some teams separate the meetings entirely: one cadence for operational throughput, another for the hard, strategic, ladder-building work, so the slow problems aren’t perpetually crowded out or graded by the same closure clock. A strategic problem measured like an operational ticket will always look like failure.

The last is absorbing the outside pressure together. When the questions come from the nosebleed seats — why isn’t this fixed yet — the individual leader shouldn’t stand there alone holding them. Leadership backs each other with a shared, honest narrative: here’s the problem, here’s the stage we’re at, here’s what it will take. Distributing the weight of the complaints is one of the most protective things a team can do for its own people, and it costs nothing but the decision to do it.

None of this makes the hard problems easy. What it does is keep the people working them from quietly concluding they’re failing while they’re actually succeeding — which is the difference between a team that grinds itself down on the long problems and one that keeps its people intact long enough to solve them.

So move your own scorecard inside. But if you’re on a leadership team — or building one — build the shared scorecard too. The ladder is easier to raise, and a lot harder to fall off of, when someone’s holding the other end.

That’s the job, once the fruit runs out. Not picking what’s easy to reach. Building the ladder for what isn’t — together.

Keep coding!
Ryan

This post first went out on Substack. Join the conversation there or subscribe to get the next one by email.