The Reliable Team Trap
Why delivering well can quietly cap your career, and what to do about it
Years ago, I took over a project full of genuinely exciting technology. It was new to the company, which meant it had almost no internal support yet, and I decided the way to fix that was to earn it. I worked with every stakeholder I could find and said yes to nearly everything they asked for, because the team needed to deliver and I wanted the technology to win. The team did an outstanding job against a very broad set of requirements. People thought highly of us, and that became the start of a trap: the better we delivered, the more we were asked to carry.
The reward for all of that was more requirements and more internal clients. Which is success, and I want to be clear that it was. But after years of working that hard, I was leading the same-sized team, doing more and more, and standing in exactly the same place. My reviews were good. My peers, whom I liked, weren’t working anywhere near as hard, and they were still my peers. I wasn’t getting a promotion or any broader responsibility, just more work and the privilege of doing it well. After six years, I left that team, not because I was unhappy with the team or what we built, but because the only thing waiting for me there was more of the same.
I’d been trusted to deliver. I had never been trusted to decide anything beyond the box my team was in. It took me a long time to understand that those are two different things, and that being very good at the first can actively keep you from the second.
The two rewards
The question people in this situation ask, the question I asked, is some version of “I’m doing great work, so why am I not getting more influence?” The honest answer is that reliability and standing are rewarded by completely different mechanisms, and most organizations hand them out separately. By “standing,” I mean the level of recognized authority, influence, and visibility you hold within the organization. Standing shows up as being consulted on big decisions, having a seat at strategic conversations, or being trusted to shape direction beyond your team’s immediate scope. That split is why the reliable team can be essential yet remain outside the conversation about direction.
Delivering well builds trust, and trust gets rewarded with more work of the same kind. More scope. Maybe (but not often) more headcount. More to be responsible for, all inside the lane you already occupy. Strategic standing comes from somewhere else: being seen to have judgment about direction. That takes capacity and visibility that pure execution never produces on its own. The better you are at absorbing work, the less room you have left for the one thing that would change how you’re seen.
Left alone, this turns you into something load-bearing rather than influential. The organization optimizes around you as a dependable function. Your capacity gets consumed, your strategic voice goes quiet at exactly the moment it needs to be loud, and eventually, the absence of that voice is read as the absence of the ability. There’s a second, crueler turn to it. Once you’re delivering so much of the critical work, you’re not just passed over for bigger things; you’re seen as too important where you are to move at all. You’ve quietly locked yourself into the role. Sometimes the only way out is the one I took: leaving.
Running an organization, or leading it
Underneath all of this is one mechanism. Someone is always setting the direction for your part of the company. If it isn’t you, it’s your boss, by default.
As long as you aren’t articulating where your area should go, your boss has to do it for you. That means when leadership or the board asks about your part of the organization, your boss answers in their own words, not yours. Not because they’re taking credit, but because you never gave them your version to repeat. You can be running the entire thing while still having the person above you narrate where it’s going. That’s the difference between running an organization and leading it. You’re doing all the work of the first and getting none of the standing of the second.
I’ve had this conversation with people who reported to me more than once. What I tell them is direct: you’re running your organization, you’re not leading it. I’m still the one setting your strategy and your long-term direction. Until you push me out of the way and start setting that vision yourself, I can’t move you up, because I still need you to run the thing. It sounds harsh in print. It’s also the most useful thing I can say to someone who’s stuck.
Reliability buys you trust to execute. It does not buy you trust to make the decision. Those are different currencies, and you can be rich in one and broke in the other. The reliable team is the one everyone counts on and no one consults.
Two leaders, same work, different endings
I’ve watched this play out from both sides with people I’ve worked with over the years.
One of them worked incredibly hard, kept ridiculous hours, took on far too much, and delivered on all of it through sheer force of will. Her team was out-executing the teams around them. Leadership’s response was to hand her more critical work because her team did it so well. Her people were burning out under the load, and she had no time left to think beyond the next delivery. Her peers were delivering less and talking about their plans more, and leadership rewarded them with more resources, while she couldn’t get more help, because her team kept hitting its numbers even as it went under. She received private feedback on her team’s morale scores and public praise for what the team shipped. Eventually, she left for her own sanity. She’d assumed the work would speak for itself. The organization wasn’t punishing her by piling on more. It was responding rationally to the signal she was sending: “We’ve got this, don’t worry about us.”
Another leader I worked with had real strategic instincts but was too buried in the day-to-day to show them to anyone. Over time, he made deliberate room for strategy. The more he did it, the more autonomy he earned and the more control his team had over its own direction. With a strategy in place, he was suddenly better positioned to decide what work not to take on, because he could say what did and didn’t fit. His manager saw that thinking, recognized it as strategic, and promoted him.
The difference between them wasn’t the quality of the work. Both teams were excellent. The difference was whether the judgment behind the work was ever made visible, and whether they made the time to build and articulate a direction in the first place. “The work speaks for itself”; it is a story we tell ourselves. Work doesn’t speak. People do, and usually about their own work.
Four moves that change what you’re measured on
A reliable leader is measured on output. A strategic peer is measured on judgment. There are four moves that shift what you’re measured on, and none of them is about doing more. Done right, they’re about being seen for what you already do. They move you from execution to direction.
First, show the thinking. Report your judgment and your decisions, not just your status. When the only thing your boss ever hears is that the work is done and on track, they learn that you’re dependable and nothing else. When they hear the calls you made and why, they learn how you think, and that’s the raw material of strategic trust.
Second, build the bench. You can’t form a direction if every hour is spent on delivery. Building leadership underneath you isn’t just succession hygiene. It’s how you buy back the capacity that standing requires. It’s also the move people skip, because it feels like a luxury when you’re already underwater. The first steps are usually small, but they matter: delegate a recurring task you usually handle to a team member, or set aside time each week to mentor someone on your team. Even handing off meeting ownership or reporting can give both you and your reports valuable space to grow. Start by identifying one thing you do that no one else can yet, and teach it to someone else, even if it takes longer at first. These small moves break the habit of holding on to everything and begin building a true leadership layer beneath you.
Third, claim the contribution. Reliable teams chronically under-claim because they assume the value is obvious. Connect what your team delivers to the business outcome it enables, out loud, before someone else’s framing fills the vacuum. That isn’t self-promotion. It’s making your work legible to the people who decide where the company goes. If it feels uncomfortable, one authentic approach is to focus on clarity rather than credit. For example, instead of saying, “My team rebuilt the entire reporting pipeline,” you might say, “This quarter, we improved the reporting pipeline, which reduced the time to insights for sales by 40 percent, enabling faster decisions across the business.” You are simply drawing a line from the team’s work to its real effect, so that the value is understood and not left to interpretation.
The fourth move, take a position, is the one that actually moves you. Setting your own strategy is how you push your boss out of the way of your own job. As long as you don’t set the direction for your area, your boss has to, and that keeps you running the organization instead of leading it. Bring a forward-looking perspective on your domain, not just answers to today’s questions, and present it to your manager before they ask. You don’t have to arrive fully formed. You do have to talk about the future consistently enough that when someone above you describes your direction, they’re repeating your words back to you. That is what makes the throughline visible.
Three of these, showing the thinking, claiming the contribution, and taking a position, are about visibility. One, building the bench, is about capacity. Work only the visibility moves without the capacity to back them, and you’ll burn out. Build capacity, but never make any of it visible, and nothing changes in how you’re seen. You need both. Nobody is going to hand you strategic standing as a reward for never needing help.
Putting it to work
Start by assessing two things honestly. Listen to your own status updates for a month. If they’re all output and no judgment, that’s the leak, because your manager has no window into how you decide, only into what you produce. Then look at where your hours go. If there’s no slack anywhere, you have no room to do anything but deliver, and no amount of wanting influence will create that room for you.
One practice I rely on for this: every week I look at where my time went, and every six months I write down where I think it should go. When the two drift apart, I pull them back together. That’s how I keep time for direction, not just execution. It’s also how I keep the ending from writing itself.
If you want a place to start, try a simple two-column weekly tracking template. In the first column, list the main tasks you spent most of your time on each week. In the second column, make a quick note for each task: was it delivery or direction, and did it involve judgment or just status? Even a basic journal with this breakdown makes your real pattern visible within a month. For status updates, keep a log by noting after every meeting or email update whether you simply reported output or included a decision and your reasoning. These running notes will quickly show whether you’re consistently showing how you think, or just what you finished. If this seems like a lot of work, it’s something an AI skill can easily help with.
Each move has a small, concrete version.
To show the thinking, in your next one-on-one, replace one status item with one decision you made and the trade-off behind it. Not a report, a window into your reasoning.
For building the bench, identify the one thing only you can do, and the things you do only because no one else can yet, and start handing off that second category even though it’s slower at first. It’s the same trap as being too busy to delegate the things you’re too busy to do.
To claim the contribution, once a quarter, write the two or three sentences that connect your team’s work to a business result, and share them with your boss and your peers. If you don’t have the language for it, finding that language is the work.
To take a position, pick one trend in your domain and form an actual opinion about what it means for your company over the next six months versus the next two years. You don’t need to be right. You need to be substantive.
The most common failure mode is treating all of this as a volume problem. People respond to feeling overlooked by delivering even harder, which deepens the trap, because more output only reinforces the signal that’s keeping them stuck. Delivery is the muscle that got you here, so under pressure, you reach for it, even when it’s the wrong lever. The frustrating version of this is watching a peer whose team is doing less get more attention, because their manager constantly talks about how well they’re doing, with little to back it up. That gets caught eventually. But in the meantime, the people talking get noticed, and the people only executing don’t. Your work should speak for itself. It doesn’t.
Signs you are already in it
A few things to watch for. Your scope keeps growing while your decision-making authority doesn’t, so you’re running more and deciding less. Your boss still sets the vision for your area, and you’ve gotten comfortable executing it. A peer with a smaller or weaker organization has more standing with leadership than you do. Reorgs move things away from you instead of toward you, and it catches you off guard, because the delivery story told you that you’d earned the opposite. The steady positive feedback never converts into the conversations you want to be in. Scope is not the same as standing. You can get more to run, less to decide, and call it a promotion.
The people inside the trap
It helps to see the roles this dynamic creates. The reliable leader is heads down and proud of the work, and increasingly resentful that none of it is translating into more responsibility. They’re often the most reluctant to do the visibility moves, because those read as politics, and politics feels beneath the work. The boss usually isn’t withholding anything on purpose. They’ve learned this person handles things, so they stop bringing them the messy, undefined problems and take those to whoever is making noise about direction instead. Reliability becomes a reason to exclude you from interesting conversations. The peer who reads as strategic often delivers less and narrates more. They’ve figured out that the story about the work travels farther than the work itself. And your team is the one absorbing the ever-growing scope, where the cycle of doing good work, getting handed more, stabilizing, and repeating runs until something breaks. Usually, that something is a person.
Your boss isn’t hiding the strategy conversation from you. They just never see you make room for it, so they take it somewhere else. You can be the wall that everything rests on and still not be in the room where the building gets designed.
What finally changes
When I moved to a new group at that same company to take on a new greenfield product, I did it differently. I built a strategy and worked with the team to deliver against it. That alone made it far easier to decide what to say yes to and what to say no to. More importantly, I made the plan visible to my team, to my peers, and to my leadership, and when we delivered against it, I made that visible too. The combination is what finally got me my first executive promotion.
What practice taught me, and theory never did, is that the leaders who get strategic standing aren’t the loudest or the most political. They’re the ones who made a deliberate choice to be seen for their judgment and not only their output, and who protected the capacity to have judgment in the first place. This isn’t a license to coast on narrative. A leader who claims contributions they didn’t earn gets found out. The move only works when the delivery is real, and the visibility is honest. Do the good work, then point to the outcome and not just the output.
I used to think that making my work visible was politics. It isn’t. It’s the difference between your judgment being useful to the company and being invisible to it.
Reliability earns you trust to execute. If you want to be trusted to decide, you have to make your judgment visible and protect the capacity to have it. That’s a separate job, and no one is going to do it for you. A test you can run this week: look at the last month of how you’ve shown up to your manager. Was it mostly output, or did they get a window into how you think and where you’d take things? If it was mostly output, you’ve found the gap. Start with one move. The team that always says “I got it” gets trusted to handle the work and overlooked for everything else. Reliability is the floor. It was never going to be the ceiling.
To hear an extended discussion of this topic, please listen to my most recent podcast episode: The Reliable Team Trap: Why Execution Excellence Doesn’t Earn You Influence.
If you’re struggling to build a strategic thinking practice, check out my article Crafting a Technical Strategy That Actually Works
Thanks again for reading! If you find it helpful, please share it with your friends.
Buy on Amazon | Buy on Bookshop.org | Buy on Audible | Other stores