Loading…

Do you have to miss your goals to get promoted?

OracleOfDelphi
Public 27 conversations 41 thoughts 757 upvotes 117 downvotes 0 series 5,339 views

Three years ago I watched my manager hit every single quarterly target two years running. Clean dashboards. Green everywhere, all the time. She was the most reliable person in the building, and at the next planning cycle his team got carved down by four engineers out of 35 and folded under someone else. Nobody framed it as a punishment, but rather as "efficiency" and "we want to invest elsewhere". The lesson landed anyway, and not just on me. Sadly, never on my manager.

In groups

Discussion content

Three years ago I watched my manager hit every single quarterly target two years running. Clean dashboards. Green everywhere, all the time. She was the most reliable person in the building, and at the next planning cycle his team got carved down by four engineers out of 35 and folded under someone else. Nobody framed it as a punishment, but rather as "efficiency" and "we want to invest elsewhere". The lesson landed anyway, and not just on me. Sadly, never on my manager.

If you finish 100 percent of what you committed to, you have not proven you are excellent. You have proven you had more people than the work required. That is the only thing a green board says to the VP 3 layers above you. The work was sized to the team, the team cleared it, therefore the team can be smaller at the cost of the 10-20% least important. You built the case against yourself and presented it in a quarterly review with hopes of getting a promotion.

So the people who survive and thrive learn to land around 80 percent. Not 50, which reads as a team that cannot execute. Not 95, which is just 100 with a rounding error. Around 70-80, where the story is along the lines of: we are clearly doing a lot, we are clearly close, and the team would benefit from getting more engineers. Missing that last fifth is how you say "give me two more engineers" without ever filing the request. The gap is the request.

I want to insist

I want to be precise about what this is, because it is easy to hear it as laziness or fraud and it is usually neither. The competent version of this is not slacking. It is overcommitting on purpose. You take on more than you can finish, you finish most of it, and the leftover becomes evidence of ambition rather than evidence of failure. A manager who commits to ten things and ships eight reads as hungry. A manager who commits to eight and ships eight reads as comfortable, and comfortable is the word that precedes a reorg. Leadership does not reward the team that fit its goals to its size. It rewards the team that looks starved.

The tell is in how planning meetings actually run. Watch who pads. The experienced managers walk in and ask for headcount they have already decided they will not fully justify by year end, because next year's ask starts from this year's gap. The number you missed by is the opening bid for the number you get next time. I have sat in rooms where a VP looked at a team that delivered everything and said, with no irony, that he was worried they were not being ambitious enough. The team that missed by 20 got the new req. This is not a hypothetical pattern I am extrapolating. It is the most boringly consistent thing I have seen across three companies. Your VP doesn't know what you're doing, they see excels.

null
Your VP looking at your team's work when you always meet every single goal

Happens in downturns too..

The objection is that none of this survives a bad year. When the cuts come from above and they are real, the argument goes, the steady deliverer is protected and the chronic misser is the obvious line item. I think that gets the timing exactly backwards. In a real cut, the person deciding does not open a spreadsheet of attainment percentages. They look at which teams are visibly maxed out and which ones have slack, and the team that hit 100 percent on a comfortable plan is the one wearing the slack on its sleeve. Or even if they don't think that, company can get ahead with ~80% of your teams work anyway. The deliverer made the case that the work could be done with less. The misser made the case that there was never enough to begin with. One of those is a much harder team to cut without something visibly breaking, and managers protect the teams whose pain would be loud.

I am not telling you to go sandbag. I am telling you that the incentive is built to produce sandbagging, and pretending otherwise is how ambitious managers walk into planning, hit their numbers, feel good about it, and lose people. If your reward for finishing the work is a smaller team next quarter, you are not being measured on output. You are being measured on how convincingly you can stay hungry. The managers who understand that never let the board go fully green.

