Being Correct Is Not Enough

Kevin's profile picture

Kevin Edry

8 min read · Jan 19, 2026


There's a specific kind of frustration that only happens at work.

It's not the frustration of a hard problem—hard problems are actually fun. It's the frustration of knowing exactly what needs to happen and watching it not happen. Of writing the doc, making the case, getting the nod, and then... nothing. Of being right and it not mattering.

You start taking it personally. You refresh LinkedIn. You vent to your friends. You wonder if you're the crazy one.

I've been there more times than I'd like to admit. And it took me years to realize that the frustration was never really about the obstacle in front of me. It was about my strategy for dealing with it.

It's Always Sunny In PhiladelphiaIt's Always Sunny In Philadelphia

The Wall

You know what I'm talking about.

Whatever's standing between you and the thing you're trying to ship—you've already pictured it. You probably felt a little spike of irritation just now.

That's the wall.

It doesn't matter if you're right. It doesn't matter if the wall is wrong. What matters is that you need something to change, and it's not changing.

The Insanity Loop

So you try again.

Harder this time. More data. More urgency. You schedule a follow-up meeting. You add more stakeholders to the invite, thinking that visibility will create accountability.

It will not.

You write a one-pager. It doesn't work. So you write a longer one-pager, because clearly the problem was insufficient documentation. You escalate to your manager. Your manager escalates to their manager. Meetings are had. Concerns are noted. Action items are assigned and immediately forgotten.

Nothing changes.

You start to feel it—that tightness in your chest, that specific frustration that lives somewhere between your ribs and your throat. The kind that makes you zone out in your next meeting, already drafting your exit in your head.

The definition of insanity is scheduling another alignment meeting and expecting alignment.

The Diagnosis

Here's the thing about frustration that nobody tells you:

Frustration is just a signal. It's not a sign that the world is broken — it was broken long before you showed up. It's a sign that you have a goal you're trying to reach, and your current strategy isn't getting you there.

That's it. That's the whole diagnosis.

Goal + Failing Strategy = Frustration.

Which means when you're frustrated, you have exactly two levers to pull:

  • Quit
  • Change the goal
  • Change the strategy

Most of the time, you don't want to change the goal. The goal is good. The goal is worth fighting for. So that leaves the strategy.

But here's where it gets interesting: not all obstacles are the same. Some walls can move. Some walls can't. And the skill — the actual skill that separates the engineers who get things done from the engineers who explain why things can't — is knowing which is which.

The Escalation Path

Let me give you a framework. When you hit a wall, you escalate through these stages:

Stage 1: Change Your Angle

Before you assume the wall is immovable, ask yourself: Am I pushing on this wrong?

Most obstacles aren't actually immovable. They just won't move for the approach you're currently using.

That stakeholder who shot down your proposal? Maybe you pitched it as a technical improvement when they only care about revenue impact. Same wall. Different angle.

That manager who won't advocate for you? Maybe they don't understand the impact. Maybe they're dealing with pressure you can't see. Maybe you need to make it easier for them to say yes — pre-write the email they'd need to send, frame it as their idea, reduce the perceived risk.

That platform team that's always behind? Maybe they're not ignoring you — they're drowning. Maybe you need to show up with a smaller ask, or offer to do some of the work yourself, or find out what their blocker is and help clear it.

Stage 1 is about changing your strategy, not routing around the obstacle.

Try a different angle. Reframe the problem. Speak their language instead of yours. Find out what they need to say yes.

You'd be surprised how many walls move when you stop pushing and start pulling.

Stage 2: Find a Different Door

Okay. You've tried different angles. You've reframed. You've spoken their language. You've made it easy. The wall still won't move.

Now it's time to stop trying to move the wall and start looking for another way through.

  • Manager won't advocate for your project? Find a different sponsor. Someone two levels up who cares about the outcome, not the org chart.
  • Stakeholder won't approve the big migration? Ship a smaller proof of concept that doesn't require their approval. Let the results speak.
  • Dependent team can't deliver what you need? Build a temporary workaround, or find a third-party solution, or descope your project to remove the dependency entirely.
  • Budget won't get approved this quarter? Find a way to prove value with zero budget first — then come back with data.

Stage 2 is about routing around the obstacle while still achieving your goal.

You're not giving up. You're not changing the goal. You're finding a path that doesn't require this particular wall to move.

This is engineering. You don't yell at gravity; you build airplanes.

Stage 3: Accept the Constraint

Sometimes — and this is the hard part — the wall genuinely cannot move. And there's no door. And there's no window. And the ceiling is also made of wall.

The manager isn't just unhelpful; they're actively opposed and have the political capital to kill anything you build. The legacy system isn't just inconvenient; leadership has explicitly decided it won't be replaced for the next three years. The approval process isn't just slow; it's mandated by legal and compliance and no amount of clever engineering will make it go away.

