Latest / Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations / How One Engineering Manager Stopped Her Team's Death March
Transcript
- Lucas: There's a pattern in engineering management that I think every leader has seen but very few talk about openly — the death march project. Luna: The one where the deadline is fixed, the scope is growing, and the team is working nights and weekends just to keep their heads above water. Lucas: Exactly. And the scary part is, by the time you realize you're in one, you've usually already burned through a lot of your team's goodwill. I want to talk about a specific case — a mid-size SaaS company I'll call DataFlow, about 40 engineers, where a death march nearly imploded the product team. Luna: If today's tech conversation gave you something usable, consider supporting the show at buy me a coffee dot com slash fexingo. It's what keeps this podcast ad-free and focused on real stories. Lucas: Right — listener support makes episodes like this possible, so if you find value in these deep dives, that's the place. So, DataFlow — their engineering manager, Maria, had committed to a major platform migration by the end of Q2. Luna: And Q2 2026 just wrapped last week, so this is fresh. Lucas: Very fresh. The migration was supposed to take three months, but by month two, feature requests from sales and customer success had added about 40 percent more scope. Maria's team was already working 50-hour weeks, and the new deadline felt impossible. Luna: So she was facing a classic sunk-cost trap — she'd already invested so much that pulling the plug felt wasteful. Lucas: Exactly. But instead of doubling down, Maria did something counterintuitive. She called a meeting with her team and said, 'We're going to trim the tree.' Luna: Trim the tree — I love that phrase. What did it mean in practice? Lucas: She brought out a whiteboard and drew a simple two-by-two matrix. One axis was customer value, the other was implementation complexity. She asked each engineer to place every feature from the backlog onto that grid. High-value, low-complexity — that's the sweet spot. High-value, high-complexity — those get negotiated. Low-value, anything — those get cut. Luna: So she made the trade-offs visible. Stakeholders couldn't argue with a shared visual. Lucas: Right. And the result was that 60 percent of the planned features ended up in the low-value quadrants. Maria took that matrix to her VP and said, 'We can deliver the core migration on time if we drop these. If you want everything, it'll be another two months.' Luna: How did the VP react? Lucas: At first, he pushed back. But Maria had data — she showed that the team's velocity had actually dropped 15 percent in the last sprint despite more hours. Diminishing returns from fatigue. The VP agreed to cut the low-value features, and the team shipped on time with no overtime in the final sprint. Luna: That's a huge win. But I think the harder part is the unlearning — getting leaders to stop equating heroism with effectiveness. Lucas: That's the core insight. Maria told me later that the hardest conversation wasn't with her VP — it was with her own engineers. Some of them felt like cutting scope was admitting failure. She had to reframe it: 'Shipping something that works is success. Burning out the team and missing the deadline is failure.' Luna: And that's the leadership lesson. The manager's job is to protect the team from their own hero instincts. Lucas: And to protect the business from a failed project. The death march doesn't just hurt morale — it hurts the product. When people are exhausted, they make mistakes. Maria's team caught three critical bugs in the final week that would have been missed if they'd been crunching. Luna: So the 'trim the tree' exercise also improved quality. Lucas: Absolutely. And it built trust with stakeholders. The VP started asking for trade-off matrices on every major project after that. One intervention changed the org's decision-making culture. Luna: I think there's something here about the timing of the intervention. Maria didn't wait until week seven of an eight-week crunch. She acted at week five, when there was still room to adjust. Lucas: That's a key point. The earlier you detect the death march, the more options you have. Some warning signs: if your team has been in crunch mode for more than two sprints, if bugs are increasing instead of decreasing, if people stop speaking up in standups. Those are red flags. Luna: And what about when the manager is the one driving the death march — the classic 'we just need to push a little harder' approach? Lucas: That's the hardest scenario because the reflection has to come from within. I've seen managers use retrospectives as a diagnostic. One thing I recommend is asking the team anonymously: 'On a scale of one to ten, how sustainable is our current pace?' If the average is below five, you have your answer. Luna: Simple, but most managers never ask that question. Lucas: Because they're afraid of the answer. But the cost of not asking is way higher. Maria's example shows that transparency — showing the data, making the trade-offs explicit — actually strengthens your position with leadership. Luna: So the playbook is: detect early, visualize the trade-offs, and lead with data rather than with desperation. Lucas: Exactly. And remember that the goal isn't to avoid hard work — it's to avoid wasted work. A death march is almost always waste disguised as effort. Luna: Alright, if you're an engineering manager listening and you suspect you're in a death march right now, what's the one thing you should do today? Lucas: Schedule a 30-minute meeting with your team, no agenda except one question: 'If we could cut 30 percent of our current work without missing the core goal, what would you cut?' Then listen. And then take that list to your stakeholders. Luna: That's a concrete action. And Maria's story proves it works. Lucas: It does. And it's a reminder that leadership is sometimes about having the courage to say 'we can't' so you can later say 'we did.'