This is good management?
You can almost see how a toxic workplace experience seeped into OP's world model.
People just want to feel heard. Show up to listen, zoom out to be strategic, think about the mission.
In an ideal org, we wouldn't need to be 'speed bumps.' But in my experience, the 'Scope Creep Bogeyman' isn't imaginary—it is often the #1 cause of team burnout.
The intent wasn't to glorify 'Slack Management,' but to acknowledge that in 2026, that is the battlefield where a manager often has to stand between their team and a chaotic environment. It’s ugly work, but someone has to be the shield.
Honestly, the "praise public, reprimand privately" truism that people learn is, along with the shit sandwich, one of the most harmful maxims in management.
There are situations where, as the leader, the team needs to see you act. Let's take an example of someone speaking to another team member in an inappropriate way. If you reprimand privately, nobody knows you did that. Now, you have a team that thinks it's ok (or is raging that you think it's ok) to talk to each other in that way. If you call it out publicly, now everyone knows it's not.
It is a double-edged sword, though. I'd not put a junior on full blast for introducing a bug, or a team member for missing an issue in a code review. That would send completely the wrong message.
I'm not sure if you're disagreeing with me or not, given that was the gist of my comment.
a) Demonstrate to all witnesses that the behaviour is not in line with your values
b) Make the victim of the behaviour feel seen and know they aren't alone
c) Make clear to the person receiving the feedback that you're unhappy
To achieve this same result in private conversations is monumentally more effort, if not impossible. If you pull them into a private conversation, you're still publicly reprimanding them, just without giving clear communication to everyone. Do you wait until later to reprimand in private? Then you need to speak to everyone about what was said and repair the damage that the delay in speaking up caused.
However, there are plenty of situations where calling out something so publicly would be the wrong thing to do, like pushing bugs to production, as you'd likely be seen to be overreacting. You still want to give the feedback if, say, the team member was ignoring processes. It's just usually better done in private.
The junior dev is watching, and got the benefit of seeing that you value his time
> managing via Slack
Far preferable to arranging a face to face meeting over this low impact, simple procedural issue
> being a speed bump just because
Defending your team's finite attention and time from random direct requests from the business is a major part of your job as an EM.
> "scope creep" bogeyman
There's good reason scopes are defined and communicated, and deadlines and expectations are managed.
Whenever an issue involves people, slack simply won't suffice. There's too much good will lost on either side. "No worries if not [grumble grumble]!"
This isn't procedural, like sending an invoice to the wrong email address. This is a vp overstepping and threatening the success of another employee. They know what they're doing.
Quickly understanding the urgency/importance of the ask while communicating the impact it is having on the deliverable is the right call. Good business people work like this all the time. Seeing the discussion is a good learning opportunity for a junior.