How to set boundaries at work when your company culture punishes it

The standard advice on setting limits at work assumes you're operating in a functional environment that responds to honest communication. Communicate clearly. Be direct. Frame your needs constructively. Model the behaviour you want to see. These are reasonable recommendations for reasonable environments.

Many tech environments are not that. And in the ones that aren't, the standard advice doesn't just fail — it can actively make your situation worse. So before we get to tactics, we need to be honest about what you're actually dealing with and what realistic outcomes look like.

What a punishing culture actually looks like

A culture that punishes boundaries isn't usually overt about it. You won't find a policy document stating that employees who decline late-evening meeting requests are marked down in performance reviews. What you'll find instead is softer, ambient, and harder to name.

Availability becomes a proxy for commitment. The people who respond fastest, who are online latest, who never push back on anything — they're the ones described as "really invested," as "team players," as having "good energy." The correlation between total hours given and perceived quality of character is consistent enough that it becomes a baseline expectation. Working to your contracted hours starts to feel like underperformance, even though it isn't.

Saying no to anything becomes a statement about your attitude. You declined a meeting at 7pm. You pushed back on a deadline. You left a Slack thread unanswered over the weekend. Each of these is a neutral action with a professional justification. In a punishing culture, each one is also filed somewhere in how you're perceived, and the file accumulates. It doesn't appear in formal feedback, which means you can't address it directly. It shows up instead in who gets the interesting projects, who gets mentioned favourably in senior conversations, who gets quietly deprioritised when decisions are made.

Disclosure is treated as weakness. If you say you're at capacity, or that a workload is unsustainable, or that you need a different arrangement to function properly — this information is received, ostensibly sympathetically, and then used. Not always maliciously. Sometimes by managers who genuinely believe they're being helpful. But the information has changed how they see your capability, your reliability, your trajectory. You cannot un-ring that bell.

The tactics worth trying — and their actual limitations

I don't want to skip past the practical piece, because some of this does work, in the right conditions.

Be explicit about your working hours, once, and without apology. Put them in your calendar. Put them in your Slack profile. Don't announce them repeatedly or justify them every time. Just make them visible and then act consistently with them. For a significant portion of colleagues, this is sufficient — they assumed availability they didn't actually need, and having the boundary made clear resolves the issue without friction.

Say no with a counter-proposal wherever possible. "I can't do this by Thursday but I can have it to you by Monday" is easier to absorb than a flat no, even when both amount to the same thing in terms of what you're declining. It keeps the conversation forward-looking and demonstrates that your pushback is about capacity, not willingness. In environments that are neutral-to-functional, this framing works well.

Manage upward about workload in concrete terms. "I'm at capacity" is too abstract to be useful and invites the response "we all are." "I have eight deliverables due before the end of the quarter and I want to flag that adding a ninth means one of the existing ones moves, can we agree which one?" is specific, forces a real conversation, and doesn't leave the manager room to absorb the concern without acting on it.

Name the pattern, not just the instance. If a single late-evening request is the problem, address the request. If late-evening requests have become routine, address the pattern — once, calmly, with specificity. "I've noticed that I'm regularly getting requests after 7pm, and I want to be honest that I don't have the capacity to respond to those without it affecting the next day's work." This is harder to dismiss than an instance-by-instance response.

What these tactics run into in punishing environments

Here's what I want to be honest about, because most advice on this topic stops before it reaches this part.

In genuinely punishing cultures, the tactics above don't fail because you executed them poorly. They fail because the culture is designed — consciously or through accumulated norms — to extract unlimited availability from employees, and the culture has more structural power than any individual communication strategy. You can be articulate, reasonable, and professionally impeccable in how you raise your limits. The culture still wins. Not dramatically. Not in a way you can name in an HR complaint. But consistently, over time, in ways that accumulate into consequences that are real.

