My Manager Left My Slack Unread for Five Hours. Then He Liked My LinkedIn Post Within Four Minutes.

At 11:14 AM I sent Amit a Slack message with the error logs attached and one direct question: do we have approval to roll back the morning deployment, or do we wait and risk the client API pipeline staying broken through the afternoon? His green dot was on. It stayed on all day. He read it — Slack shows you when someone's read something, that small shift from undelivered to seen. Nothing came back.

I sent a follow-up at 1:30. Then at 3:00, after a colleague and I had spent the afternoon managing the fallout ourselves, making decisions we weren't supposed to be making without sign-off, fielding questions from the client-facing team about timelines we couldn't officially confirm.

At 4:32 PM, riding the elevator down to get out of that office for ten minutes, my phone vibrated. LinkedIn notification. Amit had liked my post — the one I'd published at 4:28 about microservice telemetry frameworks. He'd seen it within four minutes of it going live.

I stood in that elevator for a moment longer than I needed to. I wasn't angry, exactly. I was just thinking about what that gap meant.

What I Eventually Understood About It

My first instinct was to take it personally — that Amit specifically didn't want to deal with me, or with that particular problem, or that there was something going on I wasn't aware of. I spent a few days with that reading before I let it go, because it wasn't useful and it probably wasn't accurate.

The more accurate reading, I think, is simpler and in some ways more uncomfortable: responding to an internal deployment blocker requires Amit to make a decision, own the outcome, and put his name on a call that might go wrong. If he approves the rollback and something breaks in the process, his approval is on record. If he pushes back and the pipeline stays broken, that's on him too. Either way, he's accountable for something messy and invisible — visible only to the people already in the problem, not to anyone watching from above.

Liking a LinkedIn post about microservice architecture costs him nothing and returns something real. It signals to everyone who sees it — his own managers, people outside the company, recruiters, peers — that he leads a team doing sophisticated technical work. He gets to be associated with the output without any of the friction of the process that produces it.

That's not a defence of it. A team that can't get decisions when they need them pays a real cost — in wasted hours, in bad calls made under pressure, in the slow erosion of trust that comes from feeling like you're on your own inside problems that should have two people in them. I'm describing it, not excusing it.

What Happened When I Changed My Approach

After the third or fourth time this pattern played out, I stopped waiting for Slack responses on anything time-sensitive. Not because I gave up — because I changed the channel.

Anything that genuinely required sign-off, I moved into a formal ticket with a clear deadline flag and a note that I'd be proceeding with a default action if no direction came by a specific time. Not aggressive — just clear. "Blocker on deployment approval raised at 11:14 AM via Slack (unread as of 3:00 PM). Raising formally here. Will proceed with rollback at 4:30 PM unless directed otherwise. Flagging for visibility."

Two things happened. First, responses started coming — not always fast, but they came, because the ticket created a record that was visible to more people than just me and Amit. Second, I stopped feeling like I was shouting into a void, because I wasn't. I had a paper trail that clearly showed when I'd raised something, what I'd said, and what decision had or hadn't been made in response.

The LinkedIn Part Is Actually Worth Using

Here's the thing I didn't expect to think: Amit liking my posts wasn't entirely useless to me either. Every time he engaged with something I'd written publicly, it went out to his network. Some of those people were outside our company. Some were in roles I was interested in. Some were paying attention to the kind of work I was writing about and drawing their own conclusions about who was doing it.

I kept writing. I kept publishing. Not to spite him — because it was genuinely useful. The external profile I was building through those posts was mine, not the company's. It was portable in a way that my internal reputation wasn't. And the more Amit engaged with it, the wider it went.

There's a version of this situation where you pull back on the external work because it feels hollow — your manager is praising you publicly while ignoring you privately, and it starts to feel like performance. I understand that instinct. But the audience for your public writing is not just your manager. The audience is everyone who reads it. Those are two very different groups with very different implications for your career.

What I Actually Learned From That Elevator Moment

I've worked with and around a lot of managers since Amit. Most of them are not bad people. Most of them are operating inside systems that reward certain behaviours and quietly penalise others. Visibility upward is rewarded. Accountability for messy internal decisions is not — at least not immediately, and not publicly.

What that means for the people working under those managers is that you can't outsource your own paper trail. You can't assume that because you raised something, someone senior knows about it. You have to be deliberate about how and where decisions are recorded, because the informal channels — the Slack messages, the verbal conversations, the quick DMs — are not the ones that matter when things go wrong.

And you have to keep building externally, not because your manager will suddenly become more attentive, but because the career you're building is not inside any one manager's field of vision. It's out there, in the work you publish, the problems you write about, the people who read it and remember your name when something relevant comes up.

Amit and I continued working together for another eight months after that elevator moment. I never raised the LinkedIn thing with him directly — it would have been a strange conversation and I don't think it would have changed anything. What changed was how I worked, not how he did.

I documented more. I moved time-sensitive decisions out of informal channels. I kept publishing. And I stopped measuring my manager's Slack response rate as an indicator of how the job was going.

The green dot next to someone's name tells you they're online. It doesn't tell you anything about where their attention actually is. Those are two different things, and once you see the gap between them clearly, you stop being surprised by it.