Awhile back, I shipped a big refactor last week. Weeks of effort, untangling legacy code, the kind of deep backend work that nobody sees unless you tell them about it. I posted in Slack: "Merged the BigRefactor™️!" Maybe a little too detailed about the how and the why, but I was proud of it.

First reply: "Nice! So when are we going to address the related issue in Component X?"

Instantly deflated. Weeks of work, and the response is already about the next thing. It almost makes you not want to share at all.

I've had this happen more times than I can count. And I'll be honest, I've been that person too. Someone shares good news, I get excited, and my brain immediately jumps to what's possible now. I hear "we shipped the thing" and my mouth says "oh cool so now we can do the other thing."

This time though, I sat with it. I let myself feel the deflation instead of brushing it off, and I started thinking about why this keeps happening, why it stings, and what to do about it.

I'm calling it the skipped acknowledgment.

The pattern

You share something you completed, often with real effort behind it. The response barely pauses before jumping to what's next.

It shows up in a few flavors:

• "Great, now we can start on Y." (next steps)
• "Okay, but this doesn't solve Z." (related issues)
• "Did you consider scenario Q?" (critique)
• "Cool, yeah, that needed doing." (faint praise)
• "How is this different than X?" (comparison)
• "I already have something that does Y." (one-upping)

Here's the thing: none of these are mean. I genuinely don't think people are trying to be dismissive. It's excitement. It's a forward-looking, problem-solving brain doing what it does. We're trained to find the next flaw, optimize, move forward.

The impact is the same though. Feels Bad Man.

Why it stings

When someone skips the acknowledgment and pivots straight to what's next, a few things happen at once.

The effort feels invisible. You just spent weeks on something, and the conversation is already about what you haven't done. The work stops feeling like a milestone and starts feeling like a checkbox. Just a prerequisite for the real conversation.

And I think it hits harder in backend/infrastructure work. The stuff I do is deep, detailed, and mostly invisible. When I surface to share a win, that moment is carrying a lot of weight. It's not just "hey I finished a thing," it's "hey, I exist, and the work I've been doing matters."

Tech culture doesn't help. There's this constant pressure for velocity, for forward momentum. Pausing to celebrate feels almost indulgent. And our engineering brains are optimized for finding problems, not sitting with solutions. That lens is great for systems. Less great for people.

When it happens to you

You can't control how people respond. But you can control what you do with the deflation.

Validate your own work. The effort was real whether someone acknowledges it or not. I've started keeping a personal win log for exactly this reason. Sounds corny. Works anyway.

Find your people. Not everyone skips the acknowledgment. Some colleagues are genuinely good at celebrating wins. Share with them intentionally.

Be direct about what you need. Sometimes you just have to say it: "I'm feeling good about getting this done and wanted to share the moment before we talk about what's next." It feels weird the first time. It gets easier.

Redirect gently. If someone pivots too fast, you can pull it back: "Happy to talk next steps, but can we just sit with this one for a sec?"

When you're the one doing it

This is the harder part. Because once you see the pattern, you start catching yourself mid-pivot.

Here's what I'm trying to do:

Pause. When someone shares a win, resist the urge to connect it to something else. Don't jump to the next task, the related problem, the edge case. Just... don't.

Acknowledge first. Match their energy. "That's awesome." "Congrats, that sounds like it was a beast." "You should feel good about that." Simple, direct, no qualifiers.

Ask about their experience. "How does it feel to have that done?" or "That must be a relief." Center the person, not the project.

Then, later, talk about what's next. If the win has you excited about possibilities, great. Say "I love this, it has me thinking about X. Let's talk about it after things settle." Give the win its own space.

Thirty seconds. That's all it takes. Thirty seconds of pure acknowledgment before you move on.

The real optimization

We optimize everything. Processes, pipelines, performance. But not every interaction needs to be optimized for forward progress.

Sometimes the most useful thing you can do is just witness someone's work. See it. Say so. Let the win be the win for a minute before turning it into a stepping stone for the next thing.

Let's be deliberate about that.