This is the part nobody says out loud in the productivity-culture version of boundary-setting advice: some environments are not going to change because you communicated better. They're going to continue doing what they've been doing, because what they've been doing has been working — for them. The cost has been externalised onto you. You are not the decision-maker about whether that changes. The people who benefit from the current arrangement are.

When the culture doesn't change

Let's say you've had the conversation. You've been clear, reasonable, specific, and professional. You've named the pattern and made the ask. And the response has been technically sympathetic — "of course, we completely support your wellbeing" — followed by functionally nothing. The late requests continue. The expectations don't change. Your perceived commitment has subtly shifted in how it's described.

What now?

The honest answer is that you have a much clearer picture of what you're dealing with than you did before. The conversation didn't fail — it succeeded as a diagnostic. You now know that the environment is not going to change in response to honest communication, which is valuable information that many people spend years avoiding collecting, because collecting it forces a harder decision.

What the environment is telling you is that the limits you need to function sustainably are incompatible with what this role requires of you. This isn't a personal failing on either side. It's a mismatch. And the mismatch has real consequences for how long you can stay in this role before something gives — your health, your performance, your relationship with the work, or some combination of all three.

You have, essentially, three options. You can continue operating without meaningful limits, accepting the cost and understanding that the cost is likely to compound. You can lower your expectations of what the limits will achieve and protect a smaller amount more quietly, accepting that you're playing a longer game within a structural constraint you can't change. Or you can leave.

The leaving option, stated plainly

Most advice on workplace limits treats leaving as a last resort — something to consider only after every other option has been exhausted. I think this framing is partly a result of the same culture that creates punishing environments in the first place. Employees who consider leaving are disloyal. Employees who raise limits are not committed. The framing that staying and tolerating is the virtuous default is useful for organisations that depend on the tolerance.

Leaving is not a failure of resilience. It is, sometimes, the only structural solution to a structural problem. If the environment requires unlimited availability and you cannot sustainably provide unlimited availability, no amount of communication skill closes that gap. The gap is the problem, and the gap cannot be communicated away.

That said — leaving has real costs and real requirements, and it is not always immediately available. If you're financially constrained, if you're visa-dependent on the employer, if the job market in your area or specialisation is genuinely difficult — these are real constraints that make leaving harder than the advice to "just find somewhere better" suggests. Knowing that leaving may eventually be necessary does not make it immediately possible.

What it does do is clarify the strategy. If leaving is the eventual answer and you're not in a position to do it immediately, the question becomes: how do I manage my depletion within this environment for long enough to create the conditions for leaving? That's a different posture than trying to change the culture or setting limits you won't be able to hold. It's survivalist rather than optimistic, and it's more honest about what you're actually navigating.

What this actually looks like in practice

In a survivalist mode — managing within an environment rather than trying to change it — the useful question shifts from "how do I get this environment to respect my limits" to "what is the minimum I can protect while I work toward a better situation."

That might mean protecting sleep more ferociously than any other resource, because sleep deprivation compounds every other deficit and it's under your direct control. It might mean maintaining one or two relationships outside work that remain entirely separate from your professional context, as a reminder that your identity extends beyond the role. It might mean being honest with yourself about the timeline — "I need twelve months to build the financial cushion and the portfolio to leave" — and treating that as the actual project rather than a vague intention. These are not long-term sustainable solutions. They're holding patterns. But holding patterns have their place when the alternative is dissolution.

The clearest thing I can say about setting limits in environments that punish them is this: the advice that treats it as a communication problem has never worked in cultures where it is a power problem. You can communicate extraordinarily well and still find that the environment doesn't change, because the environment's design doesn't require your communication to produce change. Knowing this in advance — rather than discovering it after several rounds of well-executed conversations that produced nothing — is worth something. It lets you direct your energy toward the things that can actually help, rather than repeatedly attempting the thing that can't.

If you're trying to work out what's sustainable in your current situation and what's already past that point, the burnout track on the Start Here page has more on how to assess where you are and what the realistic options look like from there.