At this point, the obstacle stops being an obstacle and becomes a constraint.

And constraints are different. Constraints are load-bearing. Constraints are physics.

Stage 3 is about accepting the constraint and engineering your success within it.

This is where you stop asking "how do I change this?" and start asking "how do I succeed given this?"

  • You can't get headcount? Build something that doesn't need headcount.
  • The legacy system can't be replaced? Build an abstraction layer that makes it irrelevant.
  • The approval process takes six weeks? Design your project timeline around it from the start instead of hoping it'll be faster this time.
  • The stakeholder will never prioritize your project? Find a way to ship it as a side effect of something they do prioritize.

This isn't giving up. This is the opposite of giving up. This is saying: I'm going to ship anyway, and I'm going to do it within the laws of physics that govern this organization.

The Fork in the Road

Every engineer eventually arrives at a fork.

Path A:

You hit the wall. You try once, maybe twice. It doesn't move. You get frustrated. You vent to your work friends. You tell yourself "this place is broken" and either quit or quiet-quit.

Six months later, at a new company, you hit a new wall. Different shape, same material.

Rinse. Repeat. Collect the same frustrations at every company like stamps in a passport.

Path B:

You hit the wall. You try Stage 1 — different angles, reframing, speaking their language. Some walls move. For the ones that don't, you try Stage 2 — finding different doors, routing around. And for the true immovables, you accept them as constraints and engineer your success anyway.

You get things done. Not because you had fewer obstacles, but because you had better strategies.

Path A is easier. It protects your ego. If the wall is the problem, then you're not the problem. You can spend an entire career on Path A — company-hopping, collecting grievances, never once stopping to notice that you're the common denominator in all your frustrations.

Every company is broken. Every single one. That's not a bug. That's the spec.

Path B is harder. It requires you to try multiple strategies before declaring something immovable. It requires you to accept real constraints without resentment. It requires you to succeed despite the dysfunction, not wait for the dysfunction to be fixed.

The Skill Nobody Teaches You

I used to think my job was to clear obstacles for my team. Remove the blockers, shield them from the politics, let them focus on the work.

But some obstacles don't clear. Some walls don't move no matter how hard you push. And the skill I actually needed — the one nobody taught me — was knowing when to stop pushing and start routing around.

The best engineers I've worked with understood this instinctively. They knew the system they were engineering was made of people. And they treated that like any other engineering problem: something to understand, to work with, to solve.

That's not selling out. That's not "playing politics." That's engineering — applied to humans instead of systems.

The Bitter Engineer

You know the type. Hell, maybe you've been the type. I have.

The engineer who's been at the company long enough to know where all the bodies are buried. Who can tell you, with depressing accuracy, exactly why every initiative will fail before it starts. Who's "seen this before." Who's technically excellent, respected even, but somehow nothing they care about ever ships.

They're not wrong, usually. That's the tragedy of it. Their pattern-matching is accurate. The walls they point to are real. The constraints they describe genuinely exist.

But somewhere along the way, they stopped escalating through the stages. They stopped trying different angles. They stopped looking for doors. They saw the constraint and made it their identity.

Now they're a wall themselves. The kind that new engineers hit and get warned about. "Don't bother pitching that to him, she'll just tell you why it won't work."

Don't become the bitter engineer.

The walls will always be there. The constraints are real. The question isn't whether your company is broken — it is. The question is whether you're going to spend your career pointing at constraints or finding a way through.

The Uncomfortable Truth

Here's where it gets uncomfortable.

Some constraints are people. And people are not bugs to be fixed.

That team that's always behind? Maybe they're understaffed and doing their best with impossible expectations. Maybe their leadership made promises they can't keep. Maybe they're dealing with constraints you can't see.

Or maybe — and I need you to sit with this one — you're the constraint in someone else's story. Someone else is in a meeting right now, frustrated, trying different angles to get you to see their point of view. Wondering if they need to route around you. Deciding whether you're an obstacle or a constraint.

You are not the protagonist of everyone's narrative.

Dealing with Frustration

Look. The frustration you feel is real. It's valid. You're not crazy for wanting things to be better, for being annoyed that they're not, for feeling stuck.

But you're not stuck. You're just not through yet.

The wall in front of you right now — the one you've been pushing against — it's not the end of the story. It's just where you are in the story. There's a route. You just haven't found it yet.

And maybe — when you do get through — extend a little grace to the walls you passed. They're just people, navigating their own constraints. Some of which might have been you.

The best engineers don't fail because of dysfunction — they succeed despite it.


Kevin's profile picture

Kevin Edry

Entrepreneur, manager, and engineer in Seattle, writing about how engineering teams actually work. Get in touch

Read nextThe Road to Hell is Paved with Good Intentions6 min read