Feedback doesn't scale

2025-11-2615:4022091another.rodeo

Listening is always hard, and it only gets harder at scale.

When you're leading a team of five or 10 people, feedback is pretty easy. It's not even really "feedback”: you’re just talking. You may have hired everyone yourself. You might sit near them (or at least sit near them virtually). Maybe you have lunch with them regularly. You know their kids' names, their coffee preferences, and what they're reading. So when someone has a concern about the direction you're taking things, they just... tell you.

You trust them. They trust you. It's just friends talking. You know where they're coming from.

At twenty people, things begin to shift a little. You’re probably starting to build up a second layer of leadership and there are multiple teams under you, but you're still fairly close to everyone. The relationships are there, they just may be a bit weaker than before. When someone has a pointed question about your strategy, you probably mostly know their story, their perspective, and what motivates them. The context is fuzzy, but it’s still there.

Then you hit 100#

Somewhere around 100 people, the ground shifts underneath you, as you realize you don’t know everyone anymore. You just can't. There aren't enough hours in the day, and honestly, there aren't enough slots in your brain.

Suddenly you have people whose names you don’t recognize offering very sharp commentary about your “leadership.” They’re talking about you but they don’t know you. There’s no shared history, no accumulated trust, no sense of “we’ve been in the trenches together.” Your brain has no context for processing all these voices.

Who are these people? Why are they yelling at me? Are they generally reasonable, or do they complain about everything? Do they understand the constraints we're under? Do they have the full picture?

Without an existing relationship, it feels like an attack, and your natural human response is to dismiss or deflect the attack. Or worse, to get defensive. Attacks trigger our most primal instincts: fight or flight.

This is the point where a lot of leaders start to struggle. They still want to be open to feedback—they really do—but they're also drowning. They start trusting their intuition about what they should pay attention to and what they should ignore. Sometimes that intuition is right. Sometimes it's just... self-selected, stripped of context, pattern matching against existing biases and relationships.

On top of that, each extra layer of management, each extra level to the top has separated you, and now you’re just not like them anymore. Their struggles are not your struggles anymore.

At 200, it's a deluge#

By the time you reach 200 people or more, feedback isn't an actionable signal anymore. At that size, feedback stops being signal being noise. A big, echoing amphitheater of opinions, each louder than the last, each written in the tone of someone who is absolutely certain they understand the whole system (they don’t), the whole context (they don’t), and your motives (they definitely don’t).

And all those kudos you used to hear? Those dry up. When you had a close relationship with everyone, kudos came naturally. You were just talking. But now folks just expect you to lead, and if they’re happy with your leadership they’re probably mostly quiet about it. They're doing their jobs, trusting you, assuming things are generally fine.

The people who are unhappy? They're loud. And there are a lot of them.

From where you sit, it feels like everybody's mad about everything all the time. And maybe they are! Or maybe it's just selection bias combined with the natural amplification that happens when people with similar grievances find each other. You don't know if this is a real crisis or just three loud people who found each other in a Slack channel. You just can’t tell anymore.

Because feedback doesn’t scale. Humans scale poorly. Your nervous system definitely doesn’t scale.

Why this happens#

Feedback doesn't scale because relationships don’t scale. With five people, you have some personal interaction with everyone on the team. At twenty, you interact with some, but not all. At 100 you still have personal relationships with 10 or 15 people, so there are a lot of gaps. At 200, your personal relationships are a tiny slice of the overall pie.

Making matters worse, as the din gets louder and louder, channels for processing all that feedback get smaller and smaller. Where you once had an open-door policy, now you have “office hours.” Sometimes. When we’re not too busy.

Where once All-Hands meetings had open questions, now you’re forced to take the questions ahead of time. Or not at all.

Even your Slack usage dwindles, because half the time you say anything, someone’s upset with it.

We tell ourselves we're "staying close to the ground" and "maintaining our culture,” But we're not. We can't. Because the fundamental math doesn't work. The sheer volume of feedback we’re getting absolutely overwhelms our ability to process it.

So what do you do about it?#

First, you have to admit the problem exists. Stop pretending you can maintain personal relationships with 200 people. You can't. Nobody can. Once you accept this, you can start building systems and processes that work with this reality instead of bumping against it. You have to filter, sort, and collate the feedback coming in, and you need to do it at a scale larger than your own capacity.

When you can’t rely on “just talk to people,” you need systems that distinguish between:

  • legitimate issues
  • noise
  • venting
  • misunderstandings
  • and “this person is projecting a whole other problem onto leadership”

That means: structured listening, actual intake processes, and ways to synthesize themes instead of reacting to every single spike.

