{
  "$type": "site.standard.document",
  "description": "feat: explore why silence spreads on teams and what to do about it",
  "path": "/posts/why-developers-stop-asking-for-help/",
  "publishedAt": "2025-10-15T00:00:00.000Z",
  "site": "https://read.ryancowl.es",
  "tags": [
    "DevEx"
  ],
  "textContent": "I keep seeing similar things happen on teams when it comes to asking for help.\n\nTenured engineers don't ask questions in public because they feel like they should already know the answer. They've been at the company long enough that admitting confusion feels like exposing a flaw. So they figure things out privately, or they ask one person in a DM.\n\nNew engineers see this and draw the obvious conclusion. Nobody asks questions here. If the experienced folks aren't asking, it must not be safe. So they stay quiet too. They spend hours, sometimes days, stuck on something a ten-minute conversation would have resolved.\n\nEach group's behavior reinforces the other's assumption. The silence feeds itself.\n\n  \n\nThe story I keep thinking about\n\nI worked with an engineer who was going through a career transition. She'd been in a different role for years and was learning to code in a new environment with a new team and a new stack. For the first few months, things went well. She was engaged, asking questions, getting positive feedback from her lead.\n\nThen the feedback went quiet. Not negative, just absent. And the work got harder. She was moving into territory where the problems were ambiguous and the solutions weren't clear. The kind of work where you have to sit with discomfort for a while before things click.\n\nWithout feedback or peers to check in with, the uncertainty grew. The internal story became \"I can't do this, I'm going back to my old role.\" She'd gone from thriving to nearly quitting, and almost nobody on her team knew.\n\nThe root cause wasn't technical. It was learning anxiety compounded by isolation. She was the only person at her experience level on her team. She had no peers going through the same thing. And the culture around her, without meaning to, had communicated that asking for help was something beginners do.\n\nShe pushed through, but only because someone noticed she'd gone quiet and reached out. That wasn't scheduled or part of a process. It was one person paying attention. I think about what would have happened if nobody had.\n\n  \n\nThe environment problem\n\nWhen the environment rewards knowing and penalizes not-knowing, folks perform confidence instead of building it. They pretend they understand when they don't. They avoid asking clarifying questions because the questions might reveal gaps. They spend energy managing how they're perceived instead of actually learning.\n\nThe tricky part is that most environments don't penalize not-knowing explicitly. Nobody says \"you should already know this.\" But the absence of people modeling vulnerability has the same effect. When nobody around you is asking for help, the message is clear even if nobody said it.\n\n  \n\nWhat I've tried\n\nI've tried telling people \"prefer public channels over DMs.\" It doesn't work if the culture doesn't support it. If someone posts a question in a public channel and gets a curt response, or no response at all, they won't do it again. One bad experience is enough to undo ten good ones.\n\nWhat does work is modeling. When I don't know something, I ask in public. Not performatively, just genuinely. \"I'm not sure how this works, can someone help?\" When senior folks do this, it changes the equation for everyone else.\n\nThe other thing that works is building spaces where asking is structurally normal. Peer groups where everyone is learning. Sync sessions where questions are the point. Learning Hours where the first thing you say is \"here's what I'm trying to figure out.\" In those spaces, not knowing isn't an exception. It's the default.\n\n  \n\nWhen to ask for help\n\nThere's something I try to tell folks, especially early on but honestly at any stage. When you're stuck, there's a window where working through it on your own is useful. But past a certain point, you're just stuck. And the longer you stay stuck, the harder it gets to ask, because now you have to explain why you didn't ask sooner.\n\nMost people don't know where that line is. And without explicit guidance, they default to staying quiet too long, because asking feels like admitting failure. The fix is simple. Tell people the line exists. Give them a number if it helps. \"If you've been stuck for more than an hour, reach out.\" Think of it less as a rule and more as permission to ask.\n\nLearning in public helps here too. Not big presentations or formal knowledge shares, just being open about what you're figuring out. \"I'm not sure how this works yet\" is one of the most useful things you can say on a team, because it gives other folks permission to say it too.\n\nThe hardest part is that the folks who need to hear it most are the ones least likely to ask.",
  "title": "Why Developers Stop Asking for Help"
}