The Sprint That Got Hijacked: A Real Leadership Lesson

It started with a Slack message from a VP: 'Can we just squeeze this in? It's small.' It wasn't small, and I said yes anyway. That single decision quietly rewired an entire sprint, and the lesson from it has stuck with me longer than almost any framework I've studied.

The team had committed to a sprint goal around improving onboarding conversion. Two days in, the 'small' executive request turned into three follow-up asks, each reasonable on its own, each pulled a developer off the committed work, and by Friday the sprint goal was quietly abandoned without anyone formally deciding to abandon it. Nobody said no. Nobody escalated. It just... drifted.

The retro afterward wasn't about the executive, it was about me. I had the authority to protect the sprint and didn't use it, because saying no to a VP felt riskier in the moment than letting the team's actual commitment slide. That's backwards, and it's a mistake I see other PMs make constantly: treating the person with the most positional power as the person whose requests carry the most weight, regardless of what the team already agreed to deliver.

What I do differently now: any mid-sprint request, regardless of who it's from, goes through the same visible triage - what does it displace, and is that trade-off worth making out loud, with the team and the requester both aware of the cost? Sometimes the answer is yes, and that's fine. What can't happen is the trade-off happening silently, because that's what erodes a team's trust in the sprint commitment as a real thing worth protecting.

The uncomfortable leadership lesson: protecting the team's focus sometimes means having a slightly uncomfortable conversation with someone senior to you. Avoiding that conversation doesn't remove the cost, it just moves it onto the team, invisibly, and they're the ones who pay for it in missed goals and eroding trust in planning.