Build proxy relationships. You can't know 200 people, but you can know 10 people who each know 10 people. You should already have strong, trusting relationships with your leadership team, and then set the expectation that they have strong relationships with their own teams, and explicitly ask what’s on people’s minds. When feedback comes up through this chain, it comes with context. Pay attention.

At small scale, trust is direct: I know you. You know me. At larger scale, trust must be delegated: I trust the leaders who are closer to the work than I am. If you don’t intentionally empower those leaders to absorb and contextualize feedback, you’ll drown. They’re the ones who can say: "I know who said that, why they said it, and here’s what’s actually going on."

Build structured channels for feedback. For example, you can set up working groups to dive into thorny problems. The people closest to the problem understand it better than you do, and they can turn a flood of complaints into something you can actually act on. Or consider starting an "employee steering committee" for the sole purpose of collecting feedback and turning it into proposals. You’re essentially deputizing people who care deeply to listen for you, and then manage the feedback din.

Remember that every angry message is still a person. When someone you know well gives you feedback, you might not like it, but you’re likely to say "Oof. Okay. Let’s talk." At scale, you need to find ways to respond with humanity — even when the feedback you received lacks it.

Close the feedback loop. Let people know when you’re acting on their feedback, and if you’re not going to act on it, let them know that you at least heard it. Nobody wants to feel unheard.

In fact, you'll probably think — if you haven't done it already — that you should have an anonymous comment system to capture feedback. Don't. It's a trap. Anonymous feedback is the most contextless feedback you'll get, which makes it the least actionable. And it inevitably turns out to be contradictory or lacking key information, all those folks feel even more unheard and unhappy than before.

Finally, accept that you're going to get it wrong sometimes, and own that. You're going to ignore feedback that turns out to be important. You're going to overreact to feedback that turns out to be noise. When you make a misstep, be transparent about how you're correcting it.

The uncomfortable truth#

Past a certain size, you have to make peace with the fact that a lot of people in your org are going to be frustrated with you, and you're going to have no idea why, and you may not going to be able to fix it.

Not because you're a bad leader. Not because you don't care. But because feedback doesn't scale, relationships don't scale, and the alternative—trying to maintain authentic personal connections with hundreds of people—is a recipe for burnout and failure.

This is genuinely hard to accept, especially if you came up through the early days when you did know everyone. That version of leadership was real, and it worked, and it probably felt really good. But it doesn't work anymore, and pretending it does just makes things worse.

Note: The photo is of a large crowd gathering for a union meeting during the 1933 New York Dressmakers Strike. That's scaling feedback.

Published in Writing

Read the original article

