One thing that stood out to me from this material was the idea that managing a community is also managing the relationship between the founder and the community. Most times I think that a community manager's job was to communicate with members and keep engagement high. I didn't think much about how much influence a founder's behavior can have on the health of a community.
A situation that comes to mind is when I disagreed with someone above me on the zepra project which i worked. My first instinct was to focus on why I thought the decision was wrong. Looking back, I realize that approach was less effective because people usually respond better when you explain the impact of a decision rather than telling them they are mistaken. The framing examples in this material made me think about how important it is to communicate concerns in a way that helps people see consequences for themselves.
The section about red flags also got me. Sometimes we notice patterns that concern us but ignore them because we like the project, the opportunity, or the people involved. I have experienced situations where I kept expecting things to improve even though the same issues kept repeating. The material's point about collecting evidence over time instead of reacting emotionally felt practical and realistic.
The biggest lesson I am taking away is that not every problem can be fixed. There is a difference between giving honest feedback and becoming emotionally invested in changing someone else's behavior. My responsibility is to communicate professionally, do my work well, and pay attention to patterns. Whether the other person changes is ultimately their decision. That mindset seems healthier and more sustainable in the long run.