One part that stayed with me was the idea that a community manager can't always save a project. They can only control how the project communicates during a crisis. I think that's true.
I remember when Hyperliquid had the JELLY incident. A lot of people were confused and angry because positions were being force closed. The team came out, explained why they made the decision, and shared updates instead of disappearing. Not everyone agreed with them, but at least people knew what was happening.
On the other hand, I've also seen smaller projects where the team goes completely silent after a problem. Mods keep saying "wait for an announcement" for hours while rumors spread everywhere. By the time the official message comes out, most people have already made up their minds.
If I only had 30 minutes and the founder didn't want to speak, my first move would be to explain why their silence is more damaging than making a simple statement. I'd draft something short for them that says what happened, admits the mistake if needed, and explains what the team is doing next. If they still refused, I'd let the community know an update is being prepared instead of pretending everything is normal.
The line about managing the speed of recovery or collapse feels honest to me. We've seen projects recover after hacks or mistakes because they communicated well and acted quickly. We've also seen projects lose their community because they deleted messages or acted like nothing happened. In the end people decide whether to stay or leave, but clear communication can make a huge difference.