Comments

  • By saghm 2025-11-284:275 reply

    > Somewhere around 100 people, the ground shifts underneath you, as you realize you don’t know everyone anymore. You just can't. There aren't enough hours in the day, and honestly, there aren't enough slots in your brain

    This is definitely a rare exception, but at my first job, my boss's boss's boss (basically the #2 in the engineering organization, although probably only like 2/3 of it was under his purview) somehow seemed to have an unfathomable ability for knowing not only everyone under him the org tree, but details about what they were working on. I think it must have been at least 150, maybe even 200 people, and as far as I could tell he could recall every single person's name, project, and the general status of their work without needing anyone to remind him before talking with them. Maybe he did just really studiously review notes or something before any meeting or even chance of an ad hoc conversation in the halls, but I never really saw him typing at meetings or writing stuff down to keep track of later, so at the very least he'd need to have been able to retain a lot of information long enough to accurately record it later. Witnessing this firsthand for a few years was easily one of the most impressive mental feats I've ever observed.

    • By glompers 2025-11-284:332 reply

      Did having such a person in charge make a qualitative difference in the atmosphere of how work proceeded among people there?

      If so, do you think it would have played out similarly if the organization had had an equally effective "glue person" who wasn't in charge (therefore didn't have any authority to delegate or divide most tasks) and was required to manage upward [sic] to coordinate things for people?

      • By saghm 2025-11-294:15

        I'm not sure, mostly because it's hard for me to feel confident in figuring out what to attribute to that versus other facets of how he did things. Overall, I have an extremely positive view of how he ran things, but I also personally found him great at a lot of the other things that go into a technical leadership position (making good decisions about what to prioritize, having a consistent vision of what our long-term goals were, not falling into the trap of micro-management, having enough technical skill to be able to help out with the higher-level issues while still respecting the areas where others were more knowledgeable, going out of his way to try to address issues that people raised with the idea that retaining talent long-term was hugely important, etc.), so I honestly don't know how much things would have been different if he didn't also have this level of retention of details. It was impressive still though, not in small part because I don't have any trouble imagining someone in his position just genuinely not caring enough to do it even if they were capable.

        Maybe the genuineness that it seemed to come from really is what made the difference in the long run; I obviously don't know how everyone else felt about it, but in other jobs I haven't found it particularly difficult to notice when the general perception of higher-level managers is a lot more positive or negative than my own, so my instinct is that most people probably also liked him, and I do think that makes some amount of difference. Having a "glue" person who is more detail-oriented is probably fine if the reason the actual authority figure doesn't retain the details is just not having that particular skill, but if it's because they genuinely think that the people beneath them in the org chart are just resources they can use to solve problems rather than actual people who will work better in the long term if treated well, then no, I don't think it would be as effective.

      • By patcon 2025-11-2813:10

        LOVE this question! Thanks for asking.

        I also like toying with variants of where "essential elements" can live, sometimes in odd places :)

        https://x.com/patcon_/status/1963648801962369358

        > I have an idea for a quirky event experimenting with the "minimum viable feeling of community", but need to explain some context first. Bear with me...

        > [...]

        > So here's the event idea: what if someone ran an event where the 2nd rule was "NO INTRODUCTIONS", but only because the 1st rule was "you must arrive having fully memorized ONLY everyone's name and face". Beyond the strange entry requirement, what would such an event feel like?

        > And what strange sorts of intimacy might be created by this minimal scaffold of "knowing everyone"... & being in community together? I suspect it might feel like a warm event full of friends, but where everyone had mysteriously forgotten everything they knew about one another :)

    • By fumblebee 2025-11-2810:362 reply

      I recall in the first lecture of some Comp Sci class back at uni, our lecturer had learnt what felt like every student's name and face from their digital profile, some 100 people. Whenever a random student raised their hand to participate he would say say "yes, <first name>". I'm still to this day in awe of that.

      • By bryanlarsen 2025-11-2813:14

        I had a math prof who did that in a class of 200 and still remembered our names 2 years later. Incredible.

      • By xboxnolifes 2025-11-3012:39

        My macroeconomics professor did this. Day 1, he greeted every student by name at the door. The class had at least 100 or so students.

    • By zeroq 2025-11-284:363 reply

      counterpoint

      My last CTO was hired after me, the org was hyperscaling. When i was interviewed I was told that the company is banking on JS and that's what we were doing on both ends [1]

      When CTO was hired he made a walk through the office, greeting every team, he stopped at our cubicle and asked what we were doing - I told him basics - and he said "you should be doing that in Java".

      Few weeks later he had a townhall presentation. He came to a room full of people, plug in his computer and the screen started playing a pornhub flix.

      He didn't got fired. I was.

      • By Aeolun 2025-11-286:01

        I’m not sure it’s really a counterpoint, but still an interesting story (interesting, because it’s not really funny, is it?)

      • By mewpmewp2 2025-11-287:422 reply

        Why did you get fired?

        • By fransje26 2025-11-289:10

          Maybe the p-hub Java player was buggy and shouldn't have auto-played?

        • By ozim 2025-11-2813:591 reply

          Not the OP you asked but.

          I think it is sour grapes that new CTO didn’t know shit and even did full embarrassment on display - yet tech guy who knew his job was let go most likely with his team just because CTO thought whatever they were doing should be in Java.

          • By amy_petrik 2025-11-2818:24

            also a sense of broken promises to the CTOs fault

            javascript coder joined taking the company's statement in good faith "everything will be javascript, the front and back end both" and happily did it

            New CTO joins, warmly visits all, dude who joined in good faith parrots his understanding of what we're doing to the CTO. CTO reacts "NO IT MUST BE JAVA" and this is a flex new CTOs love to do -rewrite everything- often to failure

            javascript coder now arguably may no longer be needed if he's not a java programmer, maybe CTO is bringing in their own guys, gets canned.. gets canned by a clown who (a) is watching porn during work and (b) shows it to everybody and (c) leadership above the CTO saw this and did nothing

      • By saghm 2025-11-2823:47

        I'm honestly not sure I understand what this has to do with what I said.

    • By zipy124 2025-11-2811:112 reply

      Is this that impressive? In my high-school there were roughly 200 people in the year group and I'm pretty sure most of them could list off practically everyones names and something about them?

      • By saghm 2025-11-294:21

        I don't think that's equivalent. If you were responsible for trying to make sure each of those students were getting good grades, keeping track of each of their GPAs, and getting involved proactively whenever signs that someone's grades might be slipping, that might be comparable. There's a difference between "knowing something general about each person" and being able to keep track of the same general detail about all of them and not ever getting mixed up. If anything, I'd imagine that the facts known about each person were more likely to be things that stood out compared to the others rather than 200 difference instances of the same detail.

      • By Macha 2025-11-2814:29

        On day 1 of your first year?

    • By mi_lk 2025-11-2814:151 reply

      Was he a good leader? And is that capability related to him being a good leader, would you say?

      • By saghm 2025-11-294:23

        I responded to a similar question in more detail from a sibling comment, so I won't repeat it all here, but to briefly summarize: yes, I think he was a great leader, but it's hard for me to tell whether it had much to do with that capability specifically. I certainly don't think it's a requirement for a great leader, but I also think it probably helped at least a little, even if it just ended up being a minor convenience for him and one of many small signals that helped convey that he genuinely cared about trying to do his job well.

  • By kdazzle 2025-11-2720:023 reply

    I dont think the solution to not knowing people in your company is to create bureaucracy. Ie - only hanging with 10 executives and a focus group. Get out there and talk to people for a few minutes - at the office or wherever.

    • By TeMPOraL 2025-11-286:361 reply

      Ultimately, it is. The post didn't touch on this, but it's exactly why the world looks like it does - it is, and has always been, recursively subdivided. It's why we have districts and towns and counties and states and countries. Hierarchical governance is a result of trying to cooperate in groups larger than the limit of how many direct relationships our brains can support.

      • By kdazzle 2025-11-2816:35

        Maybe, but a 200 person company isn’t really that big. The CEO should probably get over themselves if they think they couldnt possibly know everyone at least a little bit.

    • By dataflow 2025-11-2723:361 reply

      I think, putting what you're saying another way, just because your capacity might be limited to hearing from N people, that doesn't mean it has to be the same N people all the time. It should include a sampling across everyone so you have a lower chance of systematically missing entire points of view.

      • By wisty 2025-11-281:512 reply

        Teacher here. Best Principal I had would gatecrash your class once a year, then have a chat giving feedback. Kind of stressful (it could happen with little warning) but whatever.

        They knew everyone in the school (ebery teacher and about 500+ student names), and what happened in every class. It took time and talent to do it, but it made them a lot less insulated.

        Claiming you can't know 100-200 people - your high school teacher wrote 100 reports. Now obviously they aren't 100% on the ball, but they have some idea (I hope).

        There's an old story about how Bill Gates once took a call in tech support. A far larger organisation, and he still was willing to dive deep and see what was going on at the least glamorous part of the coalface.

        There's a difference between trying to micromanage everything, and micromanaging enough that you're not out of touch.

        Feedback is a two way street. It both let's you know what is happening, and let's the people below know that you actually care. Even if you can't (and arguably shouldn't) be everywhere at once, it has its place.

        Now yes, it's drive by management and isn't the main tool that a manager should use, but being overly scared that your trusted expert juniors will be destroyed by a senior checking up on them is maybe a bit silly, and if a senior manager is such a tool that they do cause havoc just by looking over someone's shoulder and giving them a bit of feedback you're already in trouble.

        Inulation isn't the answer IMO, just accepting that yes you don't need to know everyone and everything to the same level as if it was a small team.

        • By mattm 2025-11-282:351 reply

          The same principle holds for quality management. You don't need to inspect every single product. However, if you inspect a small number of products at random, you'll detect a large percentage of the quality issues.

          While leaders can't know everyone they should make it a priority to have those random connections outside their inner circle. If they don't, they become in danger of hearing only the info that their inner circle wants them to hear.

          • By anonymouskimmer 2025-11-283:23

            > However, if you inspect a small number of products at random, you'll detect a large percentage of the quality issues.

            As quality issues become fewer, the odds increase that inspecting a small number of products at random will lead to you thinking that there are zero quality issues. Have your inspections procedure scale and adapt to the relative proportion of quality issues you have reason to believe exist. And if you believe you truly have zero quality issues, then you need to switch to an immediate feedback procedure (such as an anonymous tip line, or a non-anonymous one for customer feedback).

        • By Root_Denied 2025-11-283:25

          > There's a difference between trying to micromanage everything, and micromanaging enough that you're not out of touch.

          I think there's a good point to be made here that this isn't micromanaging, it's bypassing feedback layers that have a tendency to filter out critical or important information. That information may or may not be withheld intentionally, but being Bill Gates and seeing that a crucial tool to help a customer doesn't work very fast, or is missing information, or relies on "hacks" (tribal knowledge on how to bypass restrictions or flags) to keep the support process going would be something that wouldn't filter upwards easily.

          Definitely a balance to be had though for sure.

    • By 7bit 2025-11-2810:341 reply

      Our CEO does this. She talks to a lot of people. Once you start talking business, she clearly doesn't care about your opinion, unless you're praising something. If it's remotely critical or a suggestion to change something, you can see in her eyes she's not even processing the words anymore.

      I rather have her not talking to me, because it's much worse knowing she fakes her openness, than actually just not showing up.

      • By avidiax 2025-11-2921:21

        Sounds like some meta-feedback that should be delivered to her. Of course, this kind of person has lots of ways to deflect, so they have to actually genuinely believe in open feedback as a value, and be willing to understand how they are falling short of living up to that value.

        In the worst case, they only want to present as open to feedback, while they are using that feedback to build the list of detractors who will be laid off, not promoted, etc. And this kind of personal feedback can really trigger this sort of person.

  • By w_for_wumbo 2025-11-280:245 reply

    So I get confused when I read things like "feedback doesn't scale". Because what am I, if not a self-organizing collective of a trillion cells. That seems like feedback which scales right there.

    This seems like a concrete example of why this logic is flawed.

    To me I believe it more useful to start with the premise of: I'm already communicating and leading trillions, how do I actually do that?

    A common issue is that we hold thoughts, logic and language as a type of universal gold standard, while ignoring that most of our communication isn't even verbal to begin with. It's context, observation, pattern recognition, a self-serving goal which aligns with the collective, because we're all wanting the same things. What feels good, what's expansive, what's beautiful etc. These are the reward functions for healthy communication in the human body, the more that we align and work with these, the better the results.

    • By TeMPOraL 2025-11-288:21

      > Because what am I, if not a self-organizing collective of a trillion cells. That seems like feedback which scales right there.

      You're not, not in this sense. There is no body-wide feedback at all at the cellular level, any single cell is disposable and nothing will notice if it dies. Any meaningful feedback exists between and within functional units of the body.

      There is, however, the other, original form of feedback that allows the body to exist - the one that allows you to not have this commonly understood "feedback" in the first place. That is, feedback loops, the control theory concept of systems that self-stabilize or self-amplify. This, not some top-level control, is what's keeping the body together.

      The body is a perfect example of a naturally hierarchical system. Society is another. That's what scales.

    • By wavemode 2025-11-283:021 reply

      > So I get confused when I read things like "feedback doesn't scale". Because what am I, if not a self-organizing collective of a trillion cells.

      Well, yeah, that feedback scales perfectly because your cells don't have free will.

      I think there are plenty of real-world examples of large-scale projects where feedback scaled well, for similar reasons... though I doubt we want to use those as a guide.

      • By lukan 2025-11-285:312 reply

        "because your cells don't have free will"

        They are still independent cells. If they stop cooperating with the rest of the body, they become literally cancer.

        • By TeMPOraL 2025-11-288:351 reply

          They are not independent. They're specialized. They're machines bred to perform highly specific functions in a very specific environment. They cannot survive outside of it.

          Edit: in fact, this "negative space" is probably underappreciated as the force defining the concept of a "living organism" itself. The fact that we can't just swap cells or pieces of cells around, that there is no universal, general-purpose cell that can be a skin cell today, a muscle cell tomorrow, a brain cell next week - is what makes nature be composed of organisms, instead of just being one big soup of cells.

          • By lukan 2025-11-2811:50

            Yes, you are right. Independent was not the right word, but I don't find a better one. My point was, cells used to be independent, but if they act independent now, out of sync with the feedback from the whole organism, the results are bad.

        • By 7bit 2025-11-2810:352 reply

          And tons of people get cancer, or muscle cramps, or, or, or. So clearly even on that level feedback doesn't scale.

          • By nolroz 2025-11-2817:05

            This is a great example of when feedback breaks down. The cells should be dying, but don't. I think we say that cancer is influenced by signals that are misinterpreted or ignored.

          • By lukan 2025-11-2811:49

            It does, otherwise you would not be alive. No one said it does work always ..

    • By adamhartenz 2025-11-282:08

      Might be the biggest example of false equivalence I have seen in a long time.

    • By anonymouskimmer 2025-11-283:33

      Cancer.

      Most people who live in a city want the city to function well, and actively do their tiny little bit to see this happen. This doesn't stop them from flipping each other off on the freeway.

      More broadly I think you're missing the point of the article. A single person can command a military of millions, but that single person can't ensure that everyone in that military have all of their needs met, personal emergencies dealt with, or just plain care enough to not half-ass it. Much less hear and respond to everyone's ideas on what would make things better, or what's making things worse.

      Our individual cells have very simple needs in order to keep our larger structure functioning, and even then sometimes things go catastrophically wrong.

HackerNews