How a Team Crisis Was Resolved in 48 Hours — Case Study | Anastasia Totok
Back
Case Study · Tech / Engineering

The Engineer Who Stopped Caring

How a personal crisis became a company-wide risk — and what it took to turn it around in 48 hours.

Mobility / Tech (Europe)
7,000 employees · ~$200M revenue
48 hours + 2-week recovery
$350K product investment
48h
To turn it around
+11%
Customer retention
$1.8M
Added revenue, year one

Two weeks before a major product release, the company's lead engineer began showing a pattern that no one could explain. His performance dropped sharply. Interactions with the team turned hostile. The collaborative, thoughtful engineer everyone relied on had been replaced by someone who seemed to care only about money — and didn't seem to care about people at all.

The release was at risk. The team was at risk. No one knew why.

"The data in his messages told a story his words never would."

I had already worked with other teams in this company, so they gave me access to his communication history. I wasn't looking for performance metrics — I was looking for patterns of meaning.

What I found: a sudden shift in tone. The language had moved from product-focused to self-focused. The care for colleagues was gone, replaced by an almost aggressive drive to establish personal worth. Combined with a visible physical change when I met him in person, I had a working hypothesis before the conversation even began.

This wasn't a performance issue. This was grief.

We met in person. Because we had a prior working relationship, trust came quickly. He opened up: his first serious relationship had just ended. The person who had always led with empathy and built team cohesion had decided — consciously or not — that caring about people was the problem. If he made himself unreachable, no one could hurt him. If he focused on money and status, at least he would have something to show for it.

The shift in his professional behavior was a direct expression of a decision he had made about how to protect himself.

We didn't talk about the release. We talked about what he actually believed about himself, about connection, about what he was afraid of losing. And slowly, we found a way through — not by dismissing the pain, but by separating it from the decisions he was making at work.

What Changed

  • The engineer returned to the project within 48 hours, fully functional and re-engaged with the team
  • The critical product release shipped on schedule — protecting a $350K development investment
  • The company arranged paid leave and professional support — a coach and a therapist — for his recovery
  • He returned to the team two weeks later, restored
  • The product launched successfully — driving an 11% increase in customer loyalty and retention, and generating an additional $1.8M in revenue in its first year alone

Performance problems in technical teams are almost never just technical. Behind the dropped tickets, the missed standups, the hostile Slack messages — there is almost always a person at a turning point.

The fastest path through a team crisis isn't a performance improvement plan. It's understanding what is actually happening in the person at the center of it.

This is the work I do: reading what's underneath the surface — in individuals and in teams — and finding the fastest, most human path back to function and trust.

Facing something that doesn't fit neatly into a framework?

Let's talk