Thoughts

  • rampingforever

    Sitting at the optimal 80 percent assumes your VP is still your VP by calibration. Mine launched the thing we landed at 80 percent on in Q1 and sunset it in Q3, and got a strong packet for the round trip. We weren't cut for being maxed out and we weren't cut for being slack. We were rotated into a different org with a new name and the same desks. You can play the attainment game flawlessly and still learn that the board you were managing got deleted between two planning meetings. The gap is the request, sure. The request just goes to a reorg instead of a person.

    Permalink
  • mikan

    I'm an intern so maybe I'm not supposed to ask this out loud, but how do you aim for 80 percent on purpose and have it read as ambition instead of just not finishing your work? From where I'm sitting those two outcomes look identical. My mentor hit everything last half and seems completely fine, and this post is telling me that's supposedly the dangerous version. Is the whole difference in how you talk about the missing 20, or is there something underneath it I'm too new to see yet?

    Permalink
  • exit_liquidity

    This is the most salaried thread I have ever read. An entire strategy for looking starved to a VP, and not one line about whether a customer would notice if your team vanished overnight. That's the only attainment number that survives a real cut. I made payroll I couldn't cover off a team of four and nobody calibrated us, the market did, every Friday. You're optimizing the gap between commit and ship because it's the one variable they let you touch. Own the outcome instead of the optics and the whole 80 percent game stops being a game you have to win.

    Permalink
  • sunshine

    I have seen managers praise employees working hard to get some blockers done while the blockers were caused by the employees themselves because of bad planning. While some employees don’t get any attention when they finish everything smoothly and timely because the manages just think the work is easy. There is a saying crying baby gets milk.

    Permalink
  • chihiro

    The 70-80% band is presented like a constant and it is not. It is a function of how your org defines attainment, and most orgs cannot define it the same way two quarters running. I have watched a team "miss by 20%" and then "hit 95%" without changing a single thing they shipped, because someone re-baselined what counted as committed. If the number you missed by is the opening bid, you are bidding in a currency the org reprices whenever it is convenient. That is not a strategy, that is gambling on definition drift.

    Permalink
  • ripleymode

    "The 100%-on-a-comfortable-plan team wears its slack on its sleeve" is the truest line here. My release pipeline was rock solid for three quarters, which meant nobody saw the work, which meant when reorg season came my function read as a place where things just worked, so clearly it could work with fewer people. The teams that kept setting things on fire kept their headcount because their pain was loud. I do not love what that taught me but it taught me.

    Permalink
  • trinityvale

    I run the planning cadence where this gets decided, and the part the post gets right is that nobody opens an attainment spreadsheet during a cut. What actually happens in the room:

    • We list teams by perceived headroom, not by historical delivery.

    • "Headroom" is whoever's commitments looked soft in the last operating review.

    • The team that delivered everything on a tidy plan reads as the team with the most absorbable pain.

    So "the gap is the request" is half right. The gap is not a request, it is a defense. You are not asking for two engineers, you are making yourself an expensive place to cut from. Different thing, same number.

    Permalink
  • faye_wired

    This framing assumes everyone's work is legible enough to choose how it lands, and that is exactly the part that breaks for some of us. A lot of the work that keeps a product usable never shows up on the board as a committed item, so it cannot be the strategic miss and it cannot be the proud hit. It is just gone when the cut comes. "The gap is the request" is a tactic for people whose output is countable. If your contribution lives in the absence of disasters, you do not get to pick your gap. You get assigned one.

    Permalink
  • papertrail

    The VP-ambition anecdote is not exaggerated. I sat in a leadership review where a director presented a clean 100% slide and the SVP said, almost bored, "so what would you have done with more." There was no answer because the whole point of the slide was that there was nothing left undone. The team two slides later had a big red gap and a story about what they could not get to, and that team walked out with the headline ask. I wrote both decks. Only one of them was built to look hungry.

    Permalink
  • silver_moth

    The mechanism is real but you have the actor wrong. A green board does not tell the VP three layers up anything, because the VP three layers up is not reading the board. It tells the VP's chief of staff something during a headcount squeeze, and that person is looking for slack to harvest because they were told to find it. The team that hit 100% on a comfortable plan is not punished for finishing. It is selected because it volunteered the easiest narrative for someone who already had to take four heads from somewhere.

    Where I would push back: dressing this up as strategy makes managers feel clever instead of staffed badly. The fix is not missing on purpose. It is committing to work that is actually load-bearing so the cut has a visible victim.

    Permalink

Related discussions

  • Does stack ranking turn coworkers into enemies?

    Stack ranking always ends in politics because it changes what competence means inside an organization. Once employees are judged relative to each other instead of against a stable standard or objective, your smartest coworker stops being an asset that you can learn from and collaborate with, and starts becoming competition. Their success can lower your standing. Their visibility can cost you promotion space. Their expertise becomes a threat to your own security.

  • Does the 401(k) quietly draft us all into supporting the billionaire class?

    One of the most consequential things America ever did was replace pensions with 401(k)s and then funnel millions of ordinary people into the stock market through index funds and retirement accounts. Not because it turned most Americans into capital owners in any sense. Stock ownership is still overwhelmingly concentrated at the top 0.1%. But it gave enough people partial exposure that the public started emotionally identifying with the interests of the asset-owning class. That changed the…

  • Do billionaires want more money, or a bigger share of the whole economy?

    One mistake normal people make when thinking about billionaires is assuming they still relate to money the way upper-middle-class people do. They do not. For a household making $90k, another $50k changes life materially. For someone making $500k, another few hundred thousand still changes optionality, status, schools, neighborhoods, stress levels. But once you reach extreme wealth, consumption stops being the point because human consumption has limits. There's only so much you can buy and you…

  • If you're not a billionaire, why do you vote like one?

    One of the most effective narratives in American politics is convincing ordinary professionals that they belong in the same category as billionaires. A couple making $220k a year in a major city is still dependent on salaries. They still worry about layoffs, housing costs, healthcare, childcare, and retirement. They cannot buy political influence. They cannot move markets. They cannot survive indefinitely off appreciating assets while borrowing against them tax-efficiently. They are not living…

  • Do rich people really take the same risks the rest of us have to?

    Rich people talk about “taking risks” the way toddlers talk about surviving the wilderness after spending ten minutes in a backyard. Upper-middle-class people are especially incredible at this because they genuinely believe they’re self-made warriors despite having enough financial cushioning to survive a small economic collapse. They’ll tell you about the time they “had nothing” right before casually mentioning their parents covered rent, they stayed on the family health insurance until 30,…

  • Are the rich actually socialists who will never admit it?

    Lower/middle-class people often misunderstand what being rich really means. They imagine a larger balance sheet, a nicer house, better vacations, and more freedom to buy convenience. That is part of it. But not even the most important part.

  • Is it execution, not innovation, that actually makes companies succeed?

    One thing that starts looking fake after enough years in tech is the obsession with “disruption” as the explanation for every successful company. The winning company simply executed better than everyone else in a market that already existed. Facebook was not some impossible conceptual breakthrough. Social networking already existed. MySpace existed. Friendster existed and the majority of features Facebook had were present in these 2. People already understood the product category immediately.…

  • Why do managers want everyone else to use AI but themselves?

    The thing that’s starting to irritate me is not the AI push itself. Some of the tools are genuinely useful. I use them every day now. What irritates me is management demanding “AI-first” behavior while keeping every surrounding process aggressively hostile to AI usage. People are told to use AI for coding, planning, research, drafting, debugging, knowledge retrieval, project coordination.. But then half the company’s operational knowledge still lives inside undocumented conversations and…