Losing one teammate hurts. Losing three in a short window feels personal, even when it is not. The temptation is to either pretend nothing happened or to over-explain; neither lands well.
In a recent episode, Amy Porterfield described how three departures from her marketing team triggered her deepest leadership fears—and how she worked through them before addressing her remaining team.
Why back-to-back departures hit different
One departure is a story. Three is a pattern, and patterns trigger the worst kind of team-room speculation. The remaining team quietly asks what is wrong with the business, what is wrong with the manager, what is wrong with their own future.
Porterfield admits the moment pulled her into a dark headspace before she gave herself permission to sit with it. That sequence—feel it, then lead—is the crux of the episode.
What transparent actually looks like
The episode's core move is a direct conversation with the team at a retreat. The frame is challenge versus opportunity, but the substance is honesty about why people left, what the leader does and does not control, and what changes anyway.
The key reframe: the leader is not responsible for the team's feelings, only her own response. Change is inevitable. The choice between failure and opportunity is a daily practice, not a one-off decision.
Worked example: a Scrum team's quiet departure wave
Say you are a Scrum Master and two developers leave in the same quarter. The remaining team starts wondering whether the product is being killed.
Old move: say nothing, hope the backlog absorbs the shock, watch the stand-ups go flat.
New move: in the next sprint review, name what happened, name what you do not know, and name what changes. The product owner commits to a revised roadmap. The team commits to a slower sprint. You commit to one thing you will do differently as a leader. You do not promise the team how they will feel about it.
That is the episode's lesson in a sprint-shaped box.
Our analysis
The episode's most useful idea is also its most counter-intuitive: a leader is not responsible for their team's feelings. That sounds cold until you realize the alternative is a manager who tries to manage morale directly, which never works and often backfires.
The trade-off is real. Radical transparency can feel exposing, and not every team can absorb the same level of candour. The episode argues that the choice between challenge and opportunity is a practice, not a speech—and that the practice has to fit the team's actual capacity.
Who wins: teams that get honest reckoning instead of silence. Who loses: leaders who use the frame as a shortcut to skip their own emotional work.
What to watch: whether more managers adopt the "name what you control, name what you do not" frame, and whether it holds up in larger orgs where the same dynamic plays out quietly but the leader is further removed from the people involved.
Key takeaways
- Back-to-back departures are a leadership test; treat them as such.
- Sit with the fear long enough to lead past it, then address the team.
- Be transparent about what happened and what changes, without managing the team's feelings.
- Use a retreat or off-site to reframe the moment; do not waste a planning meeting on it.
- The challenge-versus-opportunity reframe is a daily practice, not a one-off speech.
Frequently asked questions
What happened on the team?
According to the episode, three people left Amy Porterfield's marketing team in a short period of time.
What was the main fear?
The main fear was that the remaining team's morale would collapse and the business would fall apart.
What did the owner do about it?
The owner journaled about her fears, talked to a coach, and then addressed the team transparently at a retreat.
What is the key leadership lesson?
Leaders are not responsible for their team's feelings—only their own response—and challenges can be reframed as opportunities.
Where can I listen?
The episode is available wherever you get